What does HRESULT 0xC00E007D (MQ_ERROR_NO_MSMQ_SERVERS_ON_GC) mean?

MQ_ERROR_NO_MSMQ_SERVERS_ON_GC

What this result actually narrows down

The important part of MQ_ERROR_NO_MSMQ_SERVERS_ON_GC is not only whether the call failed, but which MSMQ subsystem had enough information to return this specific result. Its diagnostic boundary is global catalog search returns no MSMQ servers. A GC is reachable, but the expected MSMQ directory objects are absent or not replicated.

For MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, global catalog searches and writes to a writable domain naming context have different capabilities. When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, record whether the operation was discovery, read, create, update, or delete before choosing a domain controller.

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, MSMQ uses directory services for public queues, machine configuration, security metadata, routing, aliases, and related enterprise objects. In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, private/direct queue operation can therefore succeed while a directory-dependent action fails.

MSMQ objects involved

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, A queue can exist locally while its public registration or MSMQ configuration object is absent, stale, wrong-class, or visible only on some domain controllers. For MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, the code-specific boundary is global catalog search returns no MSMQ servers.

Triage data

• The directory object class, guid, owner, and replication state; associate it explicitly with MQ_ERROR_NO_MSMQ_SERVERS_ON_GC.
• When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, domain/workgroup mode, forest and domain names, and selected domain controller; capture the value before cleanup or retry changes it.
• In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, dns and ldap reachability plus the distinguished name being accessed; compare it with a known-good call using the same account and queue type.
• For this MQ_ERROR_NO_MSMQ_SERVERS_ON_GC 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_NO_MSMQ_SERVERS_ON_GC, 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.

A safe investigation order

1. Record the unsigned HRESULT, MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, and the native API or COM method before a framework replaces it with a generic exception.
2. When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
3. In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, capture DNS and LDAP reachability plus the distinguished name being accessed.
4. For this MQ_ERROR_NO_MSMQ_SERVERS_ON_GC result, capture the directory object class, GUID, owner, and replication state.
5. Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_NO_MSMQ_SERVERS_ON_GC; change one precondition at a time.
6. When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, apply the code-specific recovery rule: Inspect object creation and GC partial-attribute/replication state.

Correct response

Inspect object creation and GC partial-attribute/replication state.

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, an immediate loop around the same call is not recovery. In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, define who owns cancellation, handle recreation, transaction reconciliation, and duplicate suppression before another attempt is issued.

What this code is not

In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, local private-queue success does not prove that public-queue registration, global catalog discovery, or the required AD DS object is healthy. The specific focus for MQ_ERROR_NO_MSMQ_SERVERS_ON_GC remains global catalog search returns no MSMQ servers.

• In the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC path, granting broad queue or certificate permissions may mask the symptom while creating a security defect. For this MQ_ERROR_NO_MSMQ_SERVERS_ON_GC result, test the exact identity and access needed by the operation.
• For this MQ_ERROR_NO_MSMQ_SERVERS_ON_GC result, changing queue names, deleting directory objects, or recreating certificates without reconciliation can create a second object while callers still reference the first.

Example failure path

An enterprise migration tool encounters MQ_ERROR_NO_MSMQ_SERVERS_ON_GC. For MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, it compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ. When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_GC, 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_NO_MSMQ_SERVERS_ON_GC, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.

Technical references

• Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC analysis.
• Microsoft Open Specifications: MSMQ and directory services — source used for the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC analysis.
• Microsoft Open Specifications: MSMQ protocols overview — source used for the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC analysis.
• IETF RFC 4511: LDAP protocol — source used for the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC analysis.
• Microsoft: destination queues — source used for the MQ_ERROR_NO_MSMQ_SERVERS_ON_GC analysis.

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