| Previous | Next |
| MQ_ERROR_PUBLIC_KEY_DOES_NOT_EXIST | MQ_ERROR_NO_GC_IN_DOMAIN |
MQ_ERROR_ILLEGAL_MQPRIVATEPROPS
Operational meaning
The important part of MQ_ERROR_ILLEGAL_MQPRIVATEPROPS 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 private-computer property structure is empty or null. MQGetPrivateComputerInformation requires a coherent MQPRIVATEPROPS request.
MSMQ uses arrays whose indexes bind a property identifier, an MQPROPVARIANT value, and optionally a status result. When diagnosing this result, misaligned counts or reordered arrays can make the logged property differ from the one actually rejected.
When diagnosing this result, validation occurs in layers: identifier recognition, variant type, buffer shape, value range, required companions, and operation eligibility., these layers correspond to different MSMQ HRESULTs and different fixes.
Where to draw the boundary
| 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 | private-computer property structure is empty or null |
| Primary recovery rule | Initialize cProp and parallel arrays for the exact private-computer properties needed. |
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 private-computer property structure is empty or null.
Evidence to preserve
- 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.
Diagnostic sequence
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- When diagnosing it, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
- In the path, capture the complete aPropID/aPropVar/aStatus triples in original order.
- capture the API name and whether the structure was input, output, or both.
- When diagnosing it, apply the code-specific recovery rule: Initialize cProp and parallel arrays for the exact private-computer properties needed.
Handling and recovery
Initialize cProp and parallel arrays for the exact private-computer properties needed.
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.
Nearby failure boundaries
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 private-computer property structure is empty or null.
- 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 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: MSMQ message properties — source used for the result analysis.
- Microsoft: MQCreateQueue — source used for the result analysis.
- Microsoft: Message Queuing error and information codes — source used for the result analysis.
- Microsoft: queue properties and MQQUEUEPROPS — source used for the result analysis.
Looking for a different code? Search another status or error code.