| Previous | Next |
| ERROR_DS_NTDSCRIPT_PROCESS_ERROR | ERROR_DS_DRS_EXTENSIONS_CHANGED |
ERROR_DS_DIFFERENT_REPL_EPOCHS
Replication epochs prevent incompatible DC incarnations from synchronizing
MS-DRSR defines the replication epoch as a DC state variable that changes when the controller is no longer compatible for replication with its former partners. During replication, the server compares the client’s epoch with its own and refuses the request when the values differ. This prevents two directory incarnations from being treated as a continuous replication history.
This is not ordinary replication latency. Waiting for the next schedule does not make unequal epochs converge, and forcing a sync can be unsafe. Domain rename and other operations that change replication compatibility can expose the condition. The investigation must identify why one server’s replication identity/state changed.
What to inspect
- Record both DCs, the NC, and surrounding Directory Service events to establish when the epoch divergence began.
- Verify whether a domain rename, restore, reinstallation, or other topology-changing operation occurred.
- Use supported recovery and replication procedures for the specific lifecycle event; do not edit replication-epoch state directly.
References
Looking for a different code? Search another status or error code.