(2.7) Weekly Scheduled Scan - Stuck at "Cleaning"

[Capp]

Hey guys,
I have the v2.7 running. I have mine set to do a full system scan early every monday morning. I've never had a problem, and I'm not sure i have one now.

I checked the scanner logs and it seems the one that started at 6am this morning's status still says "Cleaning".

I opened up the log and it doesn't show a scan summary at the bottom like it normally does. I've attached a screenshot to better depict what I'm talking about.

Besides just doing a system reboot, anybody seen this before or know if this is a problem?

Thanks


P.S. just for the huddled masses, here is my information from NOD32:

NOD32 antivirus system information
Virus signature database version: 2110 (20070312)
Dated: Monday, March 12, 2007
Virus signature database build: 9263

Information on other scanner support parts
Advanced heuristics module version: 1.055 (20070302)
Advanced heuristics module build: 1148
Internet filter version: 1.002 (20040708 )
Internet filter build: 1013
Archive support module version: 1.052 (20070115)
Archive support module build version: 1179

Information about installed components
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
Version: 2.70.16
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
Version: 2.70.16
NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
Version: 2.70.16

Operating system information
Platform: Microsoft Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 640 MB
Processor: AMD Athlon(tm) Processor (1050 MHz)

[Thankful]

This is the closest I could recall:
http://www.wilderssecurity.com/showthread.php?t=120256

I eventually did an uninstall; run CCleaner; run RegSeeker; Remove Eset folder; restart;
reinstall NOD32

Hope that helps.

[Marcos]

I'd suggest you navigate to the program files/eset folder and run "nod32.exe c: f: /arch+ /pack+ /all /crashlog". When the scanner closes before completing the scan, open crash.log created in the eset folder and send the last file opened to support [at] eset.com along with a short description of the problem.

[Capp]

Thanks Marcos.

I checked and there is a crash.log from the 6am scanning. It appers to have stalled on the NT backup catalogs folder.

I'll submit the last line and a brief description as recommended above.

Thanks for the help


*edit* Email sent with pertinent information

[Capp]

The last 2 weekly scheduled scans have done the same thing: They still say "Cleaning".

Here is the system info for nod32:

NOD32 antivirus system information
Virus signature database version: 2379 (20070704)
Dated: Wednesday, July 04, 2007
Virus signature database build: 10256

Information on other scanner support parts
Advanced heuristics module version: 1.062 (20070630)
Advanced heuristics module build: 1159
Internet filter version: 1.002 (2004070
Internet filter build: 1013
Archive support module version: 1.053 (20070524)
Archive support module build version: 1189

Information about installed components
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
Version: 2.70.32
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
Version: 2.70.32
NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
Version: 2.70.32

Operating system information
Platform: Microsoft Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 640 MB
Processor: AMD Athlon(tm) Processor (1050 MHz)

Any ideas?
Thanks

[Blackspear]

I have seen it on my own system but never found a solution.

Cheers

[XN04113]

Hi,

please check if your harddisk have a file LARGER then 4GB. On one of our application server we had a log file that was 4.1GB in size and nod32 stopped there every time with logging "cleaning". Killed the file and everything was ok.

regards
mike