Inbound Replication Fails on Domain Controllers with Event ID: 1699, Error 8451 or jet error -1601

Inbound replication to Windows Server 2003 domain controllers does not work, and errors are listed in the Directory Services event log of the destination domain controller if NTDS diagnostic logging is set at default levels. The domain controllers that cannot replicate may log the following events in the System log:

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1699
Date: MM/DD/YY
Time: HH:MM:SS
User: username
Computer: Destination_domain_controller_Name
Description: The local domain controller failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send the change requests to the domain controller at the following network address.
Directory partition: DN path of affected replication partition
Network address: DNS CNAME address / objectGUID of source domain controller
Extended request code: 0
Additional Data
Error value: 8451
The replication operation encountered a database error.
The only partition that is failing to replicate is the Partition_Name partition.

Increasing NTDS diagnostic logging levels on the destination domain controller produces additional events that are useful in identifying this issue. For information about how to increase NTDS diagnostic logging, see the More Information section.

In Active Directory Sites and Services, right-click the connections that fail to inbound replicate to the destination domain controller and choose Replicate Now. The following events are logged in the Directory Services event log:

Event Type: Warning
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1173
Date: MM/DD/YY
Time: HH:MM:SS
User: Username
Computer: Destination_domain_controller_Name
Description: Internal event: Active Directory has encountered the following exception and associated parameters.

Exception: e0010004
Parameter: 0

Additional Data Error value: -1047
Internal ID: 205063e

Event Type: Error
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1481
Date: MM/DD/YY
Time: HH:MM:SS
Computer: Destination_domain_controller_Name
Description:
Internal error: The operation on the object failed.

Additional Data:
Error value: 2 000020EF: NameErr: DSID-032500E8, problem 2001 (NO_OBJECT), data -1601, best match of: "

Attempts to re-source read-only copies of domain partitions on global catalogs using repadmin /rehost will fail with the following error: Attempts to demote global catalogs fail, and generate the following error: Attempts to promote additional global catalogs in the forest also fail.

This problem occurs if an Active Directory partition contains one or more objects with an invalid security descriptor. An invalid security descriptor is a security descriptor that is anything less than 8 bytes. This problem occurs if an object or attribute contains a non 8-byte msExchSecurityDescriptor. Microsoft Windows 2000-based domain controllers earlier than Service Pack 4 (SP4) permitted these invalid security descriptors to be created. Windows 2000 SP4 or later versions do not permit the msExchSecurityDescriptors to be written to the global catalogs. However, if an invalid msExchSecurityDescriptor property already exists in the global catalog, it is not removed by the installation of Windows 2000 SP 4 or later versions. Upgrading a Windows 2000 domain controller to Windows Server 2003 does not correct the invalid descriptor.

One scenario that reveals these errors is the running Microsoft Exchange Server 2003 Setup /Forestprep, and /Domainprep in your Microsoft Windows Server 2003-based network.

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 this specific problem. 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 Web site: 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

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Important We recommend that administrators install this hotfix before you run Exchange 2003 FORESTPREP in Active Directory forests that contained Exchange 2000 and pre-SP3 Windows 2000-based domain controllers.

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

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To increase NTDS diagnostic logging, change the following REG_DWORD values in the registry of the destination domain controller under the following registry key:Set the value of the following subkeys to 5:

• 5 Replication Events
• 9 Internal Processing

Note Level 5 logging is extremely verbose and the values of both subkeys should be set back to the default of 0 after the problem is resolved. Filtering the Directory Services event log should be performed to isolate and identify these events.

For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: