Article ID: 281485 - Last Review: February 28, 2007 - Revision: 2.6 Name Collision in Active Directory Causes Replication Errors
This article was previously published under Q281485 On This PageSYMPTOMS
The following error message may be displayed when you attempt to replicate changes between replica partners in the Active Directory Sites and Services tool:
The following error occurred during the attempt to synchronize the domain controllers. The naming context is in the process of being removed or is not replicated from the specified server.
CAUSE
This message indicates that CrossRef object deletion or re-creation left the computer in a state in which the new naming context name has a name conflict.
RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:260910
(http://support.microsoft.com/kb/260910/EN-US/
)
How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File Name -------------------------------------------------------- 3/7/2001 01:11p 5.0.2195.3330 155,408 Ntdsutil.exe 3/7/2001 01:11p 5.0.2195.3330 155,408 Ntdsutil.exe After you install this hotfix, restart the computer in Directory Service Restore mode, start a command (Cmd.exe) prompt, and then type the following lines, pressing ENTER after each line:
c:\ntdsutil
You should see text that is similar to the following sample text to indicate a successful recovery:
sem d a go fix q
c:\ntdsutil c:\ntdsutil: sem d a semantic checker: go fix Fixup mode is turned on Opening DIT database... Done. Could not update "datatable" table: key already exists. Could not retrieve "ATTk589826" column in "datatable" table: (warning) column is null. Done. Opening database [Current].....Done. Getting record count...1744 records Writing summary into log file dsdit.dmp.0 Records scanned: 1700 Processing records..Done. semantic checker: q STATUSMicrosoft 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 3. MORE INFORMATIONFor additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below
to view the article in the Microsoft Knowledge Base:
265173
(http://support.microsoft.com/kb/265173/EN-US/
)
The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below
to view the article in the Microsoft Knowledge Base:
296861
(http://support.microsoft.com/kb/296861/EN-US/
)
Use QChain.exe to Install Multiple Hotfixes with One Reboot
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
(http://support.microsoft.com/kb/249149/EN-US/
)
Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
For additional information about how to restart your computer in Directory Service Restore mode, click the article number below
to view the article in the Microsoft Knowledge Base:
202485
(http://support.microsoft.com/kb/202485/EN-US/
)
Description of Safe Boot Mode in Windows 2000
When the problem that is described in this article occurs, you may see the following entries in the event logs:
Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1265 Date: 7/25/2000 Time: 11:06:15 AM User: N/A Computer: SRV1 Description: The attempt to establish a replication link with parameters Partition: DC="CHILD CNF:318498a8-8c57-46e3-b226-3693f7719162",DC=DOM2,DC=com Source DSA DN: CN=NTDS Settings,CN=SRV2,CN=Servers,CN=SITE2,CN=Sites,CN=Configuration,DC=CHILD,DC=DOM1,DC=net Source DSA Address: cabc8641-9a94-41d9-bf9a-56f43b67006a._msdcs.child.dom1.net Inter-site Transport (if any): CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=child,DC=dom1,DC=net failed with the following status: Logon Failure: The target account name is incorrect. The record data is the status code. This operation will be retried. Data: 0000: 74 05 00 00 t... Event Type: Information Event Source: NTDS Replication Event Category: Replication Event ID: 1226 Date: 06/11/2000 Time: 6:10:32 PM User: Everyone Computer:YOURCOMPUTERNAME Description: The object CN=YOURCOMPUTERNAME,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=YOURDOMAINNAME ,DC=com (with objectGuid 793c9a19-94ee-4713-b154-9a7f7d81b4a0) was created on a remote server. However, this name is already in use here by the object with objectGuid 980563ba-c29c-4638-ad40-3d0574c925b0. The object with objectGuid 980563ba-c29c-4638-ad40-3d0574c925b0 will be renamed to YOURCOMPUTERNAME CNF:980563ba-c29c-4638-ad40-3d0574c925b0, since the other object claimed the name first. You can use Ntdsutil to obtain the following information that shows the conflict in the names. Look for the lines beneath "Found 2 domain(s)". Using Ntdsutil while connected to server 1 in the root domain lists:
c:\>ntdsutil
Using Ntdsutil while connected to server 2 in the peer domain lists:
ntdsutil: metadata cleanup metadata cleanup: connections server connections: connect to server servername1 Binding to servername1 ... Connected to servername1 using credentials of locally logged on user server connections: quit metadata cleanup: s o t select operation target: l d Found 2 domain(s) 0 - DC=firstdomain,DC=com 1 - DC="seconddomain CNF:9b9fbae4-7ba8-45b3-bb6c-71b94c37779a",DC=com select operation target: select domain 1 No current site Domain - DC="seconddomain CNF:9b9fbae4-7ba8-45b3-bb6c-71b94c37779a",DC=com No current server
H:\>ntdsutil
In this example, the root domain shows the incorrect name:
ntdsutil: metadata cleanup metadata cleanup: connections server connections: connect to server servername2 Binding to servername2 ... Connected to servername2 using credentials of locally logged on user server connections: quit metadata cleanup: s o t select operation target: list domains Found 2 domain(s) 0 - DC=firstdomain,DC=com 1 - DC=seconddomain,DC=com select operation target: select domain 1 No current site Domain - DC=seconddomain,DC=comDescription of Safe Boot Mode in Windows 2000
Found 2 domain(s)
The peer domain shows the correct information:
0 - DC=firstdomain,DC=com 1 - DC="seconddomain CNF:9b9fbae4-7ba8-45b3-bb6c-71b94c37779a",DC=com
Found 2 domain(s) 0 - DC=firstdomain,DC=com 1 - DC=seconddomain,DC=com select operation target: select domain 1
| Article Translations
|
Back to the top
