MSExchange ADAccess 2157

  • Article

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

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 Change Logging Levels for Exchange Processes.

  • 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   If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.