Process %1 (PID=%2). No Domain Controller server is up in the local site ‘%3’. Exchange Active Directory Provider will use the following out of site Domain Controller servers: %4

Details
Product: Exchange
Event ID: 2084
Source: MSExchangeADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_GOING_OUT_OF_SITE_DC
Message: Process %1 (PID=%2). No Domain Controller server is up in the local site ‘%3’. Exchange Active Directory Provider will use the
following out of site Domain Controller servers:
%4
   
Explanation

This event indicates that no suitable domain controllers exist in the local site. DSAccess will use out-of-site domain controllers, but they may respond slower. This can cause message queuing and network saturation. This event may be logged when the following conditions are true:

  • No domain controllers exist in the local site.

  • All in-site domain controllers are down.

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

  • Permission problems.

  • Configuration errors.

   
User Action

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

  • Make sure that at least one domain controller in the local site has been promoted to become a global catalog server, and that enough time has passed to synchronize with other global catalog servers.

  • If a global catalog server is expected to be present, confirm it is running and reachable over the network from the Exchange server.

  • Use the nltest /dsgetdc: /site:<local site name> command to verify that a global catalog server can be located in the local site. Look for the global catalog server flag in the nltest output. The NLTest tool is installed with the Windows support tools.

  • 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, no suitable global catalogs may have been found when initial topology discovery completed. Review that event to determine which domain controllers have been contacted and if they are unsuitable 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, a global catalog may be down or is unreachable. Review the event for more information about why each domain controller has become unsuitable. DSAccess 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.

Note  If you aren’t already doing so, consider running the tools that 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 mailflow, and better manage disaster-recovery scenarios. Go to the Toolbox node of 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