I have an issue with 3 servers running VirusScan Enterprise 8.7, none of them will auto update to the latest definitions unless I use the SDAT manually.
The common issue i have noticed with the 3 is that the 'Buffer Overflow and Access protection DAT Version' is at 422 whereas all my other servers are running 516.
Has anyone else seen/resolved this issue?
Do you have the issue only with BOP update?
What about DAT/Engine? Is it showing latest one and only BOP DAT is showing older one?
How long have the servers been experiencing the updating issue? If it has been for a while, it could be that they were unable to update their BOP dat correctly via autoupdate either.
When you run a manual update, what errors do you get? Are they able to connect to the repository etc.Message was edited by: Katalyst on 17/06/11 6:35:13 AM
One of them has been doing it for about a year, the other two are since Feb this year.
I will confirm the exact error when I get to work but when I run autoupdate, its finds the repository, gets down to the point there it would update using the .gem files then says something along the line of 'unable to find qualifying product'
AndyMessage was edited by: andynic on 17/06/11 00:41:22 CDT
in any update related problems, please find McScript.log on the client, open it, locate the update time and scroll down to find error messages (sorry if you did it already). This is another, more detailed log than Updatelog.txt in %DEFLOGDIR% folder.
You may post it here for us to have a look at.
Some additional error messages can be get to be shown in McScript.log if you employ techniques described in KB58966. It is advised to at least perform setting LogLevel 8 and do another update manually, before you would post the log here.
Unfortunately I cant post the script (or find it for that matter!) Will carry on looking, but for now...
Looking at the UpdateLog.txt, when it gets to 'Verifying V2datdet.msc' you should see 'Downloading pkgcatalog.z' and then the new update files, however we are getting 'Unable to find any qualifying product (s).
My usual technique (rather odd, you might say) to find files (which are not hidden) is to open a CMD window, and for every root folder (C:\, D.\, etc.) I issue the "dir filename /s /p" command, it should find the file rather quickly.
This log should be by default on drive C:
On my XP machine its in drive:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Db