| Previous | Next |
| STATUS_TRANSACTION_MUST_WRITETHROUGH | STATUS_EXPIRED_HANDLE |
STATUS_TRANSACTION_NO_SUPERIOR
STATUS_TRANSACTION_NO_SUPERIOR means that the requested operation assumes a superior enlistment, but the transaction has none. A superior transaction manager coordinates outcomes for a transaction tree; ordinary resource-manager enlistments do not automatically provide that role.
Do not confuse this with STATUS_TRANSACTION_SUPERIOR_EXISTS or STATUS_TRANSACTION_NOT_ROOT. Those report an existing superior or an invalid branch position; no-superior says the expected coordinator role was never established for this transaction.
A superior transaction-manager role is missing
- Verify whether the workflow actually requires a superior coordinator, rather than a normal resource-manager enlistment.
- Trace transaction creation and enlistment order to see whether the coordinator failed to create its superior enlistment.
- Do not add a superior late without checking root status, notification requirements, and recovery responsibilities.
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.