Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 8146 Source: MSADC
An operation on server '<server>' returned [<error code>] <error description>. The Connection Agreement Config <CA> stopped.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Active Directory Connector (MSADC) ?
- Error code: 0x2, description: "Protocol Error" - See ME288392.
- Error code: 0x2, description: "Protocol Error" - As per Microsoft: "This behavior may occur if certain users or distribution lists are explicitly granted permissions to create top-level public folders or are explicitly denied permissions to create top-level public folders on the Exchange Server 5.5 computer". See ME827618 and ME842123 to fix this problem.
- Error code: 0xc, description: "Unavailable Critical Extension" - See ME891860 for a hotfix applicable to Microsoft Exchange Server 2003.
- Error code: 0x1, error description: "Operations Error" - According to Microsoft, this issue may occur if the Exchange 5.5 Server directory database contains orphaned objects (for example, recipient containers) that were deleted at a remote site. In this situation, the Active Directory Connector assumes that the Exchange 5.5 Server directory database cannot be accessed and stops processing the Connection Agreement. As a result, an "Operations Error" is generated. See ME325520 to resolve this problem.
Error code: 0x1, description: "Operations Error". As per ME324413, this issue may occur if Exchange 2000 cannot replicate Exchange Server directory objects to the Site Replication Service (SRS).
Error code: 0x2, description: "Protocol Error". See ME306360 for cause and fix.
|Private comment: Subscribers only. See example of private comment|
|Links: ME288392, ME306360, ME324413, ME325520, ME827618, ME842123, ME891860|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated