| Previous | Next |
| ERROR_ENLISTMENT_NOT_FOUND | ERROR_TRANSACTIONMANAGER_NOT_ONLINE |
ERROR_TRANSACTIONMANAGER_NOT_FOUND
The transaction manager identity does not resolve to an available KTM object
ERROR_TRANSACTIONMANAGER_NOT_FOUND belongs to the Windows Kernel Transaction Manager transaction-processing model. A transaction manager is the coordinator object that owns transaction state and, when durable, a recovery log. KTM provides OpenTransactionManager and OpenTransactionManagerById for existing TMs. This error identifies failure at the coordinator-object lookup layer; it is not evidence that one transaction ID is wrong.
Record whether the caller opens the TM by name, log path, or identifier and compare that data with the creation path. Moving or restoring a durable log, renaming a TM, or passing an ID from another machine can break the association. If the owning service recently recreated the TM, old persisted IDs may be stale. Do not silently create a new transaction manager on lookup failure when a durable log is expected: recovery and resource-manager identities must be reconciled first.
What to inspect
- Capture the TM name, identifier, and log path used for the open request.
- Check rename, restore, migration, and service-reinstallation history.
- Recover the intended durable TM rather than creating a new coordinator with unrelated identity.
References
- Microsoft: transaction managers and durable logs
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- Microsoft: creating and recovering a KTM resource manager
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.