| Previous | Next |
| ERROR_DS_ROOT_REQUIRES_CLASS_TOP | ERROR_DS_MISSING_FSMO_SETTINGS |
ERROR_DS_REFUSING_FSMO_ROLES
A DC in shutdown is not a valid new FSMO owner
FSMO ownership can move between domain controllers, but role transfer still depends on the target being an active directory service capable of accepting and later servicing single-master updates. A DC that is shutting down refuses new role ownership to avoid committing a transfer into a server state that is disappearing.
This status is a lifecycle condition, not evidence that the FSMO metadata is corrupt. Repeated transfer attempts during service stop or server restart will not make the target suitable. First determine why AD DS is shutting down and whether the selected target is actually the DC that should hold the role.
What to inspect
- Check Directory Service and System events around the refusal time and confirm the AD DS service/server shutdown state.
- Select a healthy, replicating target DC and verify it hosts the relevant NC before transferring the role.
- Do not seize a role merely because one proposed target refused it during shutdown; seizure addresses an unavailable current owner, not a transient target state.
References
Looking for a different code? Search another status or error code.