| Previous | Next |
| MQ_ERROR_INVALID_OWNER | MQ_ERROR_RESULT_BUFFER_TOO_SMALL |
MQ_ERROR_UNSUPPORTED_ACCESS_MODE
What this result actually narrows down
Applications should keep MQ_ERROR_UNSUPPORTED_ACCESS_MODE attached to the exact MSMQ call that produced it. Interpret it as requested open/access mode has no MSMQ implementation, not as a general transport outage. This differs from access denied: authorization was not evaluated because the mode itself is unsupported.
A service restart can make the symptom disappear while removing the state needed to identify it. When diagnosing this result, preserve operation parameters, identity, queue format name, and logs before intervention.
MSMQ exposes more specific property, queue, directory, transaction, and security HRESULTs. A generic value often means that the useful subordinate error was discarded by a wrapper or appears earlier in the event timeline.
MSMQ objects involved
| Subsystem | the MSMQ API boundary that returned a nonspecific failure |
|---|---|
| Relevant condition | the generic HRESULT is useful only when correlated with the operation, property statuses, service logs, and preceding failure |
| Code-specific focus | requested open/access mode has no MSMQ implementation |
Because the code is nonspecific, it should never be the only telemetry field. The operation and subordinate status determine whether retry is safe. The code-specific boundary is requested open/access mode has no MSMQ implementation.
Triage data
- Msmq service, application, and transaction logs around the first occurrence.
- Api or com method, raw parameters, and calling identity.
- Property-level status values and first windows error in the same timeline.
Correct response
Use a documented receive, peek, send, or administration access combination.
What this code is not
The generic value is not a diagnosis. Property statuses and the earliest native/service error must remain attached to the operation. Code-specific condition: requested open/access mode has no MSMQ implementation.
Example failure path
An application framework encounters it. It captures the native property statuses and first service event so the generic wrapper error can be replaced by a specific diagnosis.
Technical references
Looking for a different code? Search another status or error code.