| Previous | Next |
| ERROR_RXACT_INVALID_STATE | ERROR_SPECIAL_ACCOUNT |
ERROR_RXACT_COMMIT_FAILURE
The security account update failed at its transaction commit stage
This code reports an internal security-database corruption encountered while committing a transaction. It is later in the update lifecycle than simple name or membership validation and should be treated as an indeterminate write outcome from the caller perspective. The security database may have rejected the commit, but a multi-step management workflow can still have other changes that succeeded before the failing transaction.
Do not immediately repeat the same provisioning batch. Query every principal or membership edge the workflow intended to modify and compare the actual state with the transaction log maintained by the application. Correlate the failure with security-account database and storage events. Direct registry-subtree manipulation is not a safe substitute for SAMR, NetAPI or LSA operations.
What to inspect
- Stop blind retry loops and read back the affected account state.
- Correlate the commit failure with storage and security-service events.
- Resume from verified state through supported account APIs rather than editing database files or hives directly.
References
Looking for a different code? Search another status or error code.