Active Directory replication fails with event 1084 and status 8206: "The directory service is busy"

Applies to: Windows Server 2008 Service Pack 2Windows Server 2008 R2 Service Pack 1Windows 7

Symptoms


You notice that Active Directory replication is blocked, and you receive some events that resemble the following: 

Log Name:    Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Event ID:      1084
Task Category: Replication
Level:         Error
Keywords:      Classic
Description:
Internal event: Active Directory Domain Services could not update the following object with changes received from the following source directory service. This is because an error occurred during the application of the changes to Active Directory Domain Services on the directory service.
 
Object:
<object DN>
Object GUID:
<object GUID>
Source directory service:
<GUID-based partner DNS name>
 
Synchronization of the directory service with the source directory service is blocked until this update problem is corrected.
 
This operation will be tried again at the next scheduled replication.
 
User Action
Restart the local computer if this condition appears to be related to low system resources (for example, low physical or virtual memory).
 
Additional Data
Error value:
8206 The directory service is busy.

 

Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Event ID: 1173
Description:
Active Directory Domain Services has encountered the following exception and associated parameters.
Exception: e0010002
Parameter: 0
Additional Data
Error value: 8443
The replication operation encountered a database inconsistency.

You notice that the object was recently moved from one domain to the location that's specified in the event. You notice that the original object still exists on some of the DCs, and the new object is on other DCs in the forest. You decide to delete the source object. But that does not resolve the problem.

When you enable NTDS diagnostics logging for category replication at level 3, you see the following event: 

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Event ID:      2894
Task Category: Replication
Level:         Information
Keywords:      Classic
Description:
The destination Active Directory Domain Controller logging this event processed a link value update on the source object below. The change was not applied because the source object is in the recycled state on the destination Active Directory Domain Controller.
 To correct this condition, the destination Active Directory Domain Controller will re-request a re-ordered list of updates from the source Active Directory Domain Controller.
 
Source Object GUID:
<object GUID>
Attribute:
<attribute name> 
Target Object DN:
<object DN>

Cause


When objects are moved between domains, the process has two transactions:

  1. The object is created in the target domain with all the attributes required. The moved object has the same objectGUID as the source object, so the two objects cannot live on the same system.
  2. The source domain has a new object move proxy object in the Infrastructure container and the original object is removed from the database.

You get into this situation when the second transaction is failing for some reason. In most cases, the replication engine would resolve this problem, in particular combination of events the condition cannot be resolved due to the way the deleted objects and phantoms are represented in the database.

Resolution


This hotfix is also available at Microsoft Update Catalog

Hotfix information

A 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 website:

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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:  
  • Version

    Product

    Milestone

    Service branch

    6.0.600 2.23xxx

    Windows Server 2008

    SP2

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
  •  

    For all supported x86-based versions of Windows Server 2008

    File name

    File version

    File size

    Date

    Time

    Platform

    Ntdsai.dll

    6.0.6002.23134

    1,957,888

    7-Jun-13

    2:56

    x86

     

    For all supported x64-based versions of Windows Server 2008

    File name

    File version

    File size

    Date

    Time

    Platform

    Ntdsai.dll

    6.0.6002.23134

    2,657,280

    7-Jun-13

    3:34

    x64

    Windows Server 2008 R2 file information notes

    Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

    • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:  

    Version

    Product

    Milestone

    Service branch

    6.1.760 1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

    • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

     

    For all supported x64-based versions of Windows Server 2008 R2

    File name

    File version

    File size

    Date

    Time

    Platform

    Ntdsai.dll

    6.1.7601.22351

    2,745,856

    7-Jun-13

    5:16

    x64

    Status

    Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

    More Information

    For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

    824684 Description of the standard terminology that is used to describe Microsoft software updates

    Additional file information

    Additional file information for Windows Server 2008

    Additional files for all supported x86-based versions of Windows Server 2008

    File name

    X86_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6002.23134_none_f319d0edcf7b83d2.manifest

    File version

    Not Applicable

    File size

    12,574

    Date (UTC)

    7-Jun-13

    Time (UTC)

    3:41

    Platform

    Not Applicable

    File name

    Update.mum

    File version

    Not Applicable

    File size

    34,030

    Date (UTC)

    10-Jun-13

    Time (UTC)

    9:27

    Platform

    Not Applicable

    Additional files for all supported x64-based versions of Windows Server 2008

    File name

    Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6002.23134_none_4f386c7187d8f508.manifest

    File version

    Not Applicable

    File size

    12,632

    Date (UTC)

    7-Jun-13

    Time (UTC)

    4:24

    Platform

    Not Applicable

    File name

    Update.mum

    File version

    Not Applicable

    File size

    34,338

    Date (UTC)

    10-Jun-13

    Time (UTC)

    9:26

    Platform

    Not Applicable

    Additional file information for Windows Server 2008 R2

    Additional files for all supported x64-based versions of Windows Server 2008 R2

    File name

    Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.1.7601.22351_none_4f47871ee9033495.manifest

    File version

    Not Applicable

    File size

    3,531

    Date (UTC)

    7-Jun-13

    Time (UTC)

    5:48

    Platform

    Not Applicable

    File name

    Update.mum

    File version

    Not Applicable

    File size

    41,907

    Date (UTC)

    7-Jun-13

    Time (UTC)

    22:02

    Platform

    Not Applicable

    More Information


    In this particular customer situation, we found that the source object was gone on a few of the DCs of the source domain and they had the new object of the target domain in the database. Therefore, technically, the object was lingering on the problem DCs within the scope of the domain.

    When we ran "Repadmin /removelingeringobjects" on the problem DCs with a clean reference DC, the problem object was removed, and the new object could replicate into the database. The key is that the reference DC is not a global catalog, so it does not carry an object with that particular objectGUID.

    Windows Server 2012 resolves one combination of object and phantom states that trigger this problem.

    We experienced several side problems after we used Lingering Object Removal:

    • Several link values of the new object were out of sync on a subset of the DCs. We created ldifde import to remove and re-add the values so they would replicate out again.
    • Some DCs started to experience access violations in LSASS. The customer removed and re-added the Global Catalog role, and then the DCs were stable.
    • Replication error 8464:

    Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.

    • At the bottom of the "repadmin /showrepl" output were "Access Denied" errors reported. We could not track these down.

    On the two DCs affected by the problem, we ran DCPROMO demotion and repromotion. This resolved the problems.