| Previous | Next |
| MQ_ERROR_CANNOT_LOAD_MQDSSRV | MQ_ERROR_MESSAGE_NOT_FOUND |
MQ_ERROR_PROPERTIES_CONFLICT
What this result actually narrows down
Applications should keep MQ_ERROR_PROPERTIES_CONFLICT attached to the exact MSMQ call that produced it. The result marks mutually exclusive MSMQ properties supplied together. Response queue object and response format name are one documented conflict; only one representation should own the value.
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.
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.
MSMQ objects involved
| Subsystem | MSMQ property arrays and their parallel identifier, value, and status elements |
|---|---|
| Relevant condition | the property identifier, VARTYPE, value, operation, and buffer ownership are validated separately |
| Code-specific focus | mutually exclusive MSMQ properties supplied together |
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 mutually exclusive MSMQ properties supplied together.
Triage data
- The complete apropid/apropvar/astatus triples in original order.
- The api name and whether the structure was input, output, or both.
- The first failing property rather than only the aggregate hresult.
Correct response
Define precedence in application code and emit a single canonical property.
What this code is not
Changing a queue ACL or restarting the service does not correct an invalid identifier, VARTYPE, value, structure, or property combination. Code-specific condition: mutually exclusive MSMQ properties supplied together.
Example failure path
Build one canonical property representation
It is caused by two individually recognizable properties that express the same or mutually exclusive choice. The documented response-queue example can occur when one layer supplies an object handle while another adds the corresponding format-name property. Log the final native property array after all wrappers, defaults, and middleware have modified it.
- Assign one owner for response destination, connector metadata, privacy, and other dependent fields.
- Validate conflicts after merging configuration sources, not only when each source is parsed independently.
- Remove the losing representation instead of relying on property order, because it is not a duplicate-property warning.
Technical references
Looking for a different code? Search another status or error code.