This content has been marked as final. Show 6 replies
havnt seen that one before.
what engine version and what patch level are you using?
You may want to download the engine upadte 5200eng.exe and run this first then try a dat update using xdat (or download the superdat from here http://www.mcafee.com/apps/downloads/security_updates/superdat.asp?region=uk&seg ment=enterprise which contains the dats and engine in one package)
McAfee has just posted a knowledge base article number 613987 that seems to refer to the error that you are getting.
Below is the article:
Error: Unrecognized command in script file : Line XX (when executing a SuperDAT)
McAfee SuperDAT Manager 2.1
McAfee VirusScan Enterprise
McAfee GroupShield for Exchange
McAfee WebShield SMTP
McAfee VirusScan Multiplatform
McAfee ePolicy Orchestrator
McAfee Protection Pilot
McAfee AutoUpdate Architect
When running a SuperDAT package, the installation of the new DAT fails and the error below is displayed:
Error: Unrecognized command in script file : Line XX
Change or Cause
This issue is caused by an execution timing error related to the size of the SuperDAT package. The larger the SuperDAT package, the more likely this error will occur.
This issue is being investigated for resolution in a future release of SuperDAT Manager. If this issue significantly impacts your business operations, please contact McAfee Technical Support and reference this article number to have a case logged and escalated.
To find the appropriate telephone number for McAfee Technical Support, go to: http://www.mcafee.com/us/about/contact/index.html. Non-US customers select your country from the list of Worldwide Offices.
Alternatively, log a case in the ServicePortal via http://mysupport.mcafee.com. See KB42016 - Creating an online case from ServicePortal.
IMPORTANT: Whenever possible, the automated update mechanism should be used to keep your anti-virus product up-to-date.
Workaround 1 (if you are a Platinum customer using SuperDAT Manager)
Build and execute a smaller SuperDAT package. As this issue is directly related to the size of the SuperDAT package, building a smaller SuperDAT package which contains only v1 DATs (consisting of names.dat, clean.dat and scan.dat), or only v2 DATs (consisting of avvnames.dat, avvclean.dat and avvScan.dat) will resolve the problem.
SuperDAT packages which contain both v1 and v2 DATs are larger in size and are therefore more likely to encounter this issue.
Workaround 2 (if you use a different McAfee solution to update the DAT files and Engine)
If you use one of the following, please update using the relevant deployment software.
McAfee Protection Pilot (PRP)
McAfee ePolicy Orchestrator (ePO)
McAfee AutoUpdate Architect (MAA)
Workaround 3 (if you do not have SuperDAT Manager, PRP, ePO or MAA)
The location from which the SuperDAT is executed can also affect the likelihood of this issue occurring. As this is a timing issue, the error is more likely to occur when a SuperDAT is run from the the root folder of a disk rather than a sub-folder. This is because the additional processing overhead required when running the package from a sub-folder allows the process to complete successfully.
Therefore, to lessen the likelihood of experiencing this issue when executing a large SuperDAT package, ensure that the package is executed from a sub-folder instead of the root folder.
NOTE: Due to differences in computing environments and systems, this workaround may not resolve the issue in all scenarios.
Just a thought... Has everyone tried updating their Windows Script Engine to the newest version.. It may handle the basic DAT package correctly and eliminate the error..
I've manually updated all our W2000 and XP SP2 machines with the new script engine and we're not seeing the error at all.
Windows Script 5.7 for Windows XP
Windows Script 5.7 for Windows 2000
Windows Script 5.7 for Windows Server 2003
Hope this helps.
Thanks for the idea, I’ve done as you suggested and up dated the W2000 machines with the new script engine, but it still fails on our Win2000 PC's.
Oh well... I guess McAfee will need to fix their superdat package.
Thanks for the feedback.
Yes, it was start happen from 5152xdat.
5151xdat is OK.