What does HRESULT 0xC00E0066 (MQ_ERROR_WKS_CANT_SERVE_CLIENT) mean?

MQ_ERROR_WKS_CANT_SERVE_CLIENT

Interpretation

When MQ_ERROR_WKS_CANT_SERVE_CLIENT appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. The result marks independent client cannot act as a server for dependent clients. The topology requires an MSMQ server role; workstation-to-workstation chaining is not supported.

For MQ_ERROR_WKS_CANT_SERVE_CLIENT, establish the originating binary, operating-system build, MSMQ generation, and migration phase. When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, if those cannot be proved, treat the code as historical context rather than a current configuration prescription.

When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, several mq.h values remain documented for backward compatibility with MQIS, primary site controllers, dependent clients, and old optional-component installers. In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, modern AD DS-based MSMQ may never emit them directly.

Relevant API contract

When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, compatibility names can outlive the component that once emitted them. In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, remediation must match the historical architecture, not only the symbolic text. For MQ_ERROR_WKS_CANT_SERVE_CLIENT, the code-specific boundary is independent client cannot act as a server for dependent clients.

Decisive observations

• Installation or migration component name and original event text; associate it explicitly with MQ_ERROR_WKS_CANT_SERVE_CLIENT.
• When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, whether a current api returned the value or an old log merely contains it; capture the value before cleanup or retry changes it.
• In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, windows and msmq version where the code was captured; compare it with a known-good call using the same account and queue type.
• For this MQ_ERROR_WKS_CANT_SERVE_CLIENT 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_WKS_CANT_SERVE_CLIENT, 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

1. Record the unsigned HRESULT, MQ_ERROR_WKS_CANT_SERVE_CLIENT, and the native API or COM method before a framework replaces it with a generic exception.
2. When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, capture whether a current API returned the value or an old log merely contains it.
3. In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, capture Windows and MSMQ version where the code was captured.
4. Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_WKS_CANT_SERVE_CLIENT; change one precondition at a time.
5. For MQ_ERROR_WKS_CANT_SERVE_CLIENT, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
6. When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, apply the code-specific recovery rule: Move dependent clients to a supported server or change the deployment model.

Recovery rules

Move dependent clients to a supported server or change the deployment model.

When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, 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. In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, bound attempts and keep an idempotency key for sends or directory mutations.

Differences that matter

In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, do not copy retired DLLs or recreate obsolete registry topology until the originating MSMQ generation and component are proved. The specific focus for MQ_ERROR_WKS_CANT_SERVE_CLIENT remains independent client cannot act as a server for dependent clients.

• In the MQ_ERROR_WKS_CANT_SERVE_CLIENT path, changing queue names, deleting directory objects, or recreating certificates without reconciliation can create a second object while callers still reference the first.
• For this MQ_ERROR_WKS_CANT_SERVE_CLIENT result, 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

An archived installer log encounters MQ_ERROR_WKS_CANT_SERVE_CLIENT. For MQ_ERROR_WKS_CANT_SERVE_CLIENT, it identifies the originating MSMQ generation and uses migration documentation instead of modifying a current installation blindly. When diagnosing MQ_ERROR_WKS_CANT_SERVE_CLIENT, the acceptance test then changes only the decisive precondition and confirms both the HRESULT and the actual queue/message state.

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

Sources

• Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_WKS_CANT_SERVE_CLIENT analysis.
• Microsoft: Message Queuing overview — source used for the MQ_ERROR_WKS_CANT_SERVE_CLIENT analysis.
• Microsoft Open Specifications: MSMQ protocols overview — source used for the MQ_ERROR_WKS_CANT_SERVE_CLIENT analysis.

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