Topic Last Modified: 2010-09-12

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	^(1005\|1006)$
Event Source	MSExchangeFDS
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/File Distribution Service
Rule Name	File Distribution Service: IO operation has failed. Current file synchronization operation is aborted.

Explanation

This Warning event indicates that the Microsoft Exchange File Distribution service (MSExchangeFDS) operation failed. The MSExchangeFDS is used to distribute offline address books (OAB) and custom Unified Messaging prompts. This event may occur for various reasons, including the following reasons.

If MSExchangeFDS 1005 is logged, the Microsoft Exchange File Distribution service did not perform one of the file synchronization operations.
If MSExchangeFDS 1006 is logged, the Microsoft Exchange File Distribution service (MSExchangeFDS) did not finish a copy, replace, or move file operation when it performed a file synchronization task. This event may occur for various reasons.

User Action

To determine the cause of this Warning event, follow these steps:

Use the following Exchange Management Shell cmdlet to increase the diagnostic logging level on the FileReplication counter of the MSExchangeFDS performance object to the High setting:

Set-EventLogLevel MSExchangeFDS\FileReplication -Level High

Note:

For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.
Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.
Use the following Exchange Management Shell cmdlet to set the diagnostic logging level on the FileReplication counter of the MSExchangeFDS performance object back to the default Lowest setting:

Set-EventLogLevel MSExchangeFDS\FileReplication -Level Lowest

Important:

After you finish troubleshooting this error, you should return logging to the default level to avoid filling your event logs.

Note:
For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.

Important:
After you finish troubleshooting this error, you should return logging to the default level to avoid filling your event logs.

For More Information

If you are not already doing so, consider running the Exchange tools 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, improve mail flow, and better manage disaster recovery scenarios. 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.