| Previous | Next |
| MQ_ERROR_CANNOT_SET_CRYPTO_SEC_DESCR | MQ_ERROR_Q_DNS_PROPERTY_NOT_SUPPORTED |
MQ_ERROR_CERTIFICATE_NOT_PROVIDED
What this result actually narrows down
Applications should keep MQ_ERROR_CERTIFICATE_NOT_PROVIDED 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 authenticated send lacks certificate material. The queue/message policy requires authentication but the sending context supplied no usable certificate.
Authenticated MSMQ messages combine a sender identity, certificate, private key, hash/signature algorithm, and queue policy. When diagnosing this result, successful certificate parsing does not prove that the key is accessible to the sending process.
When diagnosing this result, MSMQ security material can live in the current user profile and be registered in directory services., services running under another account or without a loaded profile can observe a different certificate-store state.
MSMQ objects involved
| Subsystem | MSMQ message authentication, certificate registration, signing, hashing, and encryption |
|---|---|
| Decisive boundary | certificate identity, key availability, provider capability, and message policy are independent checks |
| Code-specific focus | authenticated send lacks certificate material |
| Primary recovery rule | Attach/register a certificate or use an MSMQ security context created for that sender. |
When diagnosing this result, queue ACLs, certificate trust, private-key access, provider support, and destination authentication policy are independent. Test the layer named by the evidence. The code-specific boundary is authenticated send lacks certificate material.
Triage data
- Provider name/type, hash algorithm, and privacy/authentication properties; associate it explicitly with it.
- When diagnosing it, whether the failure occurred while preparing, sending, storing, or validating the message; capture the value before cleanup or retry changes it.
- In the path, certificate store location and security identity used by the process; 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 whether the failure occurred while preparing, sending, storing, or validating the message.
- capture certificate store location and security identity used by the process.
- When diagnosing it, apply the code-specific recovery rule: Attach/register a certificate or use an MSMQ security context created for that sender.
Correct response
Attach/register a certificate or use an MSMQ security context created for that sender.
When diagnosing it, an immediate loop around the same call is not recovery., define who owns cancellation, handle recreation, transaction reconciliation, and duplicate suppression before another attempt is issued.
What this code is not
In the path, authentication failure is not synonymous with queue access denial. certificate stores, private keys, providers, signatures, and queue policy must be tested separately. The specific focus for it remains authenticated send lacks certificate material.
- 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 secure connector encounters it. It tests store and private-key access under the production identity before changing queue security.
A regression test should force it, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.
Technical references
- IETF RFC 5280: Internet X.509 PKI certificate profile — source used for the result analysis.
- Microsoft: Message Queuing error and information codes — source used for the result analysis.
- Microsoft: authenticated MSMQ message with an external certificate — source used for the result analysis.
- Microsoft: MSMQMessage object and message properties — source used for the result analysis.
- Microsoft: Windows certificate stores — source used for the result analysis.
Looking for a different code? Search another status or error code.