MSExchange ADAccess 2085

上一次修改主题： 2011-03-30

本文对特定 Exchange 事件进行了说明并提供了可能的解决方案。如果您在此处未找到所需内容，请尝试在 Exchange 2010 帮助中进行搜索。

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.

• 使用 Ping 或 PathPing 命令行工具测试基本连接。使用 Ping 可隔离网络硬件问题和不兼容配置。使用 PathPing 可检测多重跳跃行程中的数据包丢失。有关详细信息，请参阅 Microsoft 知识库文章 325487：Windows 工作站的高级网络适配器疑难解答。

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

Note   如果您尚未执行此操作，请考虑运行 Exchange 工具，已创建这些工具以帮助您分析 Exchange 环境并对其进行疑难解答。这些工具可帮助确保您的配置与 Microsoft 最佳实践保持一致。它们还可以帮助您识别和解决性能问题，并改进邮件流。若要运行这些工具，请转到 Exchange 管理控制台的“工具箱”节点。若要了解有关这些工具的详细信息，请参阅管理工具箱中的工具。