| Previous | Next |
| ERROR_TRANSACTIONAL_CONFLICT | ERROR_RM_METADATA_CORRUPT |
ERROR_RM_NOT_ACTIVE
The resource manager is not currently accepting normal transactional work
ERROR_RM_NOT_ACTIVE belongs to the Windows Kernel Transaction Manager transaction-processing model. A KTM resource manager must be created or opened, associated with its transaction manager, and recovered as required before it handles transaction notifications normally. Microsoft documents a startup sequence in which a durable TM is recovered first and the RM then recovers its own state. An inactive RM can therefore be known to KTM but not ready to enlist or process transactional work.
Check RM startup and shutdown transitions, not only the transaction that reported the error. Look for an earlier initialization, recovery, log, or fatal notification-processing failure that caused the RM to stop. If the RM is intentionally shutting down, reject new work at a higher layer instead of repeatedly enlisting. For a custom RM, log the completion of creation, RecoverResourceManager, notification registration, and service-ready publication as separate milestones.
What to inspect
- Find the first RM startup, recovery, or shutdown error before this status.
- Verify RecoverTransactionManager and RecoverResourceManager ordering for durable state.
- Do not send new transactional work to an RM that has not published an active state.
References
- Microsoft: creating and recovering a KTM resource manager
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- Microsoft: KTM resource-manager log streams and recovery
Looking for a different code? Search another status or error code.