| Previous | Next |
| ERROR_DS_CANT_ADD_TO_GC | ERROR_DS_SOURCE_AUDITING_NOT_ENABLED |
ERROR_DS_NO_CHECKPOINT_WITH_PDC
PDC coordination could not be captured while changes were still arriving
Security-principal migration and domain-move workflows can require a checkpoint with the PDC emulator so that the operation starts from a stable authoritative state. This status indicates that the checkpoint could not be obtained, commonly because the PDC was processing too many concurrent modifications or the coordination window could not be established.
Measure update load and replication state on the PDC emulator, then retry during a quieter window. Confirm that the role owner is reachable and that the migration tool is using the intended controller. Do not solve the issue by repeatedly launching more parallel jobs; that increases the modification stream that prevents checkpointing. Persistent failure warrants investigation of PDC health, Directory Service events, and any stuck migration operation.
What to inspect
- Confirm PDC emulator ownership and reachability.
- Review modification load and directory events on that DC.
- Serialize or throttle migration batches before retrying.
References
- Microsoft: source PDC requirements
- Microsoft: role-owner use during domain moves
- MS-ADTS: RID-master and move coordination
Looking for a different code? Search another status or error code.