Topic Last Modified: 2007-03-14

The Microsoft Exchange Analyzer tool includes a performance data collection engine that is used to query performance counter objects on computers that are running Exchange 2000 Server or Exchange Server 2003. The performance data collection engine collects data from the LDAP Read Time performance counter of the MSExchangeDSAccess Process performance object to analyze performance data.

The LDAP Read Time performance counter shows the time in milliseconds that it takes a Lightweight Directory Access Protocol (LDAP) read request to be fulfilled. The Exchange Analyzer retrieves a sample every 5 seconds for 5 minutes. The Exchange Analyzer then reports the maximum value for the performance counter during the collection interval. If the average value exceeds 50 milliseconds, the Exchange Analyzer displays a warning.

High LDAP read latencies can be caused by high remote procedure call (RPC) latencies and by increasing queues. High LDAP read latencies generally indicate one of the following problems:

LDAP latencies are generally higher when users connect to domain controllers that are located in different physical sites. However, the recommended maximum latencies stated in this article should generally be followed.

If the domain controller that has logged this warning is located in a different physical site, you may be able to safely ignore this error if you can determine that the domain controller that reports this warning is not used by the Exchange server. One way to determine whether a domain controller is used by Exchange is to increase diagnostic logging for the Topology component of the MSExchangeDSAccess service to Minimum. If you do not see MSExchangeDSAccess event ID event 2080, you can safely ignore this warning.

To resolve this warning, do the following: