Article ID: 285858 - Last Review: January 29, 2007 - Revision: 3.3

Error Message: The Replication System Encountered an Internal Error

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q285858
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

On domain controllers (DCs) that are already running in a domain, the following event may appear in the Directory Service event log:
Event ID 1084
Description:
Replication error: The directory replication agent (DRA) couldn't update object CN="8f03823f-410c-4483-86cc-8820b4f2103f
DEL:66aab46a-2693-4825-928f-05f6cd12c4e6",CN=Deleted Objects,CN=Configuration,DC=company,DC=com (GUID 66aab46a-2693-4825-928f-05f6cd12c4e6) on this system with changes which have been received from source server 62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.company.com. An error occurred during the application of the changes to the directory database on this system.
When you run Dcpromo.exe on a new DC, the promotion may not work, and you may receive the following error message:
The replication system encountered an internal error.
After you receive the preceding error message, the following entry may appear in the Dcpromoui.log file:
dcpromoui t:0x310 01775
Enter State::SetOperationResultsMessage
The Directory Service failed to replicate the partition CN=Configuration,DC=company,DC=com from remote server server.child.company.com.
dcpromoui t:0x310 01776 Exit DoProgressLoop
dcpromoui t:0x310 01777 Exit DS::CreateReplica
dcpromoui t:0x310 01778 Exception caught
dcpromoui t:0x310 01779 catch completed
dcpromoui t:0x310 01780 handling exception
dcpromoui t:0x310 01781 Active Directory Installation Failed
dcpromoui t:0x310 01782 Enter GetErrorMessage 800720FA
dcpromoui t:0x310 01783 Exit GetErrorMessage 800720FA
dcpromoui t:0x310 01784 The replication system encountered an internal error.
To determine if you are experiencing this exact problem, please see the "More Information" section of this article.
Back to the top

CAUSE

This problem can occur when an orphan object is present in the Active Directory. Objects can become orphaned after their parents are deleted and then removed from the Active Directory by the garbage collector.
Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910  (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
   Date         Time     Version          Size        File name
   -----------------------------------------------------------------
   2/15/2001   06:17p   5.0.2195.3261   495,888   Lsasrv.dll(56-bit)
   2/21/2001   10:51a   5.0.2195.3200   350,992   Advapi32.dll
   2/21/2001   10:49a   5.0.2195.3261   513,808   Instlsa5.dll
   2/21/2001   10:51a   5.0.2195.3238   141,072   Kdcsvc.dll
   1/26/2001   08:46p   5.0.2195.3194   207,920   Kerberos.dll
   1/26/2001   07:51p   5.0.2195.3194    69,456   Ksecdd.sys
   2/15/2001   06:17p   5.0.2195.3261   495,888   Lsasrv.dll
   2/15/2001   06:17p   5.0.2195.3261    33,552   Lsass.exe
   2/21/2001   10:51a   5.0.2195.3277   908,048   Ntdsa.dll
   2/15/2001   06:53p   5.0.2195.3263   381,712   Samsrv.dll
NOTE: The Hotfix should be installed on the domain controller the affected DC is replicating from. In the event message above, it's referenced by the GUID-based name:

62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.company.com.

In the case of DCPROMO, the name of the source computer is in dcpromo.log, close to the top.
Back to the top

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.
Back to the top

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  (http://support.microsoft.com/kb/265173/EN-US/ ) 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  (http://support.microsoft.com/kb/296861/EN-US/ ) Use QChain.exe to Install Multiple Hotfixes with One Reboot
There are some changes made to Windows 2000 Service Pack 2 to prevent creation of new orphan objects and thus to avoid the symptoms mentioned in this article. If you are running Windows 2000 Service Pack 2, you might still require this fix if you have orphan objects created prior to the deployment of Service Pack 2. For additional information on Windows 2000 service packs, click the article number below to view the article in the Microsoft Knowledge Base:
260910  (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To obtain more information about the failure that is listed in the "Symptoms" section of this article, set the following levels of diagnostic logging on the server you are replicating from:
  1. Use Registry Editor (Regedt32.exe) to locate the "19 Inter-Site Messaging" value under the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
  2. Note the original values of the following registry entries so you can restore the original values after you identify the problem. On the Edit menu, click DWORD, type 2, and then click OK.
  3. Locate the "5 Replication Events" value under the same key.
  4. On the Edit menu, click DWORD, type 4, and then click OK.
  5. Locate the "9 Internal Processing" value under the same key.
  6. On the Edit menu, click DWORD, type 1, and then click OK.
  7. Quit Registry Editor.
Run Dcpromo.exe again (or wait for replication to run again), and then look for event ID 1173 in the Directory Services event log to locate the following text:
Internal event: Exception e0010002 has occurred with parameters 8442 and 20a0 (Internal ID 11003a1).
The 11003a1 Internal ID confirms that you are seeing the problem that is addressed in this article.

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  (http://support.microsoft.com/kb/249149/EN-US/ ) Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
Back to the top
APPLIES TO
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
Back to the top
Keywords: 
kberrmsg kbbug kbfix kbwin2000presp3fix kbqfe kbwin2000sp3fix kbenv kbdirservices kbhotfixserver KB285858
Back to the top