Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: %1.

Details
Product: Exchange
Event ID: 7005
Source: MSExchangeTransportLogSearch
Version: 8.0
Symbolic Name: LogSearchReadConfigFailed
Message: Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: %1.
   
Explanation

This Error event indicates the Microsoft Exchange Transport Log Search service could not read the current local computer account name from the Active Directory directory service. The Microsoft Exchange Transport Log Search service is available on a Hub Transport server, Edge Transport server, and Mailbox server.

This error may be logged every 10 minutes on a Mailbox server if the following conditions are true:

  • The server is a passive node in a cluster continuous replication (CCR) cluster.

  • The Microsoft Exchange Transport Log Search service is started on the passive node.

In a CCR cluster, the Microsoft Exchange Transport Log Search service uses the cluster name that resides only on the active node. The cluster name differs from the computer account name of the active node or any passive nodes.

For more information, see Cluster Continuous Replication.

For non-clustered servers, this error may indicate a general problem accessing Active Directory on a domain controller.

   
User Action

To resolve this error on a Mailbox server that is a passive node in a CCR cluster, do the following:

  • In the Services console on the Exchange server, stop the Microsoft Exchange Transport Log Search service, and change the Startup Type to Manual or Disabled.

To resolve this error on a Hub Transport server, Mailbox server, or Edge Transport server in a non-clustered environment, do one or more of the following:

  • Make sure that the Exchange server that logged this event can connect to the configuration domain controller. For example, 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.

  • Make sure that the configuration domain controller that Exchange server connects to is registered correctly on the Domain Name System (DNS) server. For more information, see the following Microsoft Knowledge Base articles:

  • Examine related events in the Application log and System log for Warning events and Error events that come before or after this event. These related events may provide more information about the root cause of this error.

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