What does Windows error code 6708 (ERROR_TRANSACTION_NOT_JOINED) mean?

 
Previous Next
ERROR_RESOURCEMANAGER_READ_ONLY ERROR_TRANSACTION_SUPERIOR_EXISTS

ERROR_TRANSACTION_NOT_JOINED

This status concerns the relationship between a resource manager (RM) and a transaction. KTM has not successfully joined that RM to the transaction, yet the RM attempted a prepare operation. A transaction handle alone is not enough: KTM needs an enlistment object that binds the RM, transaction, notification mask, and optional enlistment key.

What the setup must establish

  • Create or open the correct transaction and resource-manager objects.
  • Create an enlistment using the RM handle and the transaction handle that belong to the same intended unit of work.
  • Preserve the resulting enlistment handle and use it for enlistment-phase operations.
  • Check the original GetLastError from enlistment creation instead of continuing after a failed enlistment.

Do not collapse this error into ERROR_TRANSACTION_NOT_ENLISTED. This one specifically describes an attempted prepare for a transaction that the RM never successfully joined; the latter is a broader missing-enlistment condition for an operation.

See CreateEnlistment, KTM enlistment functions, and the notification mask reference.

For an independent technical walk-through of the Transaction Manager, Resource Manager, and enlistment handle relationship, see NCC Group's KTM introduction.


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