Lately, I seem to have the incremental updates failing at some point. There is nothing obvious in the logs:
4/13/2010 11:27:47 AM BENS-CAF4\Andy Starting DAT update.
4/13/2010 11:27:48 AM BENS-CAF4\Andy Downloading DAT.
4/13/2010 11:27:48 AM BENS-CAF4\Andy Downloading gdeltaavv.ini.
4/13/2010 11:27:48 AM BENS-CAF4\Andy Downloading 59495950avv.gem.
4/13/2010 11:28:44 AM BENS-CAF4\Andy Backing up file(s) Engine DAT
4/13/2010 11:28:53 AM BENS-CAF4\Andy Pre-notifying for DAT update.
4/13/2010 11:28:53 AM BENS-CAF4\Andy Copying DAT.
4/13/2010 11:29:00 AM BENS-CAF4\Andy Update failed to version 5950.0000.
4/13/2010 11:29:04 AM BENS-CAF4\Andy Update Finished
4/13/2010 11:29:34 AM BENS-CAF4\Andy Closing the update session.
If I rerun the update, it then ends up downloading the full ZIP:
4/13/2010 11:30:42 AM BENS-CAF4\Andy Downloading DAT.
4/13/2010 11:30:42 AM BENS-CAF4\Andy Downloading gdeltaavv.ini.
4/13/2010 11:30:43 AM BENS-CAF4\Andy Downloading 59495950avv.gem.
4/13/2010 11:30:46 AM BENS-CAF4\Andy Downloading avvdat-5950.zip.
4/13/2010 11:32:30 AM BENS-CAF4\Andy Backing up file(s) Engine DAT
4/13/2010 11:32:41 AM BENS-CAF4\Andy Pre-notifying for DAT update.
4/13/2010 11:32:41 AM BENS-CAF4\Andy Copying DAT.
4/13/2010 11:32:47 AM BENS-CAF4\Andy Update succeeded to version 5950.0000.
4/13/2010 11:32:47 AM BENS-CAF4\Andy Post-notifying for DAT update.
4/13/2010 11:33:37 AM BENS-CAF4\Andy Update Finished
4/13/2010 11:34:08 AM BENS-CAF4\Andy Closing the update session.
After that happens, I've noticed that Outlook will take much longer to start up. Even booting up is slower. That will keep happening until the next incremental update is successful.
It's not a major issue, more of an annoyance. I wonder if anybody has noticed it happening more often lately? It used to be rare, but has happened 3 times in the past week.
This is with 8.5i, Patch 5, Win2K, no ePO or other. Just a stand-alone installation.
I am not sure if Patch5 already allows incremental updates of the V2 Dat files (V1 Dat files have been terminated last week). So I recommend you to update first to Patch8, as it also fixes many many other bugs.
You can download it under the Enterprise section with your Grant number.
IIRC, V 8.5i supported V2 dat incremental updates since it was first released. (Actually, the beta did too ... )
I have seen quite a few posts recently indicating issues since Mar 31 with updating dat files. I'm interested if they are related, or just the usual backgroun traffic that happens.
Are you able to post your AGENT_<Computername>.log file and the MCSCRIPT.log? Under WinXP etc, it should be located in C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\DB m under Win Vista/Win 7 etc, the path will be different.
Note the files can contain some sensitive data (eg IP addresses of updating servers etc) , so you probably want to review it before posting.Message was edited by: Mal09 on 14/04/10 17:33:25 GMT
I found the log (it's under Network Associates, not McAfee). It's not too different than what the regular log shows.
20100413112844 i #880 Script Backing up file(s) Engine DAT
20100413112852 i #880 Script Pre-notifying for DAT update.
20100413112852 i #2332 Script Copying DAT.
20100413112900 i #880 Script Update failed to version 5950.0000.
20100413112904 i #2332 Script Update Finished
20100413112934 i #2380 Script Closing the update session.
Today's update went fine.I also noticed there was a BOC update, to 499, too.
Grr @ McAfee. Couldn't they at least warn people when BOC updates are due to occur? While dat updates are normally outside of the scope of change control etc, things like Engines and BOC updates often fall under the jurisdiction of change management.
Rant over. Now back to your issue:
I would have thought the logs would give more details about the error. It is frustrating when these sorts of things occur and the logs don't help. There are higher diagnostic switches available to give more information, but that's more what Support will ask for rather than something I can easily interpret.