MSExchange ADAccess 2104

  • 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

2104

Category

Topology

Symbolic Name

DSC_EVENT_ALL_DOMAIN_DS_DOWN

Message Text

Process %1 (PID=%2). Topology discovery failed due to LDAP_SERVER_DOWN error. This event can occur if one or more domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.

Explanation

This Error event indicates that the Exchange server was unable to contact a domain controller in the local domain. DSAccess needs a local domain controller to perform topology discovery.

This event may occur when the Exchange server starts. For example, if no domain controllers respond when the Exchange server starts, the Microsoft Exchange System Attendant (MSExchangeSA) and all its dependent services won't start.

This event may also occur when the Exchange server and all required services are running. For example, if all domain controllers and global catalog servers become unreachable during ordinary operation, the MSExchangeSA and all its dependent services will stop.

Note

When all domain controllers and global catalog servers go down, a new topology discovery becomes necessary.

This event can occur if the domain controllers in local or all domains become unreachable because of network problems.

User Action

To resolve this error, verify that at least one domain controller in the local domain in which the Exchange server resides is running and reachable from the Exchange server. 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.

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.