OABGen failed to find or open the OAB version 4 manifest file.
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-02
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, 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 logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
^(9390|9391|9392)$ |
Event Source |
MSExchangeSA |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Mailbox/System Attendant |
Rule Name |
OABGen 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 corrupted 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 Exchange 2010 installation directory 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 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 running the following command in the Exchange Management Shell:
Update-OfflineAddressBook <OABGuid>Important
This procedure causes a full OAB download by all clients. A full OAB download can cause considerable 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
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.