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

Article translations Article translations
Article ID: 271946 - View products that this article applies to.
This article was previously published under Q271946
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

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 the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English-language version of this fix should have the following file attributes or later:
   Date         Time       Size      File name
   -----------------------------------------------------
   02/05/2001   05:54 PM   130,320   Adsldpc.dll
   02/05/2001   05:54 PM   360,208   Advapi32.dll
   02/05/2001   05:54 PM   133,904   Dnsapi.dll
   02/05/2001   05:54 PM    90,896   Dnsrslvr.dll
   02/05/2001   09:10 PM   512,784   Instlsa5.dll
   02/05/2001   05:54 PM   140,560   Kdcsvc.dll
   01/29/2001   09:19 PM   198,928   Kerberos.dll
   01/26/2001   10:15 PM    69,456   Ksecdd.sys
   02/05/2001   05:54 PM   494,864   Lsasrv.dll
   01/30/2001   09:04 PM    33,552   Lsass.exe
   01/29/2001   09:19 PM   108,816   Msv1_0.dll
   02/05/2001   05:54 PM   311,056   Netapi32.dll
   02/05/2001   05:54 PM   366,352   Netlogon.dll
   02/05/2001   05:54 PM   910,608   Ntdsa.dll
   02/05/2001   05:54 PM   362,256   Samsrv.dll
   02/05/2001   05:54 PM   128,272   Wldap32.dll
				



NOTE: This hotfix must be applied to all Global Catalog servers.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Properties

Article ID: 271946 - Last Review: October 21, 2013 - Revision: 3.3
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbenv kbfix KB271946

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com