MSExchangeFDS 1022
This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.
Details
Product Name |
Exchange |
Product Version |
14.0 |
Event ID |
1022 |
Category |
General |
Symbolic Name |
SourceManifestNotAvailable |
Message Text |
Process %1 (PID=%2). Could not find file %3. This is normal if it has never been generated. Otherwise, make sure this file has read permission for "Exchange Servers" group. |
Explanation
This event indicates that Microsoft Exchange File Distribution service did not find an offline address book (OAB) file. If MSExchangeFDS event 1022 is logged, the Microsoft Exchange File Distribution service did not find an OAB manifest file (oab.xml). The File Distribution service requires this file to synchronize OAB files between Exchange servers that have the Mailbox server role and Client Access server role installed.
This event may occur if either of the following conditions is true:
The OAB manifest file (oab.xml) has not been generated yet. This file is generated when the corresponding OAB is updated. By default, every OAB is updated daily at 5:00 A.M.
The Exchange Servers group does not have the Read permission on this manifest file (oab.xml).
Note
If the corresponding OAB update has yet to run, you may ignore this event. Otherwise, see the "User Action" section in this topic.
Note
The OAB GUID that follows the ExchangeOAB file share in the event description indicates the corresponding OAB.
User Action
To resolve this warning, do the following:
Make sure that Exchange Servers group has the Read permission on the oab.xml file that is specified in the event description. Then, regenerate the manifest file by following these steps:
Note the OAB GUID that follows the ExchangeOAB file share in the event description.
Run the following Exchange Management Shell command:
Update-OfflineAddressBook -Identity <offline address book identifier>
Note
In this command, replace <offline address book identifier> with the GUID that you determined in the previous step.
- Restart the Microsoft Exchange File Distribution service from the Microsoft Windows Services console on the Exchange server that logged this event.
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.