MSExchange ADAccess 2142

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

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

Details

Explanation

This Error event indicates that new topology could not be generated. If this is not the first topology discovery since system startup, the previously discovered topology will be used. If this is the first topology discovery, most of the Microsoft Exchange services will not start.

Topology discovery failure is usually a sign of connectivity or permission problems. You must investigate this failure immediately. Topology discovery failure may have one or more of the following causes:

• All local domain controllers are down or are considered inappropriate. For example, all domain controllers must be running a 64-bit edition of Windows Server 2008 or later versions.

• Network problems do not let the server that is running Microsoft Exchange contact the domain controllers.

• Permissions problems exist.

User Action

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

• Examine the Lightweight Directory Access Protocol (LDAP) error code that is specified in the event description. To do this, see Microsoft Knowledge Base article 218185, Microsoft LDAP Error Codes. Use the information in that article to learn more about the cause and resolution to this error.

• Make sure that local domain controllers are reachable and are running. To do this, do one or more of the following:

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

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

• Look for accompanying events in the Application log. To see these additional events, you may have to increase logging for MSExchangeADAccess or MSExchange Topology performance objects.