Windows error 6703 (ERROR_TRANSACTION_NOT

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: A KTM response was issued although no matching request notification was delivered.

Previous	Next
ERROR_TRANSACTION_REQUEST_NOT_VALID	ERROR_TRANSACTION_ALREADY_ABORTED

ERROR_TRANSACTION_NOT_REQUESTED

ERROR_TRANSACTION_NOT_REQUESTED is a protocol-pairing error. A resource manager or superior transaction manager has called a response API even though KTM did not issue the corresponding request. In KTM, responses such as completion or vote operations are reactions to specific notifications, not free-standing commands.

What to verify

Capture the received TRANSACTION_NOTIFICATION value before dispatching the callback.
Associate the notification with the exact enlistment handle passed to the response function.
Do not infer a missing request from local transaction state; wait for the notification KTM actually delivered.
Make callback handling idempotent so a delayed, cancelled, or duplicate work item cannot send a second response.

This is different from a normal transaction abort. The failure says that the response has no request-side basis in the KTM protocol, so retrying the same response without a newly received notification does not fix it.

See GetNotificationResourceManager, the notification mask definitions, and the KTM function groups.

Looking for a different code? Search another status or error code.