HRESULT 0xC00E0041 (MQ_ERROR_ILLEGAL

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Either the pointer to the MQQMROPS structure has a null value, or no properties are specified in it.

Previous	Next
MQ_ERROR_MACHINE_EXISTS	MQ_ERROR_DS_IS_FULL

MQ_ERROR_ILLEGAL_MQQMPROPS

What this result actually narrows down

Applications should keep MQ_ERROR_ILLEGAL_MQQMPROPS 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 invalid machine-property request structure. MQQMPROPS must contain a nonzero coherent property set for machine information APIs.

For MQ_ERROR_ILLEGAL_MQQMPROPS, validation occurs in layers: identifier recognition, variant type, buffer shape, value range, required companions, and operation eligibility. When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, these layers correspond to different MSMQ HRESULTs and different fixes.

When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, MSMQ uses arrays whose indexes bind a property identifier, an MQPROPVARIANT value, and optionally a status result. In the MQ_ERROR_ILLEGAL_MQQMPROPS path, misaligned counts or reordered arrays can make the logged property differ from the one actually rejected.

MSMQ objects involved

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	invalid machine-property request structure
Primary recovery rule	Initialize the machine property arrays and inspect aStatus for per-property results.

When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, do not merge this result with other property failures: identifier, VARTYPE, value, size, required companions, and operation eligibility are diagnosed by different codes. For MQ_ERROR_ILLEGAL_MQQMPROPS, the code-specific boundary is invalid machine-property request structure.

Triage data

The complete apropid/apropvar/astatus triples in original order; associate it explicitly with MQ_ERROR_ILLEGAL_MQQMPROPS.
When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, the api name and whether the structure was input, output, or both; capture the value before cleanup or retry changes it.
In the MQ_ERROR_ILLEGAL_MQQMPROPS 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.
For this MQ_ERROR_ILLEGAL_MQQMPROPS result, record the queue path or format name, local/remote placement, transactional flag, caller SID, process build, and UTC correlation ID when they apply.

For MQ_ERROR_ILLEGAL_MQQMPROPS, 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.

A safe investigation order

Record the unsigned HRESULT, MQ_ERROR_ILLEGAL_MQQMPROPS, and the native API or COM method before a framework replaces it with a generic exception.
When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, 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 MQ_ERROR_ILLEGAL_MQQMPROPS path, capture the API name and whether the structure was input, output, or both.
For this MQ_ERROR_ILLEGAL_MQQMPROPS result, capture the first failing property rather than only the aggregate HRESULT.
Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_ILLEGAL_MQQMPROPS; change one precondition at a time.
When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, apply the code-specific recovery rule: Initialize the machine property arrays and inspect aStatus for per-property results.

Correct response

Initialize the machine property arrays and inspect aStatus for per-property results.

When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, do not hide this HRESULT behind an unlimited framework retry. In the MQ_ERROR_ILLEGAL_MQQMPROPS path, require a verified precondition change and preserve the original correlation identifier across the next attempt.

What this code is not

In the MQ_ERROR_ILLEGAL_MQQMPROPS 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 MQ_ERROR_ILLEGAL_MQQMPROPS remains invalid machine-property request structure.

In the MQ_ERROR_ILLEGAL_MQQMPROPS path, granting broad queue or certificate permissions may mask the symptom while creating a security defect. For this MQ_ERROR_ILLEGAL_MQQMPROPS result, test the exact identity and access needed by the operation.
For this MQ_ERROR_ILLEGAL_MQQMPROPS result, changing queue names, deleting directory objects, or recreating certificates without reconciliation can create a second object while callers still reference the first.

Example failure path

A wrapper building mqpropvariant arrays encounters MQ_ERROR_ILLEGAL_MQQMPROPS. For MQ_ERROR_ILLEGAL_MQQMPROPS, it logs the rejected property index and rebuilds the request from a typed schema instead of retrying the same arrays. When diagnosing MQ_ERROR_ILLEGAL_MQQMPROPS, the acceptance test then changes only the decisive precondition and confirms both the HRESULT and the actual queue/message state.

For MQ_ERROR_ILLEGAL_MQQMPROPS, include a negative test for the nearest misleading diagnosis so monitoring and user guidance do not collapse distinct MSMQ failures into one alert.

Technical references

Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_ILLEGAL_MQQMPROPS analysis.
Microsoft: queue properties and MQQUEUEPROPS — source used for the MQ_ERROR_ILLEGAL_MQQMPROPS analysis.
Microsoft: MSMQ message properties — source used for the MQ_ERROR_ILLEGAL_MQQMPROPS analysis.
Microsoft: MQCreateQueue — source used for the MQ_ERROR_ILLEGAL_MQQMPROPS analysis.

Looking for a different code? Search another status or error code.