MSExchange ADAccess 2069

 

上一次修改主题: 2011-03-24

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

Details

Product Name

Exchange

Product Version

14.0

Event ID

2069

Category

Topology

Symbolic Name

DSC_EVENT_NO_GC_FOUND

Message Text

Process %1 (PID=%2). Exchange Active Directory Provider couldn't find any Global Catalog servers in either the local site '%3' or the following sites: %n%4

Explanation

Exchange Active Directory Provider found no global catalog servers in the local site or external sites. The sites are specified in the associated events. This can cause services startup failure or halting of mail flow. Therefore, it should be investigated immediately.

This may be caused by the following conditions:

  • All domain controllers are down or are not suitable

  • Network problems prevent the Exchange computer from contacting the domain controllers

  • Permission problems

  • Configuration errors

User Action

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

  • Verify that at least one global catalog exists in the forest and that it is reachable from the Exchange server on port 3268. If there are no global catalogs in the forest, use the Sites and Services MMC snap-in to promote a domain controller to a global catalog server.

  • Verify that DNS is configured correctly on the Exchange server and that the configured DNS servers are functional and reachable.

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

  • 查看应用程序日志中的相关事件。其他 MSExchange ADAccess 事件和其他事件中的详细信息可帮助确定出现此警告的根本原因。将 MSExchange ADAccess\Topology 类别的诊断日志记录增大到最低或更高。有关如何增加日志记录的详细信息,请参阅管理诊断日志记录级别

  • If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs may have been found when initial topology discovery was 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 is not suited. DSAccess found no suitable global catalogs when initial topology discovery was completed. Explanation

Exchange Active Directory Provider found no global catalog servers in the local site or external sites. The sites are specified in the associated events. This can cause services startup failure or halting of mail flow. Therefore, it should be investigated immediately.

This may be caused by the following conditions:

  • All domain controllers are down or are not suitable

  • Network problems prevent the Exchange computer from contacting the domain controllers

  • Permission problems

  • Configuration errors

User Action

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

  • Verify that at least one global catalog exists in the forest and that it is reachable from the Exchange server on port 3268. If there are no global catalogs in the forest, use the Sites and Services MMC snap-in to promote a domain controller to a global catalog server.

  • Verify that DNS is configured correctly on the Exchange server and that the configured DNS servers are functional and reachable.

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

  • 查看应用程序日志中的相关事件。其他 MSExchange ADAccess 事件和其他事件中的详细信息可帮助确定出现此警告的根本原因。将 MSExchange ADAccess\Topology 类别的诊断日志记录增大到最低或更高。有关如何增加日志记录的详细信息,请参阅管理诊断日志记录级别

  • If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs may have been found when initial topology discovery was 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 is not suited. DSAccess found no suitable global catalogs when initial topology discovery was completed.

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

For More Information

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