| Previous | Next |
| ERROR_DS_BACKLINK_WITHOUT_LINK | ERROR_DS_SRC_NAME_MISMATCH |
ERROR_DS_EPOCH_MISMATCH
Cross-domain move participants have different object epochs
A cross-domain move is coordinated between directory servers that must agree on current object and forest state. This status means the two participants do not have the same epoch view for the object involved. It is not the same as a malformed DN or an ordinary intra-domain rename.
Replication latency is the first structural issue to investigate: one DC may not have received the newest object version or related move state. Because cross-domain move rules span source and destination NCs, checking only the destination object in one LDAP session can miss the divergence. Object replication metadata can show which server originated the current version and whether partners have converged.
What to inspect
- Compare the object on the source and destination-side DCs and inspect replication metadata for version, originator, USN, and timestamp.
- Verify successful replication of the relevant domain NCs before restarting the move workflow.
- Do not recreate the object with a new identity as a first response; that changes the problem from move coordination to object migration.
References
Looking for a different code? Search another status or error code.