What does HRESULT 0xC00E004C (MQ_ERROR_DTC_CONNECT) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

A connection cannot be established with the Distributed Transaction Coordinator.

Previous	Next
MQ_ERROR_QUEUE_NOT_AVAILABLE	MQ_ERROR_TRANSACTION_IMPORT

MQ_ERROR_DTC_CONNECT

Why the exact HRESULT matters

Applications should keep MQ_ERROR_DTC_CONNECT attached to the exact MSMQ call that produced it; translating it immediately to “queue error” discards the diagnostic boundary. Its diagnostic boundary is MSMQ cannot establish an MS DTC relationship. The failure occurs before a coordinated transaction can be used by the queue operation.

For MQ_ERROR_DTC_CONNECT, MSMQ supports internal single-queue transactions and coordinated transactions involving MS DTC. When diagnosing MQ_ERROR_DTC_CONNECT, queue type, destination locality, receive locality, and ambient transaction propagation constrain which operations are valid.

Transaction identifiers and completion ownership are essential. In the MQ_ERROR_DTC_CONNECT path, two threads attempting to commit, abort, or consume the same locked message can turn a recoverable application bug into duplicate processing.

Subsystem context

Subsystem	MSMQ internal or coordinated transactions and their MS DTC enlistment
Decisive boundary	transaction type, queue locality, operation order, and enlistment state determine whether the action is legal
Code-specific focus	MSMQ cannot establish an MS DTC relationship
Primary recovery rule	Check DTC service, security, name resolution, RPC/firewall, and mutual authentication before changing queue type.

When diagnosing MQ_ERROR_DTC_CONNECT, A transport retry is not equivalent to transaction recovery. In the MQ_ERROR_DTC_CONNECT path, first determine whether the unit of work committed, aborted, remains in doubt, or never enlisted. For MQ_ERROR_DTC_CONNECT, the code-specific boundary is MSMQ cannot establish an MS DTC relationship.

Minimum useful telemetry

Queue transactional flag and local/remote placement; associate it explicitly with MQ_ERROR_DTC_CONNECT.
When diagnosing MQ_ERROR_DTC_CONNECT, begin, enlist, send/receive, prepare, commit, and abort timestamps; capture the value before cleanup or retry changes it.
In the MQ_ERROR_DTC_CONNECT path, transaction identifier and whether it is internal, ambient, or dtc-coordinated; compare it with a known-good call using the same account and queue type.
For this MQ_ERROR_DTC_CONNECT result, record the queue path or format name, local/remote placement, transactional flag, caller SID, process build, and UTC correlation ID when they apply.

For MQ_ERROR_DTC_CONNECT, log certificate thumbprints, provider names, SIDs, GUIDs, lengths, and hashes where useful, but do not log private keys, symmetric keys, credentials, or confidential message bodies.

Step-by-step diagnosis

Record the unsigned HRESULT, MQ_ERROR_DTC_CONNECT, and the native API or COM method before a framework replaces it with a generic exception.
When diagnosing MQ_ERROR_DTC_CONNECT, capture transaction identifier and whether it is internal, ambient, or DTC-coordinated.
In the MQ_ERROR_DTC_CONNECT path, capture queue transactional flag and local/remote placement.
Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_DTC_CONNECT; change one precondition at a time.
For MQ_ERROR_DTC_CONNECT, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
When diagnosing MQ_ERROR_DTC_CONNECT, apply the code-specific recovery rule: Check DTC service, security, name resolution, RPC/firewall, and mutual authentication before changing queue type.

Retry and cleanup

Check DTC service, security, name resolution, RPC/firewall, and mutual authentication before changing queue type.

When diagnosing MQ_ERROR_DTC_CONNECT, the retry decision must account for side effects that may already exist. In the MQ_ERROR_DTC_CONNECT path, query queue, message, directory, or transaction state first whenever the result leaves completion uncertain.

Avoiding a false diagnosis

In the MQ_ERROR_DTC_CONNECT path, do not convert the operation to a nontransactional send merely to suppress the HRESULT; that changes delivery and atomicity guarantees. The specific focus for MQ_ERROR_DTC_CONNECT remains MSMQ cannot establish an MS DTC relationship.

In the MQ_ERROR_DTC_CONNECT path, A successful test under an interactive administrator account does not prove that the production service account has the same profile, token, directory access, or key permissions.
For this MQ_ERROR_DTC_CONNECT result, restarting MSMQ before collecting evidence can invalidate handles and erase the first useful event; it is a containment action, not a root-cause diagnosis.

Example

A dtc-coordinated workflow encounters MQ_ERROR_DTC_CONNECT. For MQ_ERROR_DTC_CONNECT, it correlates the MSMQ call with the DTC transaction ID and final outcome before replaying business work. When diagnosing MQ_ERROR_DTC_CONNECT, the acceptance test then changes only the decisive precondition and confirms both the HRESULT and the actual queue/message state.

A regression test should force MQ_ERROR_DTC_CONNECT, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.

References

Microsoft: MSMQTransaction.Commit and transaction model links — source used for the MQ_ERROR_DTC_CONNECT analysis.
Microsoft: DTC Developers Guide — source used for the MQ_ERROR_DTC_CONNECT analysis.
Microsoft: enable MS DTC diagnostic tracing — source used for the MQ_ERROR_DTC_CONNECT analysis.
Microsoft: destination queues — source used for the MQ_ERROR_DTC_CONNECT analysis.
Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_DTC_CONNECT analysis.

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