| Previous | Next |
| XACT_E_CANTRETAIN | XACT_E_COMMITPREVENTED |
XACT_E_COMMITFAILED
The HRESULT reports the outcome, while participant logs reveal the cause
XACT_E_COMMITFAILED means MSDTC could not complete the commit and resolved the transaction as aborted. The outer code does not identify which participant voted no, timed out, lost durable state, or failed during preparation, so the most useful evidence is the correlated transaction identifier across the coordinator and every enlisted resource manager.
Do not rerun the business operation until its idempotency and external side effects are understood. First establish whether Phase One began, which participants reached Prepared, and whether any nontransactional action occurred outside the distributed unit of work. The transaction outcome is abort, but application-level retry can still duplicate work performed by systems that were not enlisted.
Commit-failure timeline to reconstruct
- Distributed transaction or unit-of-work identifier.
- Prepare vote and timestamp from every durable participant.
- MSDTC trace or event showing the first abort decision.
- Nontransactional calls made before the commit request.
References
- Microsoft MS-DTCO: Phase One voting
- Microsoft MS-DTCO: distribution of the final outcome
- PostgreSQL: prepared transactions in a 2PC system
Looking for a different code? Search another status or error code.