ERROR_TRANSACTION_SUPERIOR_EXISTS - 6709 (0x1A35)

The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.

Updated: Feb 21, 2026

Technical Meaning

This error code indicates that a transaction object already has an existing superior enlistment, and the operation attempted would have created a new superior. Only one superior enlistment is allowed per transaction.

Error Details

The ERROR_TRANSACTION_SUPERIOR_EXISTS error occurs when attempting to create or modify a transaction object in such a way that it would result in having more than one superior enlistment. This error is specific to the Windows Transaction Manager and its operations on transaction objects within the context of distributed transactions.

Usage Context

This error typically arises during the execution of operations involving transactional resources, where multiple layers or levels of transaction management are attempted. It can occur in scenarios such as nested transactions or when attempting to enlist a resource manager that is already enlisted at a higher level.

Developer Interpretation

Developers should ensure that their code correctly manages transactional contexts and avoids creating redundant superior enlistments. This error suggests that the operation was not allowed due to existing transactional constraints, which are designed to maintain consistency and integrity within distributed transactions.

Related Errors

  • ERROR_TRANSACTION_NOT_ENLISTED (0x1A34): The transaction is not enlisted in any resource manager.
  • ERROR_TRANSACTION_INTEGRITY (0x1A36): A transactional operation failed due to a detected inconsistency or corruption.

FAQ

Q: What does the error mean?

The error means that an attempt was made to create a new superior enlistment for a transaction object, but it already has one. Only one superior enlistment is allowed per transaction.

Q: How can I resolve this issue?

Ensure that your code correctly manages transactional contexts and avoids creating redundant superior enlistments. Review the operation context and validate parameters to ensure they align with transactional requirements.

Summary

The ERROR_TRANSACTION_SUPERIOR_EXISTS error is a specific technical error indicating an attempt to create a new superior enlistment for a transaction object that already has one. Developers should manage transactional contexts carefully to avoid this issue.