| Previous | Next |
| XACT_E_NETWORK_TX_DISABLED | XACT_E_XA_TX_DISABLED |
XACT_E_PARTNER_NETWORK_TX_DISABLED
Distributed DTC configuration must agree on both sides of the boundary
XACT_E_PARTNER_NETWORK_TX_DISABLED means the local transaction manager attempted remote propagation, but the partner reports that network transaction support is disabled. Local settings alone cannot override the remote transaction manager’s policy.
Identify the partner from the propagation trace and verify its DTC service, incoming access, authentication mode, and firewall configuration. Pay attention to asymmetric environments where one direction works but the reverse callback is blocked. Do not simply retry against different application endpoints: the failure belongs to the transaction-manager relationship. After configuration changes, test a minimal distributed transaction before returning the full workload to service.
Partner-side checks that distinguish this error
- Remote transaction-manager host selected during propagation.
- Partner incoming network DTC access setting.
- Authentication compatibility between both DTC instances.
- Bidirectional RPC and name-resolution test results.
References
- Microsoft MS-DTCO: transaction-manager propagation handshake
- Microsoft: multi-server DTC troubleshooting
- IETF: transaction-manager interoperability over a network
Looking for a different code? Search another status or error code.