| Previous | Next |
| MQ_ERROR_CANNOT_CREATE_ON_GC | MQ_ERROR_PUBLIC_KEY_NOT_FOUND |
MQ_ERROR_GUID_NOT_MATCHING
What this result actually narrows down
MQ_ERROR_GUID_NOT_MATCHING belongs to the Message Queuing HRESULT facility, but its useful meaning is narrower than a generic messaging failure. The result marks obsolete GUID consistency code. The value is retained for compatibility and should not drive modern object repair without historical evidence.
MSMQ uses directory services for public queues, machine configuration, security metadata, routing, aliases, and related enterprise objects. When diagnosing this result, private/direct queue operation can therefore succeed while a directory-dependent action fails.
Global catalog searches and writes to a writable domain naming context have different capabilities. Record whether the operation was discovery, read, create, update, or delete before choosing a domain controller.
MSMQ objects involved
| Subsystem | MSMQ integration with Active Directory Domain Services and the global catalog |
|---|---|
| Relevant condition | public queue metadata and MSMQ configuration objects depend on directory reachability, schema, class, ownership, and domain credentials |
| Code-specific focus | obsolete GUID consistency code |
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 obsolete GUID consistency code.
Triage data
- Domain/workgroup mode, forest and domain names, and selected domain controller.
- Dns and ldap reachability plus the distinguished name being accessed.
- The directory object class, guid, owner, and replication state.
Correct response
Identify the old component/version that emitted it.
What this code is not
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: obsolete GUID consistency code.
Example failure path
A domain-mode queue installer encounters it. It compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ.
Technical references
Looking for a different code? Search another status or error code.