| Previous | Next |
| STATUS_TRANSACTION_NOT_ACTIVE | STATUS_RM_NOT_ACTIVE |
STATUS_TM_INITIALIZATION_FAILED
Transaction-manager startup failed before it became usable
A durable KTM transaction manager is tied to a log and must establish its identity, open the log, and recover its state before resource managers and transactions can be used. Failure at this stage can reflect log access, storage, identity, permissions, or damaged recovery data.
Do not diagnose this as an individual transaction failure. The transaction-manager object itself did not become operational, so every dependent resource manager can fail until the initialization problem is resolved.
What to inspect
- Capture the transaction-manager log path, identity GUID, creation flags, and underlying error returned by the initialization call.
- Check filesystem permissions, free space, log-container availability, and storage events.
- Determine whether the manager is new, being reopened, or being recovered after an unclean shutdown.
- Do not delete or replace the log until its recovery role and identity have been established.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: transaction manager objects
- Microsoft: writing a resource manager
- Microsoft: using log streams with KTM
Looking for a different code? Search another status or error code.