| Previous | Next |
| MQ_ERROR_ILLEGAL_RELATION | MQ_ERROR_ILLEGAL_RESTRICTION_PROPID |
MQ_ERROR_ILLEGAL_PROPERTY_SIZE
Why the exact HRESULT matters
The important part of MQ_ERROR_ILLEGAL_PROPERTY_SIZE is not only whether the call failed, but which MSMQ subsystem had enough information to return this specific result. In this case the decisive subject is fixed-width message identifier supplied with wrong size. Message IDs and correlation IDs have protocol-defined lengths and are not arbitrary byte strings.
Validation occurs in layers: identifier recognition, variant type, buffer shape, value range, required companions, and operation eligibility. When diagnosing this result, these layers correspond to different MSMQ HRESULTs and different fixes.
When diagnosing this result, MSMQ uses arrays whose indexes bind a property identifier, an MQPROPVARIANT value, and optionally a status result., misaligned counts or reordered arrays can make the logged property differ from the one actually rejected.
Subsystem context
| Subsystem | MSMQ property arrays and their parallel identifier, value, and status elements |
|---|---|
| Decisive boundary | the property identifier, VARTYPE, value, operation, and buffer ownership are validated separately |
| Code-specific focus | fixed-width message identifier supplied with wrong size |
| Primary recovery rule | Allocate exactly the documented size and preserve binary data without text conversion. |
When diagnosing this result, do not merge it with other property failures: identifier, VARTYPE, value, size, required companions, and operation eligibility are diagnosed by different codes. The code-specific boundary is fixed-width message identifier supplied with wrong size.
Minimum useful telemetry
- The first failing property rather than only the aggregate hresult; associate it explicitly with this result.
- When diagnosing it, the complete apropid/apropvar/astatus triples in original order; capture the value before cleanup or retry changes it.
- In the path, the api name and whether the structure was input, output, or both; 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 first failing property rather than only the aggregate HRESULT.
- In the path, capture the complete aPropID/aPropVar/aStatus triples in original order.
- 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: Allocate exactly the documented size and preserve binary data without text conversion.
Retry and cleanup
Allocate exactly the documented size and preserve binary data without text conversion.
When diagnosing it, an immediate loop around the same call is not recovery., define who owns cancellation, handle recreation, transaction reconciliation, and duplicate suppression before another attempt is issued.
Avoiding a false diagnosis
In the path, changing a queue ACL or restarting the service does not correct an invalid identifier, VARTYPE, value, structure, or property combination. The specific focus for it remains fixed-width message identifier supplied with wrong size.
- 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 wrapper building mqpropvariant arrays encounters it. It logs the rejected property index and rebuilds the request from a typed schema instead of retrying the same arrays.
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: queue properties and MQQUEUEPROPS — source used for the result analysis.
- Microsoft: MSMQ message properties — source used for the result analysis.
- Microsoft: MQCreateQueue — source used for the result analysis.
Looking for a different code? Search another status or error code.