| Previous | Next |
| ERROR_TRANSACTION_ALREADY_COMMITTED | ERROR_RESOURCEMANAGER_READ_ONLY |
ERROR_TM_INITIALIZATION_FAILED
The transaction manager did not reach an operational state
ERROR_TM_INITIALIZATION_FAILED belongs to the Windows Kernel Transaction Manager transaction-processing model. A transaction manager is the KTM object that coordinates transaction state and, for a durable TM, owns the log used for recovery. Microsoft documents that a durable transaction manager must be recovered after it is created or reopened before its resource managers perform normal recovery. Initialization failure therefore belongs to the coordinator and its durable state, not to a single transaction request.
Identify the transaction manager and the log or volume associated with it. Correlate the failure with CLFS, storage, and resource-manager events, then check whether the owning service completed its documented TM creation and recovery sequence. Replaying client transactions while the TM is unavailable only produces secondary errors. For a custom RM, capture the result of CreateTransactionManager or OpenTransactionManager and RecoverTransactionManager separately so a log-open failure is not hidden behind a generic initialization message.
What to inspect
- Determine whether the TM is durable or volatile and identify its owning component.
- Check TM recovery and CLFS or storage errors that precede the initialization failure.
- Do not treat restarting an individual transaction as a substitute for recovering the transaction manager.
References
- Microsoft: transaction managers and durable logs
- Microsoft: creating and recovering a KTM resource manager
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: KTM resource-manager log streams and recovery
Looking for a different code? Search another status or error code.