| Previous | Next |
| STATUS_TRANSACTION_REQUEST_NOT_VALID | STATUS_TRANSACTION_ALREADY_ABORTED |
STATUS_TRANSACTION_NOT_REQUESTED
STATUS_TRANSACTION_NOT_REQUESTED means that a caller invoked a response API for which KTM had not issued the corresponding request. It is a protocol-sequencing result: the response cannot be accepted because the expected notification was never delivered to that participant.
It differs from STATUS_TRANSACTION_REQUEST_NOT_VALID. The latter is a broader state-machine rejection; not-requested points specifically to a missing request/notification pair. The notification mask and the actual queue or callback trace are therefore more useful than retrying the response call.
A response does not match KTM’s notification sequence
- Record the notification type, enlistment handle, transaction ID, and the response routine that was called.
- Verify that the enlistment subscribed to the matching notification and that the callback was not cancelled or consumed elsewhere.
- Do not manufacture a completion response after an application timeout; wait for a real KTM request or resolve the transaction through its documented recovery path.
References
- Microsoft: creating a KTM resource manager
- Microsoft: KTM enlistment objects
- Microsoft: KTM transaction notifications
Looking for a different code? Search another status or error code.