| Previous | Next |
| MQ_ERROR | MQ_ERROR_QUEUE_NOT_FOUND |
MQ_ERROR_PROPERTY
Interpretation
The important part of MQ_ERROR_PROPERTY 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 aggregate invalid-property failure. One or more per-property aStatus values contain the actionable result.
The property namespace is split among message, queue, computer, private-computer, and management properties. When diagnosing this result, A numeric identifier meaningful in one structure is not automatically legal in another API.
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.
Relevant API contract
| 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 | aggregate invalid-property failure |
| Primary recovery rule | Report the property identifier and status together instead of exposing only this result. |
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 aggregate invalid-property failure.
Decisive observations
- The complete apropid/apropvar/astatus triples in original order; associate it explicitly with it.
- When diagnosing it, the api name and whether the structure was input, output, or both; capture the value before cleanup or retry changes it.
- In the path, the first failing property rather than only the aggregate hresult; 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.
Troubleshooting workflow
- 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 API name and whether the structure was input, output, or both.
- capture the first failing property rather than only the aggregate HRESULT.
- Apply the code-specific recovery rule: Report the property identifier and status together instead of exposing only it.
Recovery rules
Report the property identifier and status together instead of exposing only it.
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.
Differences that matter
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 aggregate invalid-property failure.
- In the path, changing queue names, deleting directory objects, or recreating certificates without reconciliation can create a second object while callers still reference the first.
- 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.
Practical scenario
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.
A regression test should force it, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.
Sources
- 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.