windowswideopen.com

When this error occurs, the following is generally logged in the “Directory Service” event log :

Event ID : 1083

Event Type: Warning

Event Source: NTDS Replication

Event Category: Replication

Event ID: 1083

Date: 10/2/2006

Time: 9:56:19 AM

User: Everyone

Computer: DC1

Description:

Replication warning: The directory is busy. It couldn’t update object CN=DC2,CN=Servers,CN=Bad-Site,CN=Sites,CN=Configuration,DC=enterprise,DC=com with changes made by directory 62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.enterprise.com. Will try again later.

This error generally occurs when a duplicate object is present in the Active Directory of the replication partner of the local DC.

For example, Servers and “NTDS Settings” objects can be located in two different sites. Also, Users and Computers object and be located in two different OUs.

Updating this object when it receives the replication updates from it’s replication partner is then impossible for the local DC.

The description of the event 1083 contains :

The distinguished name of the object that is causing the problem (the one following “It couldn’t update object”)

Ø The GUID-based DNS name of the replication partner (the one following “with changes made by directory”). This name is composed of the GUID of the “NTDS Settings” object of the replication partner, followed by “_msdcs.enterprise.com”.

To resolve the problem:

Ping the GUID based DNS name to get the IP address of the replication partner.

Run LDP and connect this IP address using the connect option of the “Connection” menu. Then select the “Bind” option of the “Connection ” menu and enter the credentials of an administrator account. Then select the “Search” option of the browse menu. In the search dialog box, check the “Subtree” option.
In the “Base Dn” option enter :

· The distinguished name of the domain to search for a user or a computer. In the example, dc=domain,dc=enterprise,dc=com

· The distinguished name of the configuration container to search for connection objects. In the example, cn=configuration,dc=enterprise,dc=com

For the filter, enter the first part of the distinguished name of the object in parentheses. In the example, enter :

(CN=DC2)

Then hit “Run”. The right part of the widow should then display the different locations where the object has been found. Select which is the good one and delete the others using the “Delete” option of the “Browse” menu. Enter the distinguished name of the object to delete. In the example, enter :

CN=DC2,CN=Servers,CN=Bad-Site,CN=Sites,CN=Configuration,DC=enterprise,DC=com

Check the object has been properly deleted in the right part of the LDP window.

If there is no duplicate, try to move the object to a different Site/OU. Make a note of that since you will need to move it back at some point in time.

Then synchronize the Configuration and Domain naming contexts using :

repadmin /sync CN=Configuration,DC=enterprise,DC=com %computername% <rep_partner_GUID>

repadmin /sync DC=domain,DC=enterprise,DC=com %computername% <rep_partner_GUID>

If the replication completes, the event log should not show any new event 1083.

If necessary, move back to it’s original location the object that had been moved to a different site or a different OU and make a new replication of the Domain and Configuration naming contexts.

distinguished name event id replication partnerdistinguished name event id replication partner