| Previous | Next |
| STATUS_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION | STATUS_TRANSACTION_RECORD_TOO_LONG |
STATUS_TRANSACTION_RESPONSE_NOT_ENLISTED
STATUS_TRANSACTION_RESPONSE_NOT_ENLISTED is a notification-mask mismatch on a superior enlistment. A superior transaction manager is responding to a completion phase that was not requested when that enlistment was created, so KTM cannot accept the response.
It is not enough that the transaction itself is valid. KTM delivers only the notification classes an enlistment registered to receive, and the superior path has its own pre-prepare, prepare, commit, rollback, and recovery responsibilities.
The superior enlistment lacks the required response notification
- Log the
NotificationMaskpassed when the superior enlistment was created and the completion routine later called. - Match each response to the actual KTM notification that caused it, including transaction ID and enlistment handle.
- Correct the registration contract before retrying; a duplicate completion call cannot add a missing notification right.
References
- Microsoft: creating a superior transaction manager
- Microsoft: KTM transaction notifications
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.