Topic Last Modified: 2010-02-16

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	7005
Event Source	MSExchangeTransportLogSearch
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport Log Search
Rule Name	The Microsoft Exchange Transport Log Search service failed to read configuration from Active Directory.

Explanation

This Error event indicates the Microsoft Exchange Transport Log Search service could not read the current local computer account name from Active Directory.

The Microsoft Exchange Transport Log Search service is used by the Get-MessageTrackingLog and Search-MessageTrackingReport cmdlets in the Exchange Management Shell, the Delivery Reports tool in the Exchange Control Panel, and the Tracking Log Explorer tool in the Exchange Management Console to search the message tracking logs on the Hub Transport server, Edge Transport server, or Mailbox server.

This error may indicate a general problem accessing Active Directory on a domain controller.

User Action

To resolve this error, do one or more of the following:

Make sure that the Exchange server that logged this event can connect to the configuration domain controller. 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.
Make sure that the configuration domain controller that the Exchange server connects to is registered correctly on the Domain Name System (DNS) server. For more information, see How DNS Support for Active Directory Works.
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.

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.