| Previous | Next |
| XACT_E_PARTNER_NETWORK_TX_DISABLED | XACT_E_UNABLE_TO_READ_DTC_CONFIG |
XACT_E_XA_TX_DISABLED
XACT_E_XA_TX_DISABLED is the failure HRESULT 0x8004D026 (signed decimal -2147168218, unsigned decimal 2147799078). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xD026.
The coordinator has disabled XA transaction support
This HRESULT means the transaction manager has disabled support for XA transactions. XA interoperability uses DTC helper and mapping interfaces to coordinate with resource managers whose native distributed-transaction protocol is XA.
AllStat records the Windows message as: “The transaction manager has disabled its support for XA transactions.” This text should be interpreted at the transaction stage described below rather than as a generic COM failure.
The contract boundary to identify
The result is returned at the protocol-capability boundary. It does not say the XA resource manager rejected an XID, nor that the XA library failed to load. The local DTC policy has prevented XA participation.
Likely causes to separate
- XA transactions are intentionally disabled because the deployment does not require them.
- An adapter or database provider unexpectedly promotes work into an XA transaction.
- A server migration restores ordinary DTC settings but omits the XA-specific configuration.
- The application assumes XA and OleTx network transaction switches are equivalent.
Evidence worth preserving
- Identify the XA resource manager, adapter, XID correlation, and point where XA mapping was requested.
- Record current DTC XA configuration and the change that introduced the first failure.
- Capture provider and XA switch-module versions without logging credentials.
- Verify whether a non-XA transaction path exists for the same resource.
Diagnostic sequence
- Confirm that XA is required by the participating resource manager and not selected through an unintended provider option.
- Review the DTC interfaces and approved XA configuration for the platform.
- Test XA mapping with a controlled resource and verify prepare, commit, abort, and recovery behavior.
- Keep XA enablement separate from generic firewall remediation because the HRESULT identifies local feature policy.
Retry and recovery
Enable XA support only when the resource manager, security policy, and recovery procedures are ready, or configure the application to use a supported non-XA path. The same request will continue to fail while the feature remains disabled.
What this HRESULT does not establish
The code does not identify an XA protocol vote, heuristic result, or resource-manager outage. It also does not prove network DTC access is disabled.
Difference from nearby transaction results
XACT_E_TIP_DISABLED concerns TIP interoperability. XACT_E_LU_TX_DISABLED concerns SNA LU 6.2 transactions; each switch represents a different protocol family.
Practical scenario
A database adapter is upgraded and begins requesting XA coordination. The server has never enabled XA in MSDTC, so promotion fails immediately. The owner confirms the requirement, deploys the supported XA components, and runs recovery tests before production use.
Guidance for software and telemetry
Log protocol family and resource-manager identity before reporting a generic “distributed transaction failed.” Feature enablement without a tested recovery path creates a larger risk than the original rejection.
Official Microsoft references
- Microsoft: COM transaction error codes
- Microsoft: DTC interfaces
- Microsoft: enable MSDTC diagnostic tracing
- Microsoft: MSDTC security and network access
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.