Those DATs are REALLY OLD! (Approximately 6 or 7 months old.) We're currently on 5409 and if you haven't updated the dats, then it's possible your computer is infected..
So is the scan engine.. We're now at 5300 scan engine..
So is your VS 7.1 Enterprise version. It is no longer supported and you'll need to have VS 8.5i or later to be supported by McAfee..
Unfortunately, many users of VS 7.1 are having similar issues with the newest DATs.. I'll assume it's because your version of VS is no longer supported.. Time to update your antivirus program!
Hope this helps.
we have installed the new super dat the next day and it worked fine now
I get this same error when trying to install sdat5796.exe which I believe is the most up to date version as of Nov, 2009. Its never happened to me with any of the previous versions. Any ideas? I'd be glad to post any additional info required.
Please verify which verson of the ENgine you are running.
I would personally advise you to update to VSE 8.7i which is free of charge with a valid grant number. VSE 80 will reach end of support in Q1 of 2010.
Please let me know if you have any queries
Scan Engine: 5300
Will the update fix the problem? Also I'm not sure what a grant number is or if I have a valid one.
A SuperDAT will bring you up to scratch as far as the newest Engine and AntiVirus signatures are concerned.
A GRANT number entitles you to free product upgrades. Grant numbers are usually valid for one year.
To find out if you havee a grant number contact McAfee Customer Service or Support.For contact details:
- Go to: http://www.mcafee.com/us/about/contact/index.html
- Non-US customers - select your country from the list of Worldwide Offices.
Hi Mr G,
I too have seen this issue today.I get the error Sdstbres.dll ... the specified module could not be found when trying to apply 5806xdat.exe. This is on a system with Agent 22.214.171.1244, VirusScan 8.7 (Patch 2), Host Intrusion 7 (Patch 6)
I am actually trying to apply the SuperDAT because 1 particular client continues to get the following error "File Mase_Det.mcs is corrupt" when running an automatic update. Can you shed any light on this error for me?
Regarding this error, it tells me the SDAT package is getting confused when trying to execute - and fails to find the .dll it extracted at run-time.
Why? Who knows. SuperDATs are an old technology and susceptible to failure if your environment isn't pristine.
As you noted, it worked the next day. So, something environmental changed - it wasn't the internal workings of the package.
If you wanted to, you can run Process Monitor next time this occurs, and see where the package actually puts the files when it executes vs. where it goes looking for the file - and see if you can deduce why it might be looking where it does.
Where the package is run from, path statements, other environment variables, these could be relevant to the cause.
For the error "File Mase_Det.mcs is corrupt" when running an automatic update", if this was soon followed by a successful retrieval of the file, it can be ignored.
And if you don't use the anti-spyare product, it can also be ignored (or removed from your repository). The error is logged by the Agent, however, so if it needs further investigation you would want to engage that team.