| Previous | Next |
| ERROR_CURRENT_TRANSACTION_NOT_VALID | ERROR_RESOURCEMANAGER_NOT_FOUND |
ERROR_TRANSACTION_NOT_FOUND
KTM cannot locate the transaction object the caller asked to open
ERROR_TRANSACTION_NOT_FOUND belongs to the Windows Kernel Transaction Manager transaction-processing model. KTM transaction objects have identifiers and handles. OpenTransaction opens an existing transaction by its transaction ID; this status indicates that the requested object is not available to open. That is different from ERROR_INVALID_TRANSACTION, where a supplied handle is invalid. Here the lookup itself failed to find the transaction object.
Record the transaction GUID and the transaction manager context that produced it. Check whether the transaction already completed and its object lifetime ended, whether the identifier belongs to another coordinator, or whether a restart changed the durable transaction state available after recovery. For distributed transactions, compare the local branch identifier with the root transaction identity rather than assuming they are interchangeable. Avoid caching transaction IDs indefinitely without also tracking transaction-manager identity and recovery generation.
What to inspect
- Log the exact transaction ID passed to OpenTransaction.
- Check whether the transaction completed, was rolled back, or belongs to another transaction manager.
- Invalidate persisted transaction references when the owning transaction-manager state is recreated.
References
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- Microsoft: KTM programming model and transaction handles
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.