Van's FSS/Antigen/EOP Blog

My Blog for all Antigen/Forefront Server and Forefront Online Protection for Exchange issues

Microsoft Scan engine failing to update

Microsoft Scan engine failing to update

  • Comments 10
  • Likes

Just as a heads up.

We are seeing cases where the Microsoft scan engine is failing to update in Forefront Protection for Exchange with the following errors.

6019 GetEngineFiles An error occurred while testing the scan engine.

6012 GetEngineFiles An error occurred while loading the scan engine. Scan Engine: Microsoft. Error Code: 0x80004005.

This only seems to be effecting FPE and not other products that the Microsoft engine is included with.

We are working to resolve this issue and it should be resolved automatically once the cause is found. I will update this post if there is any change to how the fix will be delivered.

The only Impact is that the engine fails to update. All other engines are updating correctly and this should not effect mail flow and the other engines should provide coverage for new viruses.

Comments
  • Going forward it would be very useful if a status page could be provided in terms of the current definition file version and known problems.

    Many thanks

    Paul

  • I'm also getting this. I'm using FPSMC for distribution and this fails.

    However I just got one of the Exchange servers to update manually againts the forefrontdl.microsoft.com site and that worked ok.

  • From about 4 hours ago, same problem but with WormList

  • Is there an update for this issue? It seems to be resolved.

  • I 2nd the creating a page that shows the current versions of Engines.

  • For those of us with Antigen for Exchange2003, we started getting the below error on attempts to update "the antigen worm list" engine

    Subject: Failed update of Antigen scan engine on Server (SERVERNAME)

    Expired manifest.

     Please see the Program Log for more information.  

    The status window in the gui then shows (0x80004005)

  • Same here, hoping for a fix in a short time...

  • Does this need to take so long? Its been almost 20 days and still no fix.

  • This issue is still occurring in FPE.

    More than a year and no fix. What a mess!!!

  • Is this issue resolved?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment