An error caused by reading the SystemMessage configuration from the directory indicates that generation of delivery status notifications (DSNs) and storage quota is using out-of-date or incomplete message customizations. The configuration data may be corrupt, or the Active Directory directory service may be unreachable. The error was ‘%1’

Details
Product: Exchange
Event ID: 3005
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: DsnUnableToReadSystemMessageConfig
Message: An error caused by reading the SystemMessage configuration from the directory indicates that generation of delivery status notifications (DSNs) and storage quota is using out-of-date or incomplete message customizations. The configuration data may be corrupt, or the Active Directory directory service may be unreachable. The error was ‘%1’
   
Explanation

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

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

  • If the domain controller is not functioning correctly.

  • If the Microsoft Exchange ADAM service on an Edge Transport server has stopped.

  • If the configuration stored in Active Directory or in ADAM 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 Microsoft 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.

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.

Related:

Leave a Reply