| Previous | Next |
| MQ_ERROR_NO_GC_IN_DOMAIN | MQ_ERROR_CANNOT_GET_DN |
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.
Global catalog searches and writes to a writable domain naming context have different capabilities. When diagnosing this result, record whether the operation was discovery, read, create, update, or delete before choosing a domain controller.
When diagnosing this result, MSMQ uses directory services for public queues, machine configuration, security metadata, routing, aliases, and related enterprise objects., private/direct queue operation can therefore succeed while a directory-dependent action fails.
MSMQ objects involved
| Subsystem | MSMQ integration with Active Directory Domain Services and the global catalog |
|---|---|
| Decisive boundary | public queue metadata and MSMQ configuration objects depend on directory reachability, schema, class, ownership, and domain credentials |
| Code-specific focus | global catalog search returns no MSMQ servers |
| Primary recovery rule | Inspect object creation and GC partial-attribute/replication state. |
When diagnosing this result, 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. 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 it.
- When diagnosing it, domain/workgroup mode, forest and domain names, and selected domain controller; capture the value before cleanup or retry changes it.
- In the 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.
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
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- When diagnosing it, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
- In the path, capture DNS and LDAP reachability plus the distinguished name being accessed.
- capture the directory object class, GUID, owner, and replication state.
- When diagnosing it, 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 it, an immediate loop around the same call is not recovery., define who owns cancellation, handle recreation, transaction reconciliation, and duplicate suppression before another attempt is issued.
What this code is not
In the 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 it remains global catalog search returns no MSMQ servers.
- In the path, granting broad queue or certificate permissions may mask the symptom while creating a security defect. test the exact identity and access needed by the operation.
- 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 it. It compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ.
A regression test should force it, 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 result analysis.
- Microsoft Open Specifications: MSMQ and directory services — source used for the result analysis.
- Microsoft Open Specifications: MSMQ protocols overview — source used for the result analysis.
- IETF RFC 4511: LDAP protocol — source used for the result analysis.
- Microsoft: destination queues — source used for the result analysis.
Looking for a different code? Search another status or error code.