| Previous | Next |
| STATUS_CRM_PROTOCOL_NOT_FOUND | STATUS_TRANSACTION_REQUEST_NOT_VALID |
STATUS_TRANSACTION_SUPERIOR_EXISTS
STATUS_TRANSACTION_SUPERIOR_EXISTS is specific to KTM transaction hierarchy. A superior transaction manager coordinates outcomes for subordinate participants; KTM permits only one superior enlistment per transaction, while other resource managers may still create subordinate enlistments.
This is not a simple duplicate-handle error. Creating another superior would create conflicting owners of the prepare and commit sequence. If the caller merely needs to participate, it must use a subordinate enlistment rather than attempting to become a second coordinator.
A second superior enlistment was requested
- Identify which component created the existing superior enlistment and whether it owns the expected commit path.
- Verify that code requesting superior rights executes only for the intended root coordinator.
- Keep the superior and subordinate roles explicit in diagnostics; a generic transaction handle does not reveal that role by itself.
References
- Microsoft: creating a superior transaction manager
- Microsoft: KTM transaction notifications
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.