Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NTDS Error: 1084 Collison of Names

Status
Not open for further replies.

pserko

IS-IT--Management
Aug 6, 2001
9
US
I have the following error and can't figure out how to fix, ideas?

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1084
Date: 10/19/2001
Time: 8:30:03 AM
User: Everyone
Computer: GMCELROY0
Description:
Replication error: The directory replication agent (DRA) couldn't update object DC=0.4,DC=1.10.in-addr.arpa,CN=MicrosoftDNS,CN=System,DC=intra,DC=vashonsd,DC=wednet,DC=edu (GUID a39404e7-55f3-4ebe-8f2c-15b2ac1a67eb) on this system with changes which have been received from source server 5f5b58a5-89e9-4db9-91f9-c536b35d6a97._msdcs.intra.vashonsd.wednet.edu. An error occurred during the application of the changes to the directory database on this system.

The error message is:
The replication operation failed due to a collision of object names.

The directory will try to update the object later on the next replication cycle. Synchronization of this server with the source is effectively blocked until the update problem is corrected.
If this condition appears to be related to a resource shortage, please stop and restart this Windows Domain Controller.
If this condition is an internal error, a database error, or an object relationship or constraint error, manual intervention will be required to correct the database and allow the update to proceed. It is valuable to note that the problem is caused by the fact that the change on the remote system cannot be applied locally. Manually updating the objects on the local system in not recommended. Instead, on the source system (which has the changes already), try to reverse or back out the change. Then, on the next replication cycle, observe whether the change can now be applied locally.
The record data is the status code.
Data:
0000: 0a 21 00 00 .!..
 
pserko,
Check out Q285858. It seems you have an orphaned object in Active Directory. The Technote links to how you can contact Microsoft for a fix, but they recommend you wait for the next service pack to come out if the problem is merely cosmetic, as the fix is still being tested.

-gbiello
 
Thanks for the tip but need to do something since all directory replication has stopped.
 
Check out these two MS articles: Q216498 and Q230306.

They explain how to remove objects from AD.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top