| Previous | Next |
| MQ_ERROR_ILLEGAL_PROPERTY_SIZE | MQ_ERROR_ILLEGAL_MQQUEUEPROPS |
MQ_ERROR_ILLEGAL_RESTRICTION_PROPID
Why the exact HRESULT matters
The important part of MQ_ERROR_ILLEGAL_RESTRICTION_PROPID is not only whether the call failed, but which MSMQ subsystem had enough information to return this specific result. Its diagnostic boundary is property cannot be used in the locate restriction. A queue property may exist but still be ineligible as an AD DS query predicate.
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.
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 | property cannot be used in the locate restriction |
| Primary recovery rule | Choose a documented searchable property or filter the returned rows 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 property cannot be used in the locate restriction.
Minimum useful telemetry
- The exact property used for filtering, projection, or ordering; associate it explicitly with this result.
- When diagnosing it, mqrestriction, mqcolumns, and mqsortset as submitted; capture the value before cleanup or retry changes it.
- In the path, the ad ds mode and domain identity of the caller; 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.
- When diagnosing it, capture the exact property used for filtering, projection, or ordering.
- 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 AD DS mode and domain identity of the caller.
- When diagnosing it, apply the code-specific recovery rule: Choose a documented searchable property or filter the returned rows in the application.
Retry and cleanup
Choose a documented searchable property or filter the returned rows in the application.
When diagnosing it, do not hide this HRESULT behind an unlimited framework retry., require a verified precondition change and preserve the original correlation identifier across the next attempt.
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 property cannot be used in the locate restriction.
- 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
An administration console 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 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.
- Microsoft: MQLocateBegin — source used for the result analysis.
Looking for a different code? Search another status or error code.