MSExchange ADAccess 2157

  • 项目

 

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

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

Details

Product Name

Exchange

Product Version

14.0

Event ID

2157

Category

Validation

Symbolic Name

DSC_EVENT_VALIDATION_FAILED_PCO_MODE_CONFIG

Message Text

Process %1 (PID=%2). Configuration object %3 read from %4 failed validation. A partially valid object will be returned. Set the event logging level for Validation category to Expert to get additional events about each failure.

Explanation

This Warning event indicates that the configuration object that is specified in the event description is in an inconsistent state. An inconsistent state means that one or more attributes of the specified configuration object contain corrupted or invalid values. A configuration object is considered a Fully Consistent object if the following conditions are true:

  • All attributes for the object contain valid values.

  • These values are consistent with those of other attributes.

This event indicates that the specified configuration object is inconsistent and will be ignored.

User Action

To resolve this issue, do the following:

  • Increase diagnostic logging so that you can determine which attributes or properties contain invalid values. Specifically, increase the diagnostic logging level on the Validation counter of the MSExchange ADAccess performance object. You can increase logging by running the following Exchange Management Shell cmdlet:

    Set-EventLogLevel "MSExchange ADAccess\Validation" -Level High

    For more information about how to increase logging, see 如何更改 Exchange 进程的日志记录级别.

  • Change the logging level by editing the registry as follows.

Note   Editing the registry incorrectly can cause serious problems that may require you to reinstall your operating system. Problems that result from editing the registry incorrectly may not be able to be resolved. Before you edit the registry, back up any valuable data.

  1. Start Registry Editor (regedit).

  2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Diagnostics.

  3. In the results pane, change the Value data of the General key to 5.

  4. Exit Registry Editor.

Important After you finish troubleshooting this issue, return logging to the default level by running the following cmdlet:

Set-EventLogLevel "MSExchange ADAccess\Validation" -Level Lowest

  • Review the additional MSExchangeADAccess events in the Application log to determine which attributes or properties contain invalid values.

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