Topic Last Modified: 2010-02-18

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:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source


Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport

Rule Name

Failed to read message customization configuration.


This Error event may be logged on a Hub Transport server when Microsoft Exchange Server 2010 is unable to read the delivery status notification (DSN) message configuration information from Active Directory. This Error event may also be logged on an Edge Transport server if Exchange 2010 is unable to read the DSN message configuration from Active Directory Lightweight Directory Services (AD LDS). This Error event may be caused if one or more of the following conditions are true:

  • There is a connectivity problem between the Hub Transport server and Active Directory.

  • The domain controller is not functioning correctly.

  • The Microsoft Exchange AD LDS service on an Edge Transport server has stopped.

  • If the configuration stored in Active Directory or in AD LDS is corrupted.

User Action

To resolve this error, do one of the following:

  • If this error occurred on a Hub Transport server, try one or both of the following:

    • Verify connectivity between Active Directory and the Hub Transport server. Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems

    • Run the Dcdiag command-line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.

  • If this error occurred on an Edge Transport server, verify that the Microsoft Exchange ADAM service is started on the local server.

If you still can't resolve the problem, contact Microsoft Product Support. For information about how to contact support, visit Microsoft Help and Support Web site.

For more information about DSNs, see Managing Delivery Status Notifications.

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.