| Previous | Next |
| MQ_ERROR_NO_ENTRY_POINT_MSMQOCM | MQ_ERROR_CANNOT_JOIN_DOMAIN |
MQ_ERROR_NO_MSMQ_SERVERS_ON_DC
Retry and cleanup
Check AD DS integration installation, replication, DNS, and the queried domain controllers.
Avoiding a false diagnosis
Local private-queue success does not prove that public-queue registration, global catalog discovery, or the required AD DS object is healthy. Code-specific condition: domain controllers do not expose expected MSMQ server data.
Example
An enterprise migration tool encounters it. It compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ.
Domain-controller discovery versus object absence
It 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
Looking for a different code? Search another status or error code.