Article ID: 281485
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q281485
SYMPTOMS
The following error message may be displayed when you attempt to replicate changes between replica partners in the Active Directory Sites and Services tool:
You may also find event ID 1226 or 1265 in the System event log.
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.
RESOLUTION
Service Pack Information
To 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 How to Obtain the Latest Windows 2000 Service Pack
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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
sem d a
go fix
q
You should see text that is similar to the following sample text to indicate a successful recovery:
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
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 3.
MORE INFORMATION
For 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 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 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 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 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:
Note that the GUIDs listed in these entries may vary.
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
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
Using Ntdsutil while connected to server 2 in the peer domain lists:
H:\>ntdsutil
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
In this example, the root domain shows the incorrect name:
Found 2 domain(s)
0 - DC=firstdomain,DC=com
1 - DC="seconddomain
CNF:9b9fbae4-7ba8-45b3-bb6c-71b94c37779a",DC=com
The peer domain shows the correct information:
Found 2 domain(s)
0 - DC=firstdomain,DC=com
1 - DC=seconddomain,DC=com
select operation target: select domain 1
Additional query words: kbDirServices
Keywords: kbhotfixserver kbqfe kbbug kbdirservices kbfix kbwin2000presp3fix kbwin2000sp3fix KB281485
