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.

Details
Product: Exchange
Event ID: 2389
Source: MSExchange ADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_LDAP_TIMEOUT
Message: 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 directory service is under heavy stress. This warning may also be caused if a network error is introduced at the packet level. The causes the sending server to continuously try to resend the directory service information back to Exchange.

   
User Action

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

  • 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 particular domain controller named in the Description section of the event and check to see whether it is being heavily loaded.

    • 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 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