| Previous | Next |
| STATUS_SXS_RELEASE_ACTIVATION_CONTEXT | STATUS_RECOVERY_NOT_NEEDED |
STATUS_HEURISTIC_DAMAGE_POSSIBLE
A successful return does not prove that every branch reached the same outcome
This informational KTM status belongs to distributed or propagated transaction processing. A heuristic participant can make a local decision when it can no longer complete the normal coordination sequence. The coordinator may finish the commit request while still being unable to prove that every subordinate branch committed consistently.
Treat the result as a data-consistency incident rather than as a retryable API failure. Repeating the commit cannot safely reconstruct which resource managers changed durable state. The useful evidence is the transaction identifier, the participant list, each enlistment outcome, and the application-level records affected by the transaction.
What to inspect
- Correlate the transaction ID with transaction-manager and resource-manager logs on every participating host.
- Verify the durable state of each resource independently instead of assuming an all-or-nothing result.
- Preserve recovery information and avoid compensating writes until the inconsistent branches are identified.
- Distinguish this status from an ordinary rollback or a transaction that never entered commit processing.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Kernel Transaction Manager overview
- Microsoft: writing a resource manager
- Microsoft: enlistment objects
Looking for a different code? Search another status or error code.