Process %1 (PID=%2). Exchange Active Directory Provider could not find any Domain Controller servers in neither the local site ‘%3’ nor the following sites: %4

Details
Product: Exchange
Event ID: 2077
Source: MSExchange ADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_NO_DC_FOUND
Message: Process %1 (PID=%2). Exchange Active Directory Provider could not find any Domain Controller servers in neither the local site ‘%3’
nor the following sites:
%4
   
Explanation

This event indicates that topology discovery determined that there are no suitable domain controllers in the local site or adjacent sites.

This can cause services startup failure or halting of mail flow and interruption of address book services. This problem should be investigated immediately.

This event may be logged if the following conditions are true:

  • Network connectivity issues may be preventing communication with the global catalog server.

  • The Exchange server may be pointing to the wrong DNS servers.

  • DNS may be configured incorrectly or the configured DNS servers may be down and not reachable.

  • Permission problems exist.

   
User Action

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

  • Check the Application log for related events. The detail in other MSExchangeADAccess events and other events may help determine the root cause of this warning. Increase diagnostic logging for the MSExchangeADAccess\Topology category to Minimum or higher.

    • To review the current MSExchangeADAccess service diagnostic logging settings, in the Exchange Management Shell, type Get-EventLogLevel MSExchangeADAccess.

    • To change the logging level for the Topology category, in the Exchange Management Shell, type Set-EventlogLevel MSExchangeADAccess\Topology -Level Minimum.

  • If MSExchangeADAccess Event ID 2080 is logged, suitable global catalogs may not be present when initial topology discovery completes. Review that event to determine which domain controllers have been contacted and if they are not suitable for any reasons. Correct any problems as indicated by the event description. For more information, see Microsoft Knowledge Base article 316300, Event ID 2080 from MSExchangeDSAccess.

  • If MSExchangeADAccess Event ID 2070 is logged, global catalog may be down or is unreachable. Review the event for more information about why each domain controller is not suitable. ADAccess found no suitable global catalogs when initial topology discovery was completed.

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

For more information about diagnostic logging commands, see get-eventloglevel and set -eventloglevel in the Exchange 2007 Help.

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