| Previous | Next |
| STATUS_RM_DISCONNECTED | STATUS_FILE_IDENTITY_NOT_PERSISTENT |
STATUS_ENLISTMENT_NOT_SUPERIOR
Only a superior enlistment can drive the transaction outcome sequence
A normal resource-manager enlistment participates in prepare, commit, and rollback notifications. A superior transaction manager uses a special superior enlistment that can coordinate the outcome for a transaction branch. These roles are not interchangeable.
This status usually indicates that code called a superior-only operation with the wrong enlistment handle or created the enlistment without the required superior relationship. Adding access rights to an ordinary enlistment will not change its role.
What to inspect
- Query and log the enlistment ID, transaction ID, and the API used to create the enlistment.
- Verify which component is intended to coordinate the superior branch.
- Keep ordinary participant and superior-enlistment handles in distinct typed objects.
- Do not recreate the whole transaction until the role mismatch in the caller is understood.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: creating a superior transaction manager
- Microsoft: enlistment objects
- Microsoft: KTM objects and their relationships
Looking for a different code? Search another status or error code.