| Previous | Next |
| MQ_ERROR_PROPERTY_NOTALLOWED | MQ_ERROR_MACHINE_EXISTS |
MQ_ERROR_INSUFFICIENT_PROPERTIES
Interpretation
Applications should keep MQ_ERROR_INSUFFICIENT_PROPERTIES attached to the exact MSMQ call that produced it; translating it immediately to “queue error” discards the diagnostic boundary. In this case the decisive subject is required property set is incomplete. Another supplied property or operation mode makes an additional field mandatory.
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, the property namespace is split among message, queue, computer, private-computer, and management properties., A numeric identifier meaningful in one structure is not automatically legal in another API.
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 | required property set is incomplete |
| Primary recovery rule | Identify the dependency and submit the complete set atomically. |
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 required property set is incomplete.
Decisive observations
- 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.
Troubleshooting workflow
- 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: Identify the dependency and submit the complete set atomically.
Recovery rules
Identify the dependency and submit the complete set atomically.
When diagnosing it, retry only after a measurable state change: corrected property data, resized storage, restored service/directory reachability, recreated handle, completed transaction recovery, or repaired certificate access., bound attempts and keep an idempotency key for sends or directory mutations.
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 required property set is incomplete.
- 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.
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.
Sources
- 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.
- Microsoft: MSMQ message properties — source used for the result analysis.
Looking for a different code? Search another status or error code.