MSExchange ADAccess 2389
This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.
Details
Product Name |
Exchange |
Product Version |
14.0 |
Event ID |
2389 |
Category |
LDAP |
Symbolic Name |
DSC_EVENT_LDAP_TIMEOUT |
Message Text |
Process %1 (PID=%2). A request to Directory Server %3 did not return a result within %4 seconds and is being abandoned. The search will be retried if possible. The search that failed has the following characteristics: Base DN=%5, Filter=%6, Scope=%7. |
Explanation
This Warning event indicates that a search request that was sent to the server that is running Active Directory did not provide a result within a reasonable time period. The search request was abandoned. This event is logged when the search request to the directory service did not return in less than 120 seconds.
The most frequent cause of this warning is because the domain controller is under heavy stress. This warning may also be caused if a network error is introduced at the packet level. This causes the domain controller to continuously try to resend the requested information to Microsoft Exchange.
User Action
If this event is seen rarely, it can be ignored. If this Warning event is logged at specific times or if any other pattern is detected, do the following:
Investigate what is occurring on the specific domain controller named in the Description section of the event and check to see whether it is being heavily loaded.
Use the
Ping
orPathPing
command-line tools to test basic connectivity. UsePing
to isolate network hardware problems and incompatible configurations. UsePathPing
to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.Run the
Dcdiag
command-line tool to test domain controller health. To do this, rundcdiag /s:[Domain Controller Name]
at a command prompt on the Exchange server. Use the output ofDcdiag
to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.