Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Config_CA Connection Agreement Replication Stops with Event ID 8146 Protocol Error Message After You Remove Server


View products that this article applies to.

Symptoms

When you remove the last Exchange 2000 server in a pure administrative group and then perform a "Replicate Now" operation on the Config_CA connection agreement to try to replicate the deleted server object to the Exchange Server 5.5 directory, the Config_CA connection agreement may stop and an error message may be logged that is similar to the following:
Event Source: MSADC
Event Category: Replication
Event ID: 8146
"An operation on server 'server_name' returned [0x2]Protocol Error. The Connection Agreement Config CA_AG_SERVER stopped."

↑ Back to the top


Cause

This problem can occur if the Routing Information Daemon (RID) server on the legacy GWART is left pointing to a deleted server object after the last Exchange 2000 server is removed from a pure administrative group. The Config_CA connection agreement tries to read the object that the distinguished name (also known as DN) points to, a protocol error is returned, and the Config_CA connection agreement throws an exception and stops processing.

↑ Back to the top


Resolution

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

↑ Back to the top


Workaround

To work around this problem, delete the administrative group; the Config_CA connection agreement recovers and starts processing again.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.

↑ Back to the top


Keywords: KB288392, kbfix, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 288392
Revision : 6
Created on : 2/26/2007
Published on : 2/26/2007
Exists online : False
Views : 257