MSExchange ADAccess 2085

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

Explanation

This event indicates that no suitable global catalog servers exist in the local site. DSAccess will use out-of-site global catalog servers, but they may respond more slowly. This can cause message queuing and network saturation. The loss of all global catalogs in a site is an unusual occurrence that must be investigated.

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 are preventing the Exchange server from contacting the domain controllers.

• Permission problems exist.

• Configuration errors exist.

User Action

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

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

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

• 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 together with the Windows support tools.

• Check the Application log for related events. The detail in other MSExchangeADAccess events and in other events may help determine the 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, type Get-EventLogLevel MSExchangeADAccess in the Exchange Management Shell.

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

• If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs may have been found when initial topology discovery finished. Review that event to determine which domain controllers have been contacted and whether they are unsuitable for any reason. 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 unreachable. Review the event for more information about why each domain controller has become unsuitable. ADAccess found no suitable global catalogs when initial topology discovery finished.

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

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

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