• Article

File Distribution Service: IO operation has failed

 

Topic Last Modified: 2008-08-22

The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) 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 event, do one or more of the following:

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

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

Details

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

1005;1006

Event Source

MSExchangeFDS

Alert Type

Warning

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/File Distribution Service

MOM 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 and custom Unified Messaging prompts. This event may occur for various reasons.

  • If MSExchangeFDS 1005 is logged, 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 of various reasons.

User Action

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

  1. 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:

    1. Set-EventLogLevel MSExchangeFDS\FileReplication -Level High

      Note

      For detailed information about increasing logging, see How to Change Logging Levels for Exchange Processes.

  2. Review other related Error and Warning events in the Application log. These related events may help you determine the root cause of this error.

  3. 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:

    1. Set-EventLogLevel MSExchangeFDS\FileReplication -Level Lowest

      Important

      After you have completed troubleshooting this issue, you should always return logging to the default level to avoid filling your event logs.

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 MOM 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.