Failure during NOD32 install - exit code: 121.

Discussion in 'NOD32 version 2 Forum' started by mattjabs, Jun 7, 2006.

Thread Status:
Not open for further replies.
  1. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    Okay! I'm about ready to pull my hair out & the NOD32 support in San Diego cannot seem to help. I have the corporate version with a month long, 10 user license (for testing on my network before purchase).

    I really want to get the program working but am having problems with the remote install feature on my WinXP Pro SP2 laptop. Note: I did install the trial version, but have since uninstalled it, rebooted & ran the reg key deletions that I received from Nigel in the San Diego office. Anyway, when I go to push the package that I built, out to my laptop, I get the following error: Failure during NOD32 install - exit code: 121.

    Here is my nod32installer.log file:

    [2006-06-07 10:23:04.744] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 10:23:04.744] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 10:23:04.759] Status 1: NOD32 Installer is creating a temporary file.
    [2006-06-07 10:23:04.759] Status 1: NOD32 Installer is downloading an installation package 'issidefault' from server 'ISSIHQ1:2224'.
    [2006-06-07 10:23:04.953] Status 1: NOD32 Installer is installing NOD32.
    [2006-06-07 10:23:10.240] Status 1012: Failure during NOD32 install - exit code: 121.
    [2006-06-07 10:24:37.904] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 10:24:37.904] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 10:24:37.904] Status 1: NOD32 Installer is creating a temporary file.
    [2006-06-07 10:24:37.919] Status 1: NOD32 Installer is downloading an installation package 'issidefault' from server 'ISSIHQ1:2224'.
    [2006-06-07 10:24:38.097] Status 1: NOD32 Installer is installing NOD32.
    [2006-06-07 10:24:42.119] Status 1012: Failure during NOD32 install - exit code: 121.
    [2006-06-07 10:26:53.343] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 10:26:53.359] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 10:26:53.359] Status 1: NOD32 Installer is creating a temporary file.
    [2006-06-07 10:26:53.359] Status 1: NOD32 Installer is downloading an installation package 'issidefault' from server 'ISSIHQ1:2224'.
    [2006-06-07 10:26:53.543] Status 1: NOD32 Installer is installing NOD32.
    [2006-06-07 10:26:57.768] Status 1012: Failure during NOD32 install - exit code: 121.

    Please help.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hello,

    please run the installer eset/install/setup.exe with the /test parameter manually on that computer, and send the log nsetup.log to support[at]eset.com with a link to this thread.
     
  3. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Hi
    I've seen similar things. I've tried a few options, reinstall file and printer sharing, disabeling firewall and that kind of stuff, but didn't work

    So, instead of inventing a wheel again, i did a pull install from the command line of the client PC via:
    start, execute: \\"share"\nod32\NT\setup.exe /silentmode /reboot /cfg=\\"share"\nod32\config2.xml

    that works perfectly well. But you'll have to create an .XML file first and put it in a share before you can use this option.
    Alternatively, you can install without using the config file and only add /silentmode / reboot.

    Greetings from Holland
     
  4. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands

    Hi Marcos that's a good idea, I didnt know that option :eek:
    so I'm still learning every day :D

    greetings from Holland
     
  5. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    Thanks for the advice...

    When I run the manual install it works, but I then have to go through all the setup options. Do you want me to simply do a "Typical Install" with the /test paramater & then send the log?
     
  6. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    When I try to run the following command:
    \eset\install\setup.exe /test /cfg=\\t:\Program Files\eset\ra\server\my profile.xml - The setup comes up fine & I can install fine.

    When I try to run the package I created:
    \eset\RA\server\packages\issidefault\nod32installer.exe /test /cfg=\\t:\Program Files\eset\ra\server\my profile.xml - It does nothing & then in my nod32installer.log file I have this:

    [2006-06-07 12:44:48.754] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 12:44:48.754] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 12:44:48.770] Status 1: NOD32 Installer is sending installation request.
    [2006-06-07 12:44:48.770] Status 20000: NOD32 Installer was told to quit by the server 'ISSIHQ1:2224'.

    I can do a manual install, but I don't want to...I want the program to execute the remote install for me...that's that whole point isn't it?? ;)
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Yes, that's the point. However, if there is a problem installing specific component and the install fails, there's no way than to install it manually and create a log from the installation which will shed more light.

    The message "Installer was told to quit by the server" means that the installer has already sent a signal to RAC about installation so RAC will not try to push it again. You can try removing installation leftovers using RAC in order to be able to re-install NOD32.
     
  8. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    How do I "remove installation leftovers using RAC"?

    I have run the reg key that eset support sent me & have deleted the Program Files\Eset directory. Here's the guts of that reg key:

    REGEDIT4

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Eset]
    [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AMON]
    [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NOD32krn]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
    "nod32kui"=-
    [-HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_CLASSES_ROOT\CLSID\{B089FE88-FB52-11d3-BDF1-0050DA34150D}]
    [-HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_CLASSES_ROOT\Drives\Shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B089FE88-FB52-11d3-BDF1-0050DA34150D}]
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drive\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Drives\Shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shellex\ContextMenuHandlers\NOD32 Context Menu Shell Extension]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved]
    "{B089FE88-FB52-11d3-BDF1-0050DA34150D}"=-

    Is there something else I have to do in the RAC?
     
  9. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    After cleaning all that info out of my workstation & trying the install again via:

    \eset\RA\server\packages\issidefault\nod32installer.exe /test /cfg=\\t:\Program Files\eset\ra\server\my profile.xml

    I get this in my nod32installer.log file:

    [2006-06-07 13:13:38.321] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 13:13:38.321] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 13:13:38.321] Status 1: NOD32 Installer is sending installation request.
    [2006-06-07 13:13:38.967] Status 1: NOD32 Installer is preparing to install.
    [2006-06-07 13:13:38.967] Status 1: NOD32 Installer is trying to connect to 'ISSIHQ1:2224'.
    [2006-06-07 13:13:38.967] Status 1: NOD32 Installer is creating a temporary file.
    [2006-06-07 13:13:38.967] Status 1: NOD32 Installer is downloading an installation package 'issidefault' from server 'ISSIHQ1:2224'.
    [2006-06-07 13:13:39.140] Status 1: NOD32 Installer is installing NOD32.
    [2006-06-07 13:13:44.858] Status 1012: Failure during NOD32 install - exit code: 121.
    [2006-06-07 13:13:46.087] Status 1012: Failure during NOD32 install - exit code: 121.

    So now what do you think the problem is? I'm at a total loss.
     
  10. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    Hi mattjabs,
    Now that you have run using the /test switch, you will be able to send the nsetup.log as Marcos requested in post#2

    Cheers :)
     
  11. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Just to check, is there any other anti-virus or security software (or policies) running on the target computer which could be interfering with the remote installation? This could include things such preventing access to the registry and the temporary file folders.

    Regards,

    Aryeh Goretsky
     
  12. mattjabs

    mattjabs Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    6
    On the computer I was trying to install on, I moved my default profile directory to D:\profiles. I partitioned my HDDs & made the C: (sysvol) partition 7.8MBs & the D: (data) partition the remainder of the drive. I didn’t want the profiles taking up too much space on the C: drive, so I moved them to D:\profiles. I think this is probably the issue we’re running into.

    What do you think?
     
  13. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Check the TEMP / TMP user and system variables and make sure they point to the new location of the temporary folders.
     
Thread Status:
Not open for further replies.