Cannot stop the VirusScan 4.5.1 SP1 On-Access Scanner

[Oztokyo]

Cannot stop the On-Access Scanner:

11/1/2001 11:00 SYSTEM XXXXXXX AutoUpdate Task started.
11/1/2001 11:01 SYSTEM XXXXXXX Cannot stop the On-Access Scanner. The .DAT Update cannot continue because the old .DAT files cannot be replaced.

This is widespread with our deployment of VirusScan 4.5.1 SP1 on Windows NT 4.0 and W2K.

HELP!

 

[ts17721]

Please let me@know if you know the solution for this. I have the same problem.

 

[FatesWebb]

what version is your scan engine? js error; 67 on line; 36 of signature.class

 

[kevinnaomi]

I have done extensive research on this, even spoken to Network Associates` engineers, and they can not explain why. They advised to run mcupdate.exe...
Not much of an answer.

 

[AVChap]

Get Hotfix #33 for VirusScan 4.51 SP1. As stated in the README file under resolved issues, check out #2:

RESOLVED ISSUES

ISSUE:
1. Systems with more than one Shell statement (found at [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]) separated by a comma (,), or a Shell statement containing a comma, could cause VirusScan to become unstable if left in a logged off state. VShield icon may be missing after logging in, or Outlook may fail to open correctly.

RESOLUTION:
This HotFix replaces the files AVSYNMGR.EXE, WBHOOK32.DLL, VSSTAT.EXE, and AVCONSOL.EXE, to be updated with instruction on how to accommodate varying Shell values.


ISSUE:
2. During an AutoUpdate, the update fails and logs the error message "Cannot stop the On-Access Scanner. The .DAT Update cannot continue because the old .DAT files cannot be replaced."

RESOLUTION:
This HotFix replaces the files WEBSCANX.EXE, SCANEMAL.DLL and VSSTAT.EXE with newer versions that prevent the AutoUpdate from failing.


ISSUE:
3. When running an on-demand scan on a Danish operating system, the scan fails.

RESOLUTION:
This HotFix replaces the file SCAN32.EXE with a newer version that correctly runs an on-demand scan on a Danish operating system.


ISSUE:
4. On Windows XP, the Windows taskbar disappears when VirusScan is enabled and the Windows taskbar is unlocked.

RESOLUTION:
This HotFix replaces the file VSSTAT.EXE with a newer version that does not cause the taskbar on Windows XP to disappear.


ISSUE:
5. On systems running Windows NT, Windows XP, or Windows 2000, after the system shuts down and displays the shutdown screen, scheduled scans are still launched.

RESOLUTION:
This HotFix replaces the file AVSYNMGR.EXE with a newer version that correctly shuts down VirusScan when the system is shutdown.


ISSUE:
6. If you have configured AutoUpgrade for VirusScan using McAfee ePolicy Orchestrator, and you attempt to edit that task from the VirusScan console, a forward slash (/) is placed in front of the Domain/User information on the client.

NAI19110: "A forward slash is placed in front of Domain/User information of AutoUpgrade task"

RESOLUTION:
This HotFix replaces the file MCUPDATE.EXE with a newer version that does not place a forward slash (/) in front of the Domain/User information on the client.

Call your McAfee rep and SE to help you get this from Technical Support.

HTH,

AVChap

PS: It's just a matter at looking at the right places

 

[Holinwun]

I have the same error message being written to the update log when trying to perform the autoupdate. The difference for me is that it is on an NT4.0 Server running Thin Client 6.0.

Is there a separate hotfix for TC6.0 or will the one released for VS451 also work on TC6.0?

 

[AVChap]

I believe there's already TC 6.1 available. It's available for download on the NAI web site. It should fix this problem. Ask your McAfee rep about this.

HTH, AVChap
... take my advice, I don't use it anyway!

 

[VictorySabre]

Yup, I've seen this problem on my PCs. I even got the Hotfix 33 files... It reduced a large number of update failures, but unfortunately it doesn't fix them all.

I'm also looking to find a reason/solution. Yes, on those PCs that reported the same error mentioned above, I even verified that the hotfix files were present. I raised the issue up with Network Associates, but I was told the fix is 100% effective and that my claims are false.

One thing I did notice on a few of the hotfixed PCs was that when the AutoUpdate was set to run during the day when the user had Outlook or Internet Explorer opened, the updates would fail and report the above error. At the end of the day, the user logs out of NT4 or 2000 and the AutoUpdates that run when the user is not logged in usually works.

Of course there are the stubborn ones that won't work at all until after a reboot.

Anyone know why the hotfix isn't 100% effective?