| Previous | Next |
| XACT_E_CONNECTION_DOWN | XACT_E_REENLISTTIMEOUT |
XACT_E_CONNECTION_DENIED
A reachable host can still reject distributed transaction participation
XACT_E_CONNECTION_DENIED means a connection request reached the transaction infrastructure but was not accepted. This is distinct from a transport timeout: authentication policy, network DTC access, partner trust, endpoint mapping, or a disabled protocol can reject the session before transaction propagation succeeds.
Compare DTC security configuration on both machines and test name resolution and authentication in both directions. Record the identities presented by the services and whether the failure occurs for all partners or one host. Avoid weakening authentication globally as a first response; align the intended mutual-authentication or incoming/outgoing access settings and verify firewall rules for the DTC/RPC path.
Configuration evidence for a denied DTC session
- Source and destination computer names as resolved by each side.
- Incoming, outgoing, and network DTC access settings.
- Authentication mode and service identities.
- Firewall or RPC endpoint-mapper result before denial.
References
- Microsoft MS-DTCO: propagation between transaction managers
- Microsoft: distributed COM+ transaction troubleshooting
- IETF: security and connectivity requirements for transaction managers
Looking for a different code? Search another status or error code.