HRESULT 0xC00E0075 (MQ_ERROR_NO_MSMQ_SERVERS_ON

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Message Queuing servers cannot be found on domain controllers.

Previous	Next
MQ_ERROR_NO_ENTRY_POINT_MSMQOCM	MQ_ERROR_CANNOT_JOIN_DOMAIN

MQ_ERROR_NO_MSMQ_SERVERS_ON_DC

Why the exact HRESULT matters

MQ_ERROR_NO_MSMQ_SERVERS_ON_DC belongs to the Message Queuing HRESULT facility, but its useful meaning is narrower than a generic messaging failure. Its diagnostic boundary is domain controllers do not expose expected MSMQ server data. Domain membership alone does not guarantee the required MSMQ directory objects/services are discoverable.

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

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, A domain join, a successful DNS lookup, and an LDAP bind are separate checkpoints. In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC path, directory errors must be correlated with the exact naming context, object class, GUID, and domain controller used by MSMQ.

Subsystem context

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	domain controllers do not expose expected MSMQ server data
Primary recovery rule	Check AD DS integration installation, replication, DNS, and the queried domain controllers.

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, 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_DC, the code-specific boundary is domain controllers do not expose expected MSMQ server data.

Minimum useful telemetry

Domain/workgroup mode, forest and domain names, and selected domain controller; associate it explicitly with MQ_ERROR_NO_MSMQ_SERVERS_ON_DC.
When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, dns and ldap reachability plus the distinguished name being accessed; capture the value before cleanup or retry changes it.
In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC path, the directory object class, guid, owner, and replication state; compare it with a known-good call using the same account and queue type.
For this MQ_ERROR_NO_MSMQ_SERVERS_ON_DC 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_DC, 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_NO_MSMQ_SERVERS_ON_DC, and the native API or COM method before a framework replaces it with a generic exception.
Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_NO_MSMQ_SERVERS_ON_DC; change one precondition at a time.
In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC path, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
For this MQ_ERROR_NO_MSMQ_SERVERS_ON_DC result, capture domain/workgroup mode, forest and domain names, and selected domain controller.
For MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, capture DNS and LDAP reachability plus the distinguished name being accessed.
When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, apply the code-specific recovery rule: Check AD DS integration installation, replication, DNS, and the queried domain controllers.

Retry and cleanup

Check AD DS integration installation, replication, DNS, and the queried domain controllers.

When diagnosing MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, retry only after a measurable state change: corrected property data, resized storage, restored service/directory reachability, recreated handle, completed transaction recovery, or repaired certificate access. In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC path, bound attempts and keep an idempotency key for sends or directory mutations.

Avoiding a false diagnosis

In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC 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_DC remains domain controllers do not expose expected MSMQ server data.

In the MQ_ERROR_NO_MSMQ_SERVERS_ON_DC 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_NO_MSMQ_SERVERS_ON_DC 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

An enterprise migration tool encounters MQ_ERROR_NO_MSMQ_SERVERS_ON_DC. For MQ_ERROR_NO_MSMQ_SERVERS_ON_DC, 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_DC, 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_DC, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.

Domain-controller discovery versus object absence

MQ_ERROR_NO_MSMQ_SERVERS_ON_DC indicates that the domain-controller path did not yield the Message Queuing server information expected by the caller. Check whether AD DS integration for MSMQ was installed, whether MSMQ configuration objects were created, and whether those objects replicated to the particular domain controllers being queried. This is broader than the absence of the migration-only MSMQ Users OU.

Compare results from writable domain controllers in each site and record the DC locator decision.
Verify DNS SRV records, LDAP bind identity, and schema/object visibility before reinstalling the Message Queuing service.
Distinguish a reachable DC with no MSMQ objects from a failed bind or global catalog lookup, because each has a different repair owner.

References

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

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