| Previous | Next |
| STATUS_INVALID_IMAGE_NE_FORMAT | STATUS_RXACT_COMMIT_FAILURE |
STATUS_RXACT_INVALID_STATE
RXACT lifecycle rules were violated
RXACT contexts move through distinct preparation, application, commit, and abort states. This error occurs when the requested operation does not make sense in the current state, such as beginning another transaction for a subtree that already has one or applying actions when no transaction is active.
Retrying the same call without inspecting the context normally repeats the failure. The useful evidence is the sequence of RXACT calls and the point where ownership changed, especially in error paths that commit twice, abort after commit, or reuse a context after cleanup.
What to inspect
- Trace initialization, action insertion, commit, abort, and context destruction.
- Look for two threads or modules sharing one transaction context.
- Verify that failure cleanup does not execute both commit and abort paths.
- Recreate the context only after the previous state has been resolved safely.
References
- ReactOS RTL source: RXACT implementation
- ReactOS source: Configuration Manager
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.