Install error in Nod32?

Discussion in 'NOD32 version 2 Forum' started by Zipp, Oct 12, 2005.

Thread Status:
Not open for further replies.
Page 2 of 3
  1. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    I have only seen the method described above fail on Service Pack 1.

    No, it refers to this page and WinsockXPfix

    Cheers :D
     
    Blackspear, Dec 6, 2006
    #26
  2. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    I should refer to step 1, step 2, then WinsockXPfix

    or step X and WinsockXPfix is alternative ?
     
    a1s1, Dec 6, 2006
    #27
  3. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Download and run WinsockXPfix, then reboot when requested, then start IMON.

    Cheers :D
     
    Blackspear, Dec 6, 2006
    #28
  4. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    I'm sorry , I have not installed nod32, because it display :121 Nod32Mod Winnt English

    so my question is not how to repair IMON ,just how to installed nod32.

    and I tried the step X method and WinsockXPfix method , nod32 still can not be installed.
     
    a1s1, Dec 6, 2006
    #29
  5. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Repair Winsock and then install NOD32, don't worry about repairing IMON because NOD32 isn't installed when you are repairing Winsock.

    Cheers :D
     
    Blackspear, Dec 6, 2006
    #30
  6. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    download and run WinsockXPfix, then reboot, and then install NOD32.

    but unlucky, it still display : 121 Nod32Mod Winnt English

    sigh, I want to give it up, maybe something is wrong with my computer

    anyway, thank you very much
     
    a1s1, Dec 6, 2006
    #31
  7. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    I forget... is this error message the one caused by a missing TEMP folder, or is it some other error message?

    Just in case... try making sure that your computer has the following folders. If they are not present, then the NOD32 installer cannot extract the files to run the installation. If they are not there, create them yourself and try installing again.

    C:\Windows\Temp
    C:\Documents and Settings\username\Local Settings\Temp

    These folders may be hidden from normal view, so you may have to go to Control Panel --> Folder Options --> View --> "Show hidden files and folders" to get them to show up.
     
    alglove, Dec 6, 2006
    #32
  8. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    The two folders are there,so I don't why
     
    a1s1, Dec 6, 2006
    #33
  9. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    If repairing Winsock and removing and replacing the Temp folder has not resolved the issue I would be formatting and reinstalling Windows.

    Cheers :D
     
    Blackspear, Dec 7, 2006
    #34
  10. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Are the folders empty? If not, try emptying them and try again. It could be that the leftovers from some other installation program are interfering with the NOD32 installer.
     
    alglove, Dec 7, 2006
    #35
  11. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    The supporter tell me to install nod32 in Expert mode. After having installed it, the nod32 control center is blank.
     
    a1s1, Dec 8, 2006
    #36
  12. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Strange. Try running the NOD32 installer in "test" mode.
    • Go to Start --> All Programs --> Accessories --> Command Prompt.
    • Type "C:\Program Files\ESET\Install\setup.exe" /test . (with the quotes)
    • This will write a log to C:\Program Files\ESET\Install\nsetup.log .
    • Copy the contents of this log file here so we can look for errors.
     
    alglove, Dec 8, 2006
    #37
  13. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14
    [2006-12-09 14:53:37.031] Is program installed?
    [2006-12-09 14:53:37.031] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - c:\program files\eset\install\setup.xml
    [2006-12-09 14:53:37.031] Registry: old settings read
    [2006-12-09 14:53:37.078] global.xml created
    [2006-12-09 14:53:37.078] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\global.xml
    [2006-12-09 14:53:37.078] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - c:\program files\eset\install\setup.xml
    [2006-12-09 14:53:37.078] Main settings added
    [2006-12-09 14:53:37.078] Engines nups
    [2006-12-09 14:53:37.078] InstallPath added
    [2006-12-09 14:53:37.078] LogPath added
    [2006-12-09 14:53:37.406] EngineFile extracted
    [2006-12-09 14:53:37.437] EngineFile extracted
    [2006-12-09 14:53:37.468] EngineFile extracted
    [2006-12-09 14:53:37.484] EngineFile extracted
    [2006-12-09 14:53:37.500] EngineFile extracted
    [2006-12-09 14:53:37.531] EngineFile extracted
    [2006-12-09 14:53:37.875] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpa\setupc.xml
    [2006-12-09 14:53:37.875] SetupAddComponentDescToGlobal
    [2006-12-09 14:53:37.890] Component added
    [2006-12-09 14:53:37.890] Componet libraries
    [2006-12-09 14:53:38.515] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpb\setupc.xml
    [2006-12-09 14:53:38.531] SetupAddComponentDescToGlobal
    [2006-12-09 14:53:38.531] Component added
    [2006-12-09 14:53:38.546] Componet libraries
    [2006-12-09 14:53:38.796] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpc\setupc.xml
    [2006-12-09 14:53:38.796] SetupAddComponentDescToGlobal
    [2006-12-09 14:53:38.796] Component added
    [2006-12-09 14:53:38.796] Componet libraries
    [2006-12-09 14:53:39.000] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpd\setupc.xml
    [2006-12-09 14:53:39.000] SetupAddComponentDescToGlobal
    [2006-12-09 14:53:39.000] Component added
    [2006-12-09 14:53:39.000] Componet libraries
    [2006-12-09 14:53:39.078] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\global.xml
    [2006-12-09 14:53:39.140] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2006-12-09 14:53:39.140] - krnstp.dll
    [2006-12-09 14:53:39.156] - ps_upd.dll
    [2006-12-09 14:53:39.156] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2006-12-09 14:53:39.156] - ps_amon.dll
    [2006-12-09 14:53:39.171] - ps_nod32.dll
    [2006-12-09 14:53:39.171] - ps_dmon.dll
    [2006-12-09 14:53:39.171] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_ADMIN
    [2006-12-09 14:53:39.187] - ps_mirr.dll
    [2006-12-09 14:53:39.187] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_INET
    [2006-12-09 14:53:39.187] - imon.dll
    [2006-12-09 14:53:39.203] - ps_emon.dll
    [2006-12-09 14:53:39.234] ExeLibs: Init
    [2006-12-09 14:53:39.437] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2006-12-09 14:53:39.437] - krnstp.dll
    [2006-12-09 14:53:39.453] - ps_upd.dll
    [2006-12-09 14:53:39.453] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2006-12-09 14:53:39.453] - ps_amon.dll
    [2006-12-09 14:53:39.468] - ps_nod32.dll
    [2006-12-09 14:53:39.468] - ps_dmon.dll
    [2006-12-09 14:53:39.484] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_ADMIN
    [2006-12-09 14:53:39.484] - ps_mirr.dll
    [2006-12-09 14:53:39.484] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_INET
    [2006-12-09 14:53:39.484] - imon.dll
    [2006-12-09 14:53:39.500] - ps_emon.dll
    [2006-12-09 14:53:39.500] ExeLibs: Load Current State
    [2006-12-09 14:53:39.500] Error: Couldn't open Administrator's XML : nod32.xml
    [2006-12-09 14:53:56.453] Registry: root written
    [2006-12-09 14:53:56.453] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\global.xml
    [2006-12-09 14:53:56.703] SetupCopyFiles
    [2006-12-09 14:53:56.703] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2006-12-09 14:53:56.703] - krnstp.dll
    [2006-12-09 14:53:56.984] - ps_upd.dll
    [2006-12-09 14:53:57.250] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2006-12-09 14:53:57.250] - ps_amon.dll
    [2006-12-09 14:53:57.843] - ps_nod32.dll
    [2006-12-09 14:53:58.125] - ps_dmon.dll
    [2006-12-09 14:53:58.140] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_ADMIN
    [2006-12-09 14:53:58.140] - ps_mirr.dll
    [2006-12-09 14:53:58.250] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_INET
    [2006-12-09 14:53:58.250] - imon.dll
    [2006-12-09 14:53:59.671] XML_ACCESS: C:\Documents and Settings\zhaohuabiao - C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\global.xml
    [2006-12-09 14:54:00.578] Deleting directory: C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\NSetup\
    [2006-12-09 14:54:00.625] Deleting directory: C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpa\
    [2006-12-09 14:54:00.656] Deleting directory: C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpb\
    [2006-12-09 14:54:00.687] Deleting directory: C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpc\
    [2006-12-09 14:54:00.718] Deleting directory: C:\DOCUME~1\ZHAOHU~1\LOCALS~1\Temp\nodtmpd\
    [2006-12-09 14:54:00.734] Exitcode: 121 NOD32MOD_WINNT_ENGLISH_INET
     
    a1s1, Dec 9, 2006
    #38
  14. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    I noticed this line:
    This seems to say that remnants of an earlier version of NOD32 may in your Windows registry, and could possibly causing problems. Try going to Add/Remove Programs, uninstall NOD32, and reboot.

    Once you get back into windows, open up the Windows registry editor by going to Start --> Run... and typing in regedit . On the left side, look for HKEY_LOCAL_MACHINE\Programs\Eset . There should not be one, since you just uninstalled. If there is, then highlight Eset and hit the Delete key on your keyboard.

    Now try reinstalling and see what happens.
     
    alglove, Dec 9, 2006
    #39
  15. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    There isn't any "eset" in the registry. But the log is same with above.
     
    a1s1, Dec 9, 2006
    #40
  16. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14
    Now i installed it in "safe" mode

    but the IMON is not run

    and the setup--repair is gray.
     
    a1s1, Dec 9, 2006
    #41
  17. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    This points back to your Winsock Layer being corrupt. I would try repairing Winsock again.

    Cheers :D
     
    Blackspear, Dec 10, 2006
    #42
  18. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    Download and run WinsockXPfix, then reboot when requested


    then still cannot start IMON
     
    a1s1, Dec 10, 2006
    #43
  19. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Please try the following, it will require the Windows XP CD-ROM:

    1. From the Start menu, select Run.
    2. In the Open field, type sfc /scannow (Note: There is a space between sfc and /scannow)
    3. Select the OK button.
    4. Follow the prompts throughout the System File Checker process.
    5. Reboot the computer when System File Checker completes.

    Cheers :D
     
    Blackspear, Dec 10, 2006
    #44
  20. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14
    The situation is the same with above.

    Then I run WinsockXPfix, but it still the same

    Oh ,my God
     
    a1s1, Dec 11, 2006
    #45
  21. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Like I said previously, if it was mine, I would be formatting and stating again. Fresh install of Windows, don't add anything except NOD32 and it will install without a doubt.

    Blackspear.
     
    Blackspear, Dec 11, 2006
    #46
  22. a1s1

    a1s1 Registered Member

    Joined:
    Dec 6, 2006
    Posts:
    14

    Giving up is another decision!!
     
    a1s1, Dec 11, 2006
    #47
  23. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    On a hosed system, yes. Fresh install will resolve the issue which is localized to your particular machine.

    Blackspear.
     
    Blackspear, Dec 11, 2006
    #48
  24. apoto

    apoto Registered Member

    Joined:
    May 19, 2007
    Posts:
    4
    Location:
    Moscow/Petersburg
    120: Error occured while registering the service

    hi, i have same problem with install any version nod32:
    error 120: Error occured while registering the service NOD32MOD...
    There isn't any "nod32" in the registry, but in services are present nod32kernel in state "OFF". i also used winsockfix, sfc and simply winsock reset.
    i don't know what i can do anymore!
    Help plz! i want use nod32 on my current system w/o full reinstall:oops:

    sorry for my English)

    Install log:
    [2007-05-19 13:35:59.343] CmdLine: /test
    [2007-05-19 13:35:59.343] Resource: main.dll
    [2007-05-19 13:35:59.343] Is program installed?
    [2007-05-19 13:35:59.343] XML_ACCESS: C:\Program Files\ESET\Install - C:\Program Files\ESET\Install\setup.xml
    [2007-05-19 13:35:59.343] Registry: old settings read
    [2007-05-19 13:35:59.359] global.xml created
    [2007-05-19 13:35:59.359] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:35:59.359] XML_ACCESS: C:\Program Files\ESET\Install - C:\Program Files\ESET\Install\setup.xml
    [2007-05-19 13:35:59.359] Main settings added
    [2007-05-19 13:35:59.359] Engines nups
    [2007-05-19 13:35:59.359] InstallPath added
    [2007-05-19 13:35:59.359] LogPath added
    [2007-05-19 13:36:00.781] EngineFile extracted
    [2007-05-19 13:36:00.796] EngineFile extracted
    [2007-05-19 13:36:00.812] EngineFile extracted
    [2007-05-19 13:36:00.812] EngineFile extracted
    [2007-05-19 13:36:00.812] EngineFile extracted
    [2007-05-19 13:36:00.828] EngineFile extracted
    [2007-05-19 13:36:01.109] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:01.109] SetupAddComponentDescToGlobal
    [2007-05-19 13:36:01.109] Component added
    [2007-05-19 13:36:01.109] Componet libraries
    [2007-05-19 13:36:01.468] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:01.468] SetupAddComponentDescToGlobal
    [2007-05-19 13:36:01.468] Component added
    [2007-05-19 13:36:01.468] Componet libraries
    [2007-05-19 13:36:01.765] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:01.765] SetupAddComponentDescToGlobal
    [2007-05-19 13:36:01.765] Component added
    [2007-05-19 13:36:01.765] Componet libraries
    [2007-05-19 13:36:01.937] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:01.937] Admin settings added
    [2007-05-19 13:36:01.937] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2007-05-19 13:36:01.937] - krnstp.dll
    [2007-05-19 13:36:01.953] - ps_upd.dll
    [2007-05-19 13:36:01.953] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2007-05-19 13:36:01.953] - ps_amon.dll
    [2007-05-19 13:36:01.953] - ps_nod32.dll
    [2007-05-19 13:36:01.953] - ps_dmon.dll
    [2007-05-19 13:36:01.968] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_INET
    [2007-05-19 13:36:01.968] - imon.dll
    [2007-05-19 13:36:01.968] - ps_emon.dll
    [2007-05-19 13:36:01.968] ExeLibs: Init
    [2007-05-19 13:36:01.968] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2007-05-19 13:36:01.968] - krnstp.dll
    [2007-05-19 13:36:01.968] - ps_upd.dll
    [2007-05-19 13:36:01.984] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2007-05-19 13:36:01.984] - ps_amon.dll
    [2007-05-19 13:36:01.984] - ps_nod32.dll
    [2007-05-19 13:36:01.984] - ps_dmon.dll
    [2007-05-19 13:36:02.000] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_INET
    [2007-05-19 13:36:02.000] - imon.dll
    [2007-05-19 13:36:02.000] - ps_emon.dll
    [2007-05-19 13:36:02.015] ExeLibs: Load Current State
    [2007-05-19 13:36:02.015] Error: Couldn't open Administrator's XML : nod32.xml
    [2007-05-19 13:36:15.406] Registry: root written
    [2007-05-19 13:36:15.406] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:15.484] SetupCopyFiles
    [2007-05-19 13:36:15.500] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
    [2007-05-19 13:36:15.500] - krnstp.dll
    [2007-05-19 13:36:15.656] - ps_upd.dll
    [2007-05-19 13:36:15.734] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
    [2007-05-19 13:36:15.734] - ps_amon.dll
    [2007-05-19 13:36:15.750] AMONPLG Status: Install case begin
    [2007-05-19 13:36:15.750] AMONPLG Status: InstallDriver - InstallDriver ChangeServiceConfig 87
    [2007-05-19 13:36:15.750] AMONPLG Status: InstallDriver C:\Program Files\Eset\ps_amon.dll
    [2007-05-19 13:36:17.375] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\[2007-05-19 13:36:17.515] Deleting directory: C:\DOCUME~1\[2007-05-19 13:36:17.531] Deleting directory: C:\DOCUME~1\[2007-05-19 13:36:17.531] Deleting directory: C:\DOCUME~1\[2007-05-19 13:36:17.531] Deleting directory: C:\DOCUME~1\[2007-05-19 13:36:17.546] Exitcode: 120 NOD32MOD_WINNT_ENGLISH_STANDARD
     
    apoto, May 19, 2007
    #49
  25. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Re: 120: Error occured while registering the service

    Hi there, welcome to Wilders.

    What previous antivirus was on this system?

    Cheers :D
     
    Blackspear, May 19, 2007
    #50
Page 2 of 3
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...