MSExchange ADAccess 2086

 

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

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

Details

Product Name

Exchange

Product Version

14.0

Event ID

2086

Category

Topology

Symbolic Name

DSC_EVENT_NO_LOCAL_DC_FOUND

Message Text

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

Explanation

This event indicates that topology discovery determined that there are no suitable domain controllers in the local site. DSAccess will use out-of-site domain controllers. However, they might respond slower, which 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 or not suitable.

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

  • Permissions problems exist.

  • Configuration errors exist.

User Action

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

  • Make sure that the local site has enough domain controllers for Exchange.

  • Use the nltest /dsgetdc:<domain> /site:<local site name> command to verify that a domain controller can be located in the local site. The NLTest tool is installed with the Windows support tools.

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

  • If MSExchange ADAccess 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 MSExchange ADAccess 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. ADAccess found no suitable global catalogs when initial topology discovery completed.

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

  • 运行 Dcdiag 命令行工具可测试域控制器的运行状况。为此,请在 Exchange 服务器上的命令提示符处运行 dcdiag /s:[域控制器名称]。查看 Dcdiag 的输出,找出其报告的任何失败或警告的根本原因。有关详细信息,请参阅位于 Windows Server TechCenter 的 Dcdiag 概述

For more information about the Get-EventLogLevel and Set-EventLogLevel diagnostic logging cmdlets, see the following topics:

For More Information

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