| Previous | Next |
| MQ_ERROR_NOT_A_CORRECT_OBJECT_CLASS | MQ_ERROR_GC_NEEDED |
MQ_ERROR_MULTI_SORT_KEYS
Operational meaning
Applications should keep MQ_ERROR_MULTI_SORT_KEYS attached to the exact MSMQ call that produced it; translating it immediately to “queue error” discards the diagnostic boundary. In this case the decisive subject is AD DS locator accepts only one sort key. A structurally valid multi-column sort set exceeds the directory-backed implementation’s capability.
MQLocateBegin searches public queues registered in the directory; it does not enumerate arbitrary private queues. When diagnosing this result, its restriction, projection, and sort structures are translated into a directory-backed query.
When diagnosing this result, public-queue discovery depends on both valid MSMQ query structures and AD DS behavior., A malformed MQSORTSET should be separated from LDAP bind, schema, replication, or permissions failures.
Where to draw the boundary
| Subsystem | MQLocateBegin directory queries over public-queue metadata |
|---|---|
| Decisive boundary | query restrictions, selected columns, and sort keys must be valid for the AD DS-backed locator |
| Code-specific focus | AD DS locator accepts only one sort key |
| Primary recovery rule | Select one server-side key and perform secondary ordering in the application. |
When diagnosing this result, separate a malformed query structure from an AD DS availability error., repeating the same invalid MQSORTSET or MQRESTRICTION against another domain controller will not repair it. The code-specific boundary is AD DS locator accepts only one sort key.
Evidence to preserve
- Mqrestriction, mqcolumns, and mqsortset as submitted; associate it explicitly with this result.
- When diagnosing it, the ad ds mode and domain identity of the caller; capture the value before cleanup or retry changes it.
- In the path, the exact property used for filtering, projection, or ordering; 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.
Diagnostic sequence
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- In the path, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
- capture the exact property used for filtering, projection, or ordering.
- Capture MQRESTRICTION, MQCOLUMNS, and MQSORTSET as submitted.
- When diagnosing it, apply the code-specific recovery rule: Select one server-side key and perform secondary ordering in the application.
Handling and recovery
Select one server-side key and perform secondary ordering in the application.
When diagnosing it, 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., bound attempts and keep an idempotency key for sends or directory mutations.
Nearby failure boundaries
A directory query shape error is deterministic. switching domain controllers cannot make an unsupported column, relation, or sort key valid. The specific focus for it remains AD DS locator accepts only one sort key.
- In the path, restarting MSMQ before collecting evidence can invalidate handles and erase the first useful event; it is a containment action, not a root-cause diagnosis.
- 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.
Worked example
A discovery service querying public queues encounters it. It captures the restriction/column/sort structures and validates the query before testing directory availability.
Automated coverage should preserve the original arrays/identities, confirm that cleanup is safe after it, and test that a retry does not duplicate messages or directory objects.
References
- Microsoft: Message Queuing error and information codes — source used for the result analysis.
- Microsoft: MQLocateBegin — source used for the result analysis.
- Microsoft Open Specifications: MSMQ and directory services — source used for the result analysis.
- IETF RFC 4511: LDAP protocol — source used for the result analysis.
Looking for a different code? Search another status or error code.