MSExchange ADAccess 2114

  • Article

 

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

2114

Category

Topology

Symbolic Name

DSC_EVENT_DISCOVERY_FAILED

Message Text

Process %1 (PID=%2). Topology discovery failed, error 0x%3 (%4). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Explanation

This Error event indicates that the new topology could not be generated. If this is not the first topology discovery since system startup, the previously discovered topology will be used. If it is the first topology discovery, most of the Exchange services will not start.

Topology discovery failure is usually a sign of connectivity or permission problems and must be investigated immediately. The following are the possible causes:

  • All local domain controllers are down or considered inappropriate. For example, at least one domain controller must be running Windows Server 2003 Service Pack 1 (SP1) or later. For more information about Active Directory minimum requirements, see Exchange 2010 System Requirements.

  • Network problems prevent the Exchange server from contacting the domain controllers.

  • There are permissions problems.

User Action

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

  • Verify at least one domain controller is running Windows Server 2003 SP1 or later.

  • Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, refer to Microsoft Knowledge Base article 218185, Microsoft LDAP Error Codes. Use the information in that article to learn more about the cause and resolution to this error.

  • Make sure that local domain controllers are reachable and running by doing one or more of the following:

    • 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, Advanced network adapter troubleshooting for Windows workstations.

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

  • Look for accompanying events in the Application log. You may have to increase logging for MSExchangeADAccess or MSExchange Topology performance objects to see these additional events.

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.