Windows error 8610 (ERROR_DS_ROLE_NOT

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: a DC cannot activate its FSMO role until the owning partition has replicated.

Previous	Next
ERROR_DS_CANT_MOVE_APP_QUERY_GROUP	ERROR_DS_WKO_CONTAINER_CANNOT_BE_SPECIAL

ERROR_DS_ROLE_NOT_VERIFIED

FSMO ownership exists in metadata but the role is not yet trusted for use

Microsoft documents an initial-replication safeguard for FSMO roles. A role holder normally does not perform the single-master operation until it has successfully inbound-replicated the naming context that stores the role since Directory Services started. This prevents a restarted DC from acting on stale role-ownership or directory state.

Determine which FSMO role and naming context are named in the event, then diagnose replication for that partition. DNS, connectivity, authentication, or all partners being offline can prevent verification. Transferring the role elsewhere may hide the symptom without correcting the replication failure; seizure is appropriate only when the prior owner cannot return and the operational consequences are understood.

What to inspect

Map the role to its owning naming context and inspect inbound replication.
Use repadmin and Directory Service events to find the first replication error.
Do not force role validation until the topology and partner availability are understood.

References

Looking for a different code? Search another status or error code.