| Previous | Next |
| XACT_E_DEST_TMNOTAVAILABLE | XACT_E_NETWORK_TX_DISABLED |
XACT_E_TIP_DISABLED
XACT_E_TIP_DISABLED is the failure HRESULT 0x8004D023 (signed decimal -2147168221, unsigned decimal 2147799075). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xD023.
TIP interoperability is disabled by transaction-manager policy
This HRESULT means the transaction manager has disabled support for Transaction Internet Protocol. The failure is a capability or policy decision, not evidence that a particular remote TIP endpoint is unreachable.
AllStat records the Windows message as: “The Transaction Manager has disabled its support for TIP.” This text should be interpreted at the transaction stage described below rather than as a generic COM failure.
The contract boundary to identify
TIP is an optional interoperability path between OleTx and TIP-compliant transaction managers. A system can support ordinary local or OleTx network transactions while refusing TIP. Enabling unrelated DTC network settings may therefore leave this result unchanged.
Likely causes to separate
- TIP support is intentionally disabled by security or interoperability policy.
- The application selected a TIP transaction path even though both resources can use another supported protocol.
- A deployment assumes TIP is enabled because network DTC access is enabled.
- Configuration was changed or reset during upgrade, repair, or host replacement.
Evidence worth preserving
- Record which component requested TIP and why TIP rather than OleTx propagation was selected.
- Capture local transaction-manager configuration and policy-change history.
- Identify the remote manager and the exact interoperability requirement.
- Preserve the transaction URL or request metadata in sanitized form.
Diagnostic sequence
- Confirm that the application truly requires TIP and is not using it accidentally through a compatibility layer.
- Review approved MSDTC security settings before changing protocol support.
- If TIP is permitted, enable it consistently and test with a nonproduction transaction between the actual peer types.
- If TIP is prohibited, select an OleTx, XA, local, or compensating architecture supported by all participants.
Retry and recovery
Change policy only after security review or route the operation through a supported transaction mechanism. Retrying while TIP remains disabled is deterministic. Do not weaken authentication or firewall controls merely to make the HRESULT disappear.
What this HRESULT does not establish
The code does not report a failed TIP handshake or malformed protocol message. It also does not mean all remote transactions are disabled; XACT_E_NETWORK_TX_DISABLED covers the broader network-transaction setting.
Difference from nearby transaction results
XACT_E_TIP_CONNECT_FAILED means TIP was attempted but connection establishment failed. XACT_E_XA_TX_DISABLED is the corresponding policy result for XA interoperability.
Practical scenario
A newly deployed connector uses a TIP URL to bring an external transaction into COM+. The server’s approved policy disables TIP. The team either enables the reviewed interoperability feature or changes the connector to a supported DTC propagation model.
Guidance for software and telemetry
Expose protocol selection in configuration and audit logs. Operators need to know whether TIP was explicitly requested, inferred from a URL, or chosen by middleware.
Official Microsoft references
- Microsoft: COM transaction error codes
- Microsoft: OleTx TIP protocol
- Microsoft: relationship between OleTx and TIP
- Microsoft: MSDTC security and network access
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.