Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Checkpoing with the PDC error?

Status
Not open for further replies.

MrPlough69

IS-IT--Management
May 17, 2005
39
GB
Hi all,

On one of our domain controllers (all windows 2000 standard server SP4) we're getting the following error in the event log:

Source: NTDS Replication, EventID: 1586

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. The error returned was: The naming context is in the process of being removed or is not replicated from the specified server.

This started to happen after the main FSMO roles were moved to a new server. The server with the error is the infrastructure master and holds no other FSMO roles.

Can any one help!

Cheers in advance.
 
eventid.net gives this:

Comments Ionut Marin (Last update 9/17/2004):
See Q326855 for details on this error.

Anonymous (Last update 7/26/2004):
In our case, this message occurred when the DCs had different date/time settings. After we set all DCs to the exact same date/time, the error disappeared.

Adrian Grigorof
This message occur when a domain controller holding the PDC operation master role cannot successfully communicate with downlevel backup domain controllers. See Q269417 for details.


Aftertaf
________
I reserve the right to be wrong, be confused, be suffering because it is monday, or because it is nearly the weekend.
 
Heya,

thanks for the swift reply.

First of all, the domain controllers all have their time correctly synchronised.

The first knowlege base article (Q326855) refers to the setup of exchange, which we don't even run.

Tried what it says in Q269417 but we start getting global catalogue errors on all of the servers.

Any ideas?

cheers in advance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top