GroupShield update failures

[NickFerrar]

We have GroupShield 5.2 on Exchange 2000 and 5.0 on Exchange 5.5, as well as McAfee command line scanner running on an SMTP gateway box.

Around the middle of April these all stopped being able to update their DAT files and I've been unable to resolve it so far. The Exchange 2000 box has DAT 4466 and the Exchange 5.5 box has 4473 - if I run updates on these it seems to go through until the very end and then fails with the unhelpful message:

"The update service failed to update the .dat files." but with no useful diagnostic info anywhere. I've been unable to try a server reboot but does anyone know if something changed with the DAT file format or something around mid-April? Our ePO v3.5 and VS8.0i clients are receiving and updating their DATs just fine (in fact the Exchange 2000 server has VS7 on it and it has the latest DAT to).

I have a call logged with McAfee so should get a response soon but it just seems too big of a coincidence to me that 3 systems that have been updating fine for months should suddenly start to fail within a few days of each other.

Also when the Groupshield update fails it leaves a 5MB folder, we had a couple of GB's worth of these as we try updating every hour!

 

[epochap]

Hi,

We have the same issue on GS5.2 with Exchange2003.

What version of scan engine you have? The older scan engine (example: 4.2.60) does not allow the DAT updation to happen (As far as i know),.

The only way to update the scan engine is to Run the SDat file. We need to try that yet.

 

[NickFerrar]

It works intermittently for us but we're in the process of migrating to Exchange 2003 and GS 6 so I haven't bothered trying some tests/fixes McAfee sent me.