| Previous | Next |
| STATUS_TRANSACTION_NOT_REQUESTED | STATUS_TRANSACTION_ALREADY_COMMITTED |
STATUS_TRANSACTION_ALREADY_ABORTED
STATUS_TRANSACTION_ALREADY_ABORTED is a terminal-outcome status. The requested operation arrived after the transaction had already been aborted, so it cannot be used to continue preparation or to commit the original work.
The correct distinction is between a known abort and an unknown outcome after a crash. A known abort should lead to rollback cleanup and a new transaction for any retry. An unknown or in-doubt recovery case requires the resource manager’s recovery records and KTM notifications rather than an optimistic re-submit.
Rollback already decided the transaction outcome
- Correlate the abort with the responsible caller, timeout, resource-manager failure, or recovery event.
- Discard uncommitted transactional state only after the rollback path has completed its required cleanup.
- Start a new transaction for a retry; do not attempt to reopen the aborted transaction as if it could become active again.
References
- Microsoft: Kernel Transaction Manager overview
- Microsoft: understanding KTM transaction-processing components
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.