| Previous | Next |
| ERROR_TRANSACTION_NOT_ACTIVE | ERROR_TRANSACTION_NOT_REQUESTED |
ERROR_TRANSACTION_REQUEST_NOT_VALID
This status means the requested KTM operation does not belong to the transaction's current state. The problem is therefore the ordering or role of the call, not necessarily the validity of the handle. KTM separates transaction requests, resource-manager notifications, enlistment completion calls, and recovery operations; each is valid only in the appropriate phase.
Typical diagnosis
- Identify the exact KTM function that returned the error and the transaction or enlistment handle supplied to it.
- Build a timeline of
CreateTransaction, enlistment, notification delivery, prepare, commit, rollback, and completion calls. - Check that a callback does not issue a completion method for a different notification or a different enlistment.
- After a terminal outcome, create or open the appropriate new transaction instead of continuing the earlier protocol sequence.
For a resource manager, the relevant state is often visible in the notification delivered through GetNotificationResourceManager. The notification type and the enlistment's notification mask determine which response is legal.
See KTM functions, GetNotificationResourceManager, and the NOTIFICATION_MASK reference.
Looking for a different code? Search another status or error code.