| Previous | Next |
| MQ_ERROR_NOT_SUPPORTED_BY_DEPENDENT_CLIENTS | MQ_ERROR_NOT_A_CORRECT_OBJECT_CLASS |
MQ_ERROR_OPERATION_NOT_SUPPORTED_BY_REMOTE_COMPUTER
What this result actually narrows down
The important part of MQ_ERROR_OPERATION_NOT_SUPPORTED_BY_REMOTE_COMPUTER 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 remote MSMQ version lacks lookup-ID operation. MQReceiveMessageByLookupId requires newer remote queue-manager support than MSMQ 1.0/2.0 provide.
Remote send and remote receive use different paths. When diagnosing this result, A sender can often place data in a local outgoing queue even while direct remote reading requires RPC and a responsive destination queue manager.
When diagnosing this result, the queue name, resolved address, MSMQ service, firewall path, protocol version, and requested operation are separate checkpoints., A ping or DNS success alone does not prove remote-read support.
MSMQ objects involved
| Subsystem | remote queue access, queue-manager availability, and version-dependent RPC operations |
|---|---|
| Decisive boundary | a local handle, an outgoing transfer path, and a remote-read RPC path fail for different reasons |
| Code-specific focus | remote MSMQ version lacks lookup-ID operation |
| Primary recovery rule | Use a compatible cursor/receive method or upgrade the remote service. |
When diagnosing this result, differentiate remote-read RPC from ordinary send-and-forward delivery., opening or peeking a remote queue can fail even when outgoing messages eventually reach it. The code-specific boundary is remote MSMQ version lacks lookup-ID operation.
Triage data
- Msmq service state and protocol reachability on both systems; associate it explicitly with it.
- When diagnosing it, remote msmq version and the exact operation requested; capture the value before cleanup or retry changes it.
- In the path, destination computer and resolved address or format name; 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.
A safe investigation order
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- When diagnosing it, 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 path, capture destination computer and resolved address or format name.
- capture MSMQ service state and protocol reachability on both systems.
- When diagnosing it, apply the code-specific recovery rule: Use a compatible cursor/receive method or upgrade the remote service.
Correct response
Use a compatible cursor/receive method or upgrade the remote service.
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.
What this code is not
In the path, DNS success and an open TCP path are not proof that the remote MSMQ version supports the requested read, cursor, or management operation. The specific focus for it remains remote MSMQ version lacks lookup-ID operation.
- In the path, granting broad queue or certificate permissions may mask the symptom while creating a security defect. test the exact identity and access needed by the operation.
- 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 cross-machine receiver encounters it. It separates DNS, service/RPC reachability, remote version, and the specific remote-read operation.
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.
Technical references
- Microsoft Open Specifications: Queue Manager Remote Read Protocol — source used for the result analysis.
- Microsoft Open Specifications: MSMQ protocols overview — source used for the result analysis.
- Microsoft: Windows service port requirements — source used for the result analysis.
- Microsoft: destination queues — source used for the result analysis.
- Microsoft: Message Queuing error and information codes — source used for the result analysis.
Looking for a different code? Search another status or error code.