| 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. In this case the relevant 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.
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 |
|---|---|
| Relevant condition | certificate identity, key availability, provider capability, and message policy are independent checks |
| Code-specific focus | authenticated send lacks certificate material |
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.
- Whether the failure occurred while preparing, sending, storing, or validating the message.
- Certificate store location and security identity used by the process.
Correct response
Attach/register a certificate or use an MSMQ security context created for that sender.
What this code is not
Authentication failure is not synonymous with queue access denial. Certificate stores, private keys, providers, signatures, and queue policy must be tested separately. Code-specific condition: authenticated send lacks certificate material.
Example failure path
A secure connector encounters it. It tests store and private-key access under the production identity before changing queue security.
Technical references
Looking for a different code? Search another status or error code.