Process %1 (PID=%2). No Global Catalog server was found in the local site %3. Exchange Active Directory Provider will try to find Global Catalog servers in other sites.

Details
Product: Exchange
Event ID: 2060
Source: MSExchange ADAccess
Version: 08.01.0107.000
Symbolic Name: DSC_EVENT_NO_LOCAL_GC_FOUND
Message: Process %1 (PID=%2). No Global Catalog server was found in the local site %3.
Exchange Active Directory Provider will try to find Global Catalog servers in other sites.
   
Explanation

This event indicates that topology discovery determined that there are no suitable global catalog servers in the local site. DSAccess will use out-of-site global catalog servers. However, they may respond slower, which can cause message queuing and network saturation.

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

  • No global catalog servers exist in the local site.

  • All in-site global catalog servers are down or not suitable.

  • Network problems prevent the Exchange server from contacting the global catalog servers.

  • Permissions problems exist.

  • Configuration errors exist.

   
User Action

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

  • Make sure that the local site has enough global catalog servers for Exchange.

  • 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 increase logging levels, see How to Change Logging Levels for Exchange Processes.

  • If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs were 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. 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 details about why each domain controller has become unsuitable. ADAccess found no suitable global catalogs when initial topology discovery 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.

  • 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 Microsoft Windows Server TechCenter.

For more information about diagnostic logging commands, see Get-EventLogLevel and Set -EventLogLevel in the Exchange 2007 Help.

Related:

Leave a Reply