| Previous | Next |
| ERROR_DS_EXISTING_AD_CHILD_NC | ERROR_DS_DISALLOWED_IN_SYSTEM_CONTAINER |
ERROR_DS_REPL_LIFETIME_EXCEEDED
Tombstone lifetime is a replication safety boundary
Deleted objects remain represented long enough for the deletion state to replicate, but after the tombstone lifetime they can be garbage-collected. A DC that has been disconnected longer than that interval may still contain objects that healthy replicas have already deleted and forgotten. Reintroducing its changes can create lingering-object inconsistencies.
For that reason, error 8614 is not a normal “partner was offline” timeout. Microsoft documents it as a protective replication block. The recovery decision depends on which DC has trustworthy data, how long replication has been broken, and whether lingering objects exist. Simply disabling the safety check can allow stale data back into the directory.
What to inspect
- Use replication diagnostics to record the affected NC, source, destination, last-success time, and consecutive failures.
- Compare the elapsed isolation period with the directory’s configured deletion/tombstone lifetime and investigate clock jumps as well as real disconnection.
- Follow the supported 8614/lingering-object recovery path; do not force replication before deciding whether the stale DC should be cleaned, demoted, or rebuilt.
References
- Microsoft replication error 8614
- MS-DRSR tombstone and lingering-object definitions
- AD replication troubleshooting
Looking for a different code? Search another status or error code.