What does HRESULT 0x8004D02C (XACT_E_LU_TX_DISABLED) mean?

 
Previous Next
XACT_E_PULL_COMM_FAILURE XACT_E_CLERKNOTFOUND

XACT_E_LU_TX_DISABLED

XACT_E_LU_TX_DISABLED is the failure HRESULT 0x8004D02C (signed decimal -2147168212, unsigned decimal 2147799084). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xD02C.

The coordinator has disabled SNA LU 6.2 transaction support

This HRESULT states that MSDTC support for SNA LU 6.2 transactions is disabled. LU 6.2 uses a dedicated set of DTC interfaces for configuration, enlistment, and recovery, so ordinary OleTx or XA enablement does not satisfy this request.

AllStat records the Windows message as: “The MSDTC transaction manager has disabled its support for SNA LU 6.2 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 a local feature-policy rejection. It does not indicate a failed LU session, a partner vote, or an SNA transport outage. The application or resource-manager proxy selected a transaction family that the coordinator is not configured to provide.

Likely causes to separate

  • The environment intentionally disables legacy LU 6.2 interoperability.
  • A host-integration adapter requests LU transactions on a server where the feature was never configured.
  • Configuration was lost during migration or DTC instance recreation.
  • Middleware selects LU coordination based on an obsolete connection profile.

Evidence worth preserving

  • Identify the host-integration component, LU pair, resource manager, and transaction UOW.
  • Capture the DTC LU configuration and the adapter setting that requested this protocol.
  • Record whether the workload previously used LU transactions on this exact server instance.
  • Preserve recovery configuration because enabling a protocol without recovery support is incomplete.

Diagnostic sequence

  • Confirm that SNA LU 6.2 coordination is a current requirement rather than a legacy default.
  • Review the documented IDtcLu* interfaces and platform components required by the adapter.
  • If approved, configure LU transaction support and test commit, abort, and recovery with the actual partner.
  • Otherwise migrate the integration to a supported transaction or compensating workflow.

Retry and recovery

Enable and validate LU support only in an environment designed to operate and recover it, or change the adapter protocol. The same LU request will remain rejected while support is disabled.

What this HRESULT does not establish

The HRESULT does not report LU partner availability or the state of a specific transaction. It also does not mean XA, TIP, or ordinary network DTC transactions are disabled.

Difference from nearby transaction results

XACT_E_XA_TX_DISABLED and XACT_E_TIP_DISABLED identify separate interoperability switches. Their remediation and recovery tooling are not interchangeable.

Practical scenario

A migrated host-integration service retains an LU 6.2 transaction profile, but the replacement Windows server has no LU DTC configuration. The team either provisions the supported host-integration stack and recovery tests or changes the connector to a modern supported boundary.

Guidance for software and telemetry

Inventory legacy protocol dependencies before server migration. Operational documentation must include partner identity, recovery ownership, and a tested way to resolve in-doubt LU transactions.

Official Microsoft references

Looking for a different code? Search another status or error code.