| Previous | Next |
| XACT_E_TMNOTAVAILABLE | XACT_E_CONNECTION_DENIED |
XACT_E_CONNECTION_DOWN
Connection loss must be interpreted in the current commit phase
XACT_E_CONNECTION_DOWN means a participant or application had a transaction-manager connection and that channel failed. The consequence depends on protocol state: during active work the transaction may abort, while a prepared durable participant must enter recovery and learn the final outcome later.
Correlate the disconnect with the last protocol message rather than treating every case as a network retry. Record whether prepare was acknowledged, whether a commit decision was durably logged, and which side restarted. If the branch was Prepared, preserve its state and reenlist. If no durable work existed, the application may start a new transaction after verifying that the failed attempt produced no external side effects.
Disconnect context that determines safe handling
- Transaction phase at the last successful message.
- Local participant state: active, prepared, committed, or aborted.
- Which process, host, or network path failed.
- Recovery information available after reconnection.
References
- Microsoft MS-DTCO: participant behavior after losing contact
- Microsoft MS-DTCO: reconnecting for recovery
- IETF: TIP connection and transaction recovery behavior
Looking for a different code? Search another status or error code.