Error when updating virus sig database!

[Tom Tucky]

I'm asking in this forum because I've sent Eset five support requests in the past week, and I've not gotten any response.

Whenever I attempt to update the virus signature database, whether through an automated process or manual event, I get the following error message:

Time Module Event User
6/15/2004 20:14:02 PM Update Error occured while updating program modules (Cannot replace the current file.)

When I trigger the update, I see a series of files get downloaded into the ESET\updfiles subdirectory. The update then creates a file nod32.xxx in the Eset directory, and immediately afterward I get this error.

I've tried disabling the AMON and IMON modules, and it makes no difference. As nearly as I can tell from enabling auditing on this directory, the error comes from trying to replace nod32krn.exe. I can find no documentation that either describes this error or a workaround.

Windows XP Pro SP1, service running under the LocalSystem account, which has "Full Control" access to all the Eset files.

I have purchased NOD32. The program can access and download the updates, it just cannot complete the process.

[Tom Tucky]

My system information, for what it's worth:

NOD32 Antivirus System information
Virus signature database version: 1.578 (20031212)
Dated: Friday, December 12, 2003
Virus signature database build: 4104

Information on other scanner support parts
Advanced heuristics module version: 1.004 (20031028)
Advanced heuristics module build: 1037
Internet filter version: 1.001 (20031104)
Internet filter build: 1012
Archive support module version: 1.008 (20031127)
Archive support module build version: 1078

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.9
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.9

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 1
Version of common control components: 5.82.2800
RAM: 1024 MB
Processor: Intel(R) Pentium(R) 4 CPU 3.20GHz (3214 MHz)

[ronjor]

{QUOTE-> I'm asking in this forum because I've sent Eset five support requests in the past week, and I've not gotten any response.

Whenever I attempt to update the virus signature database, whether through an automated process or manual event, I get the following error message:

Time Module Event User
6/15/2004 20:14:02 PM Update Error occured while updating program modules (Cannot replace the current file.)

When I trigger the update, I see a series of files get downloaded into the ESET\updfiles subdirectory. The update then creates a file nod32.xxx in the Eset directory, and immediately afterward I get this error.

I've tried disabling the AMON and IMON modules, and it makes no difference. As nearly as I can tell from enabling auditing on this directory, the error comes from trying to replace nod32krn.exe. I can find no documentation that either describes this error or a workaround.

Windows XP Pro SP1, service running under the LocalSystem account, which has "Full Control" access to all the Eset files.

I have purchased NOD32. The program can access and download the updates, it just cannot complete the process. <-QUOTE}


I did a search on this forum for error occured--------

http://www.wilderssecurity.com/search.php?searchid=41037

[rumpstah]

The easiest fix may be to uninstall NOD32, delete the ESET directory under Program files (after reboot) and reinstall. You may have a corrupted installation file. I would also download the commercial version again before installing. If you have download accelerators I would turn them off. 8)

[DiGi]

Check that default SYSTEM TEMP folder is exists (eg: c:\winnt\temp - NOT user temp (c:\documents and settings\user\...\temp))

[Marcos]

What address did you send the request to? I suggest you send it directly to support@nod32.com.

[-_-]

I can confirm this problem.

Uninstalling & reinstalling NOD32 did not help.

I solved this issue in the following way:

1. I installed NOD32 on a virtual machine and made an update.

2. I copied the files of the updated NOD32 installation to the original installation which could not be updated.

(It goes without saying that a normal user won't like to update NOD32 in this way.)

[Marcos]

It happens if the file NOD32.000 gets corrupted for some reason (e.g. a disk error). The following should remedy the problem:
- restart Windows in safe mode
- delete the file nod32.000
- restart Windows in normal mode ignoring the error loading resident protection
- update NOD32
- reboot

However, the easiest way would be to reinstall NOD32 (the installation files are pertained in the eset/install directory).

[DiGi]

Hey, does your TEMP folder exist? I had exactly SAME bug and it was by removed c:\winnt\temp...

[Mele20]

Did you fill in that support request on Nod32's support page? If so, that is a bad way to get support in my experience. Always send emails to support@nod32.com using your email client. Turn off any spam filtering that requires authentication. Be sure to include information from NOD32 System Tools/information in order to speed up help.