A recipient object in Active Directory isn't valid. Review the exception in MSExchange ADAccess 2156 for the cause.
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2010-02-15
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
2156 |
Event Source |
MSExchange ADAccess |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access |
Rule Name |
A recipient object in Active Directory isn't valid. Review the exception in MSExchange ADAccess 2156 for the cause. |
Explanation
This Error event indicates that the recipient object specified in the event description is in an inconsistent state. An inconsistent state means that one or more attributes of the specified recipient object contain corrupted or invalid values. A recipient object is considered a Fully Consistent Object (FCO) if all its attributes contain valid values and these values are consistent with other attributes.
User Action
To determine which attributes or properties contain invalid values, increase diagnostic logging. Specifically, increase the diagnostic logging level on the Validation counter of the MSExchange ADAccess performance object to High. For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.
After the diagnostic logging level has been set to 5 (which is Maximum), review other Warning and Error events in the Application log to determine which attributes or properties contain invalid values.
Important After you have completed troubleshooting this issue, return logging to the default level, Lowest.