| Previous | Next |
| XACT_E_TIP_DISABLED | XACT_E_PARTNER_NETWORK_TX_DISABLED |
XACT_E_NETWORK_TX_DISABLED
Local transactions can work even when cross-machine propagation is prohibited
XACT_E_NETWORK_TX_DISABLED indicates that the local MSDTC configuration does not permit remote transaction participation. An application may create and use a local transaction successfully, then fail only when a resource on another machine causes the transaction to be propagated or promoted.
Confirm that the architecture genuinely requires one atomic transaction across hosts. If it does, enable the necessary network DTC access under the organization’s authentication and firewall policy and test both directions. If distributed atomicity is not required, redesign the boundary with an outbox, durable message, or compensating workflow rather than enabling network transactions merely to hide an accidental second resource.
Boundary information needed before enabling network DTC
- Local operation that first introduces a remote participant.
- Hosts and resource managers expected in one atomic unit.
- Required authentication and firewall policy.
- Alternative asynchronous or compensating design if 2PC is unnecessary.
References
- Microsoft MS-DTCO: cross-manager transaction propagation
- Microsoft: checking DTC on distributed systems
- IETF: distributed transaction deployment considerations
Looking for a different code? Search another status or error code.