Microsoft Knowledge Base Email Alertz

Error messages are logged in the Programlog.txt file or in the Application log, and Antigen 9.0 for Exchange does not obtain engine updates from the Antigen Enterprise Manager server

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 932485 - Last Review: April 24, 2007 - Revision: 1.1

Error messages are logged in the Programlog.txt file or in the Application log, and Antigen 9.0 for Exchange does not obtain engine updates from the Antigen Enterprise Manager server

SYMPTOMS

You use Microsoft Antigen Enterprise Manager as a redistribution server for servers that are running Microsoft Antigen 9.0 for Exchange. In an environment in which intermittent network problems occur, you find that Antigen 9.0 for Exchange does not obtain engine updates from the Antigen Enterprise Manager server. Additionally, one or more of the following error messages are logged either in the Progamlog.txt file or in the Application log:
"ERROR: UpdateException: GetFileCommand failed on ScanEngineName_fullpkg.cab. (0x00000006) The handle is invalid. Failed to read from file: \\ShareName\sybariredistribution$/x86/ScanEngineName/Package/0611200163/ScanEngineName_fullpkg.cab, handle: 000000C8"
Date Time (4580-4860), "INFORMATION: The ScanEngineName scan engine for Antigen has been rolled back."
Date Time (4580-4860), "INFORMATION: Sending Signature Update Failed Alert to SEM"
"ERROR: Unable to acquire the scan engine update mutex within the designated timeout period (300 seconds)."
"ERROR: The ScanEngineName scan engine update timed out while loading scanner"
"ERROR: The scan engine update thread has been stopped due to a timeout condition while loading scanner."
"ERROR: UpdateException: Unable to load manifest from: file:///\\ShareName\sybariredistribution$/x86/ScanEngineName/Package/0610170121/manifest.cab : (0x00000040) The specified network name is no longer available. Failed to access: \\ShareName\sybariredistribution$/x86/ScanEngineName/Package/0610170121/manifest.cab"
"ERROR: Unable to load manifest from: file:///\\ShareName\sybariredistribution$/x86/ScanEngineName/Package/manifest.cab : (0x00000040) The specified network name is no longer available. Failed to read from file: \\ShareName\sybariredistribution$/x86/ScanEngineName/Package/manifest.cab, handle: 00000310"

CAUSE

This problem occurs because of an issue in the way that the GetEngineFiles process in Antigen 9.0 for Exchange retrieves updates from the Antigen Enterprise Manager server.

RESOLUTION

To resolve this issue, apply the hotfix that is described in the following article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base:
930360  (http://kbalertz.com/Feedback.aspx?kbNumber=930360/ ) Antigen 9.0 signatures are not updated when you try to update signatures by using Antigen Enterprise Manager
The hotfix incorporates retry operations at various stages of the engine update process.

MORE INFORMATION

For more information about Antigen for Exchange and about Antigen Enterprise Manager, visit the following Microsoft Web site:
http://www.microsoft.com/antigen/default.mspx (http://www.microsoft.com/antigen/default.mspx)

APPLIES TO
  • Microsoft Antigen for Exchange
Keywords: 
kbtshoot kbprb kbexpertiseinter KB932485
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate