Microsoft KB Archive/269417

= Event 1586 Message: The Checkpoint with the PDC Was Unsuccessful =

Article ID: 269417

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q269417



SYMPTOMS
The following event is generated on a Microsoft Windows 2000-based domain controller in a Windows 2000-based domain that is in Mixed mode:

Event ID: 1586

Source: NTDS Replication

Type: Warning

Description: The checkpoint with the PDC was unsuccessful. The checkpointing process will be retried again in four hours. A full synchronization of the security database to downlevel domain controllers may take place if this machine is promoted to be the PDC before the next successful checkpoint.



CAUSE
This behavior can occur because the domain controller on which this event occurs did not successfully replicate the checkpoint information for downlevel backup domain controllers (BDCs).

If a domain controller is not configured to replicate directly with the primary domain controller (PDC) Floating Single Master Operation (FSMO) role holder, it does not replicate the checkpoint information. This event can also be generated because of network-related problems and in situations where a domain controller is configured to replicate with the PDC FSMO role holder.



RESOLUTION
To resolve this behavior, a connection object can be manually configured in Active Directory (AD) Sites and Services to replicate from the PDC FSMO role holder prior to transferring the FSMO role to a different Windows 2000 domain controller.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
In a mixed mode domain, the PDC FSMO role holder is the single point for replication to Microsoft Windows NT BDCs. The PDC maintains a checkpoint for each BDC representing the most recent replicated change. This process enables partial synchronizations which enables the PDC to update a specific BDC.

Windows 2000 has a multimaster replication scheme. Only a subset of Windows 2000 domain controllers can be configured to replicate directly with the PDC FSMO role holder. If the PDC FSMO role is transferred to a different domain controller, the Windows NT BDCs begin to replicate with the new FSMO role holder. If the new role holder does not have information about each individual BDC's checkpoint, a full synchronization is required by each Windows NT BDC in the domain. This situation could be undesirable under certain circumstances.

At present, only Windows 2000 domain controllers that are configured to replicate directly with the PDC FSMO role holder replicate the checkpoint information. This situation may generate the 1586 event on other domain controllers that do not replicate directly with the PDC FSMO role holder.

If you access AD Sites and Services, you can observe which Windows 2000 domain controllers replicate directly with the PDC FSMO role holder. If you have a specific domain controller designated to assume the PDC role when the current FSMO role holder is unable to function, that domain controller must be configured to replicate directly with the PDC FSMO role holder. If you have a small number of Windows NT BDCs, the preceding scenario cannot be ignored.

If you create a connection that is similar to one that the knowledge consistency check (KCC) would have created (that is, the KCC would have connected the same two domain controllers in the same direction), the KCC does not create another connection between those servers, nor does it delete or modify the connection that you have created.

For information about how to create a connection object, go to Microsoft Windows 2000 Server Help.

Keywords: kbenv kberrmsg kbprb KB269417

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.