Replication Does Not Work When there Is a Name Conflict on a Global Catalog

This article has been archived. It is offered "as is" and will no longer be updated.

SYMPTOMS

If a Global Catalog (GC) server that does not have a writable copy of the partition contains an object in its naming context that was deleted on the server with the writable partition and the deletion of the object was not replicated to the GC, the GC may stop replicating on that naming context until the problem is resolved.

CAUSE

This problem can occur when replication to the GC does not occur either in the tombstone lifetime (by default, the lifetime 60 days) or in the tombstone garbage collection time. Because neither the deleted parent nor the conflicted object exist, the GC never receives an update that puts this object in the LostAndFound, which it needs to do. Until the object becomes "unstuck," the affected GC is not a viable replication source for the affected NC. Other GCs fail over to other sources for this NC.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base: