Article ID: 825782
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
SYMPTOMS
When a Windows Server 2003-based global catalog server tries to replicate a partial attribute set, the replication does not complete. The following event is logged in the system event log:
Event Source: Active Directory
Event Type: Error
Event ID: 8418
Description:
The replication operation failed because of a schema mismatch between the servers involved.
If you run the repadmin /showreps /v command, you receive output similar to the following:
DC=<DomainComponent>,DC=<DomainComponent>,DC=<DomainComponent>
<SiteName>\<ReplicationPartnerName> (deleted DSA) via RPC
DC object GUID: <ReplicationPartnerGUID>
Address: <ReplicationPartnerGUID>._msdcs.DomainName
DC invocationID: <InvocationID>
DO_SCHEDULED_SYNCS COMPRESS_CHANGES NO_CHANGE_NOTIFICATIONS PARTIAL_ATTRIBUTE_SET
USNs: 0/OU, 500803/PU
Last attempt @ 2003-03-20 01:47:48 was successful.
The output of the Repadmin.exe command shows the following:
- The global catalog server is trying to replicate with a global catalog server that has been deleted.
- The replication entry for the deleted global catalog server includes PARTIAL_ATTRIBUTE_SET as one of its descriptors.
- The last replication attempt occurred at a time in the past (beyond an ordinary replication interval). This indicates that the global catalog server has not recently tried to obtain the partial attribute set from the deleted replication partner.
CAUSE
This problem may occur when the partial attribute set changes and then the global catalog server tries to obtain the new partial attribute from a replication partner that has been deleted (for example, a demoted domain controller).
RESOLUTION
Hotfix Information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
File Information
The English version of this hotfix has the file attributes (or later) 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.
Date Time Version Size File name --------------------------------------------------------- 29-Apr-2003 21:34 5.2.3790.2 1,365,504 Ntdsa.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
229896 Using Repadmin.exe to Troubleshoot Active Directory Replication
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB825782
