Event ID:2159
Source:MSExchange ADAccess
Message:Process %1 (PID=%2). Configuration object %3 read from %4 failed validation and will be excluded from the result set. Set event logging level for Validation category to Maximum to get additional events about each failure.

This Warning event indicates that the configuration object 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 its attributes contain valid values.

  • These values are consistent with other attributes.

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

User Action

To resolve this warning, follow these steps:

  • 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 detailed information about how to increase logging, see How to Change Logging Levels for Exchange Processes.

  • You can also change the logging level by editing the registry as described here:

    Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing 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 have completed 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.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.