• Article

OALGen failed to find or open the OAB version 4 manifest file

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:

  • From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.

To learn more about this alert, if you are using System Center Operations Manager 2007, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the events that have been logged that meet the criteria of this Operations Manager alert.

Details

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

9390;9391;9392

Event Source

MSExchangeSA

Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Mailbox/System Attendant

MOM Rule Name

OALGen failed to find or open the OAB version 4 manifest file.

Explanation

Event error ID 9390 indicates that either this is the first time that the offline address book (OAB) was created, or that the file was accidentally deleted.

Event error ID 9391 indicates that the OAB version 4 manifest file is corrupt or has been tampered with.

Event error ID 9392 indicates that OAB generation (OABGen) could not read the OAB version 4 manifest file metadata.

User Action

To resolve error event 9390, determine if the OAB was created for the first time or if the OAB was accidentally deleted.

If the OAB was accidentally deleted or to resolve error event 9391, do one or more of the following:

  • If daily backups are available, restore the content of the OABGen folder to the <ExchangeInstallDir> \ExchangeOAB\ <OAB GUID> folder (where <ExchangeInstallDir> is a placeholder for the installation directory of Microsoft Exchange Server 2007 and <OAB GUID> is a placeholder for the name of the folder).

  • If the corrupted OAB item is enabled for public folder distribution and the data has been published to public folders before the OAB item was corrupted, you can delete the contents of the OABGen folder from the <ExchangeInstallDir> \ExchangeOAB\ <OAB GUID> folder and rebuild the OAB files by updating the OAB. For more information about how to update the OAB, see How to Update the Offline Address Book.

  • If neither daily backups nor public folder distribution is enabled, delete the contents of the OABGen folder from <ExchangeInstallDir> \ExchangeOAB\ <OAB GUID>, and then rebuild the OAB files by using the following command in the Exchange Management Shell:

    Update-OfflineAddressBook <OABGuid>

    Important

    This procedure will cause a full OAB download by all clients. A full OAB download can cause massive network traffic between Client Access servers and clients.

To resolve error event 9392, do one or more of the following:

  • Review the Application log to determine if this event has been logged more than once for the same file.

  • If this event has been logged more than once for the same file, check the file permissions in the OAB distribution point. To locate the file path location for the OAB Web-based distribution point, use the Exchange Management Shell to run the Get-OABVirtualDirectory cmdlet. To locate the file path location for the OAB public folders-based distribution point, use the Exchange Management Shell to run the Get-PublicFolder cmdlet.

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message Center.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.