| Previous | Next |
| ERROR_TRANSACTION_OBJECT_EXPIRED | ERROR_TRANSACTION_RECORD_TOO_LONG |
ERROR_TRANSACTION_RESPONSE_NOT_ENLISTED
This status applies to a superior enlistment. KTM rejected an operation because that enlistment was not created with the matching completion response in its NotificationMask. The mask is part of the enlistment contract: it declares which protocol notifications and completion responses the participant can handle.
How to diagnose the mismatch
- Inspect the
NotificationMaskpassed toCreateEnlistment. - Record the notification that led to the response call and the exact enlistment handle used.
- Verify that the code is executing as a superior transaction manager rather than as an ordinary resource manager.
- Recreate the enlistment with the required mask before the transaction reaches the relevant phase; changing a local callback table later is not enough.
Do not confuse this with ERROR_TRANSACTION_NOT_REQUESTED. Here a notification may have been received, but the enlistment did not declare the corresponding response capability. In the other case, there was no matching KTM request at all.
See CreateEnlistment, NOTIFICATION_MASK, and KTM enlistment APIs.
Looking for a different code? Search another status or error code.