MSExchange ADAccess 2142

  • 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

2142

Category

Topology

Symbolic Name

DSC_EVENT_DISCOVERY_FAILED2

Message Text

Process %1 (PID=%2). Topology discovery failed, error 0x%3.

Explanation

This Error event indicates that 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 this is the first topology discovery, most of the Microsoft Exchange services will not start.

Topology discovery failure is usually a sign of connectivity or permission problems. You must investigate this failure immediately. Topology discovery failure may have one or more of the following causes:

  • All local domain controllers are down or are considered inappropriate. For example, all domain controllers must be running a 64-bit edition of Windows Server 2008 or later versions.

  • Network problems do not let the server that is running Microsoft Exchange contact the domain controllers.

  • Permissions problems exist.

User Action

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

  • Examine the Lightweight Directory Access Protocol (LDAP) error code that is specified in the event description. To do this, see 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 are running. To do this, do 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. To see these additional events, you may have to increase logging for MSExchangeADAccess or MSExchange Topology performance objects.