The Directory Services event log contains:

Event ID : 1083
Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Description: Replication warning: The directory is busy. It couldn't update object CN=... with changes made by directory GUID._msdcs.domain. Will try again later.

This behavior is symptomatic of a duplicate object in Active Directory of the replication partner.

To fix this problem:

01. Install the Support Tools if you haven't already done so.

02. Ping the GUID-based DNS name from the event log Warning message to obtain the IP address of the replication partner.

03. Run Ldp.exe.

04. Press Connect on the Connection menu.

05. Type the IP address from step 02 into the Server dialog and press OK.

06. Press Bind on the Connection menu.

07. Enter the credentials of a domain administrator and press OK.

08. Press Search on the Browse menu.

09. Press Subtree.

10. Type the domain name that you want to search into the Base Dn dialog (CN=Configuration,dc=JSIINC,dc=com)

11. In the Filter dialog, type the Relative Distinguished Name of the computer object. If the replication partner computer name is XYZ, type CN=XYZ.

12. To delete any object in the right-hand pane, press Delete on the Browse menu and type the distinguished name of the object. 13. Verify that the object has been deleted.

NOTE: You may wish to view the How to Use the Windows 2000 LDP Support Tool to View the BaseDN Knowledge Base article.

14. If you cannot find a duplicate object:

           A. Temporarily move the replication partner to a new site or OU.

           B. Use the RepAdmin.exe support tool to synchronize the configuration and domain naming contexts:

                 repadmin /sync CN=Configuration,DC=company,DC=com <local domain controller name> <replication partner GUID>

                 repadmin /sync DC=company,DC=com <local domain controller name> <replication partner GUID>

            C. Wait for replication to complete and insure that there are no new event ID 1083 Warming messages.

           D. Move the replication partner back to its' original site or OU.

           E. Use the RepAdmin.exe support tool to synchronize the configuration and domain naming contexts:

                 repadmin /sync CN=Configuration,DC=company,DC=com <local domain controller name> <replication partner GUID>

                 repadmin /sync DC=company,DC=com <local domain controller name> <replication partner GUID>

            F. Wait for replication to complete and insure that there are no new event ID 1083 Warming messages.