| Previous | Next |
| MQ_ERROR_DS_LOCAL_USER | MQ_ERROR_BAD_XML_FORMAT |
MQ_ERROR_Q_ADS_PROPERTY_NOT_SUPPORTED
Why the exact HRESULT matters
The important part of MQ_ERROR_Q_ADS_PROPERTY_NOT_SUPPORTED is not only whether the call failed, but which MSMQ subsystem had enough information to return this specific result. Its diagnostic boundary is MQLocateBegin cannot return the ADS path column. PROPID_Q_ADS_PATH is not available as a projected locate-query property.
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, the locator observes a directory snapshot beginning when MQLocateBegin is called., newly replicated objects and properties unsupported as columns or sort keys can produce results that differ from direct queue access.
Subsystem context
| 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 | MQLocateBegin cannot return the ADS path column |
| Primary recovery rule | Use supported queue identifiers and perform a separate directory lookup if the ADS path is needed. |
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 MQLocateBegin cannot return the ADS path column.
Minimum useful telemetry
- 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.
Step-by-step diagnosis
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- Capture MQRESTRICTION, MQCOLUMNS, and MQSORTSET as submitted.
- In the path, capture the AD DS mode and domain identity of the caller.
- verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
- When diagnosing it, apply the code-specific recovery rule: Use supported queue identifiers and perform a separate directory lookup if the ADS path is needed.
Retry and cleanup
Use supported queue identifiers and perform a separate directory lookup if the ADS path is needed.
When diagnosing it, the retry decision must account for side effects that may already exist., query queue, message, directory, or transaction state first whenever the result leaves completion uncertain.
Avoiding a false diagnosis
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 MQLocateBegin cannot return the ADS path column.
- In the 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.
- 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
A discovery service querying public queues encounters it. It captures the restriction/column/sort structures and validates the query before testing directory availability.
Include a negative test for the nearest misleading diagnosis so monitoring and user guidance do not collapse distinct MSMQ failures into one alert.
References
- 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.
- Microsoft: Message Queuing error and information codes — source used for the result analysis.
Looking for a different code? Search another status or error code.