| Previous | Next |
| ERROR_CANT_ACCESS_DOMAIN_INFO | ERROR_INVALID_DOMAIN_STATE |
ERROR_INVALID_SERVER_STATE
The security-account server lifecycle does not allow this operation now
SAM and LSA expose stateful security databases through server and policy handles. ERROR_INVALID_SERVER_STATE indicates that the server reached a valid service state, but not one in which the requested security operation is permitted. This differs from a bad RPC handle and from ERROR_SERVER_DISABLED, which identifies a particular disabled-server precondition.
Correlate the status with startup, shutdown, restore, role change or security-database maintenance on the same machine. Reopening the same object handle does not necessarily change the server lifecycle state. For automation, log the operation and server identity and stop destructive retries until the state transition is understood; repeated writes during account-database recovery can make diagnosis harder.
What to inspect
- Capture service/startup state and recent security-account database events.
- Verify the request is sent to the intended server, not a node in a different lifecycle phase.
- Retry only after the relevant state transition; do not treat this as a malformed account name.
References
Looking for a different code? Search another status or error code.