ERROR_ENLISTMENT_NOT_SUPERIOR - 6820 (0x1AA4)
The request was rejected because the enlistment in question is not a superior enlistment.
Updated: Feb 21, 2026
Technical Meaning
The error code ERROR_ENLISTMENT_NOT_SUPERIOR with the numeric value 6820 and hexadecimal representation 0x1AA4 indicates that a request to enlist in a transaction has been rejected because the specified enlistment is not considered superior within the context of the transaction manager.
Error Details
This error typically arises when an attempt is made to enlist a resource manager or transaction manager in a transaction, but the current enlistment does not have the necessary authority or precedence over the existing enlistments. This can occur in scenarios where multiple transactions are being managed simultaneously and there is a hierarchy of enlisting entities.
Usage Context
This error code may be encountered in various contexts involving the Windows Transaction Manager (TM) and its associated resource managers. It is particularly relevant when dealing with distributed transaction processing, where different components or systems need to coordinate their operations within a single transaction scope.
Developer Interpretation
Developers should interpret this error as an indication that the current operation cannot proceed due to the enlistment hierarchy constraints. Specifically, the system enforces a strict order of precedence among enlisting entities, and if the requested enlistment is not at a higher level in this hierarchy, it will be rejected.
Related Errors
ERROR_TRANSACTION_NOT_ENLISTED(0x2009)ERROR_TRANSACTION_INTEGRITY(0x2014)ERROR_TRANSACTION_NO_LOG_SPACE(0x2015)
FAQ
Q: What does the error mean?
A: The request was rejected because the enlistment in question is not a superior enlistment.
Q: How can I resolve this issue?
A: Ensure that the operation context and parameters are correct, and that the current enlistment has the necessary authority to proceed with the transaction.
Summary
The ERROR_ENLISTMENT_NOT_SUPERIOR error code is specific to scenarios involving the Windows Transaction Manager and its management of enlisting entities. It indicates a rejection due to hierarchy constraints within the transaction scope. Developers should focus on ensuring that their operations are correctly structured and that the necessary authority exists for the enlistment.