What does HRESULT 0xC00E006B (MQ_ERROR_ENCRYPTION_PROVIDER_NOT_SUPPORTED) mean?

 
Previous Next
MQ_ERROR_UNSUPPORTED_OPERATION MQ_ERROR_CANNOT_SET_CRYPTO_SEC_DESCR

MQ_ERROR_ENCRYPTION_PROVIDER_NOT_SUPPORTED

What this result actually narrows down

Applications should keep MQ_ERROR_ENCRYPTION_PROVIDER_NOT_SUPPORTED attached to the exact MSMQ call that produced it. The result marks CSP/provider is outside MSMQ supported set. A provider can exist in Windows yet be incompatible with MSMQ message-signing/encryption expectations.

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.

Encryption capability and message authentication are related but distinct. Preserve provider, algorithm, certificate, key-container, and queue authentication/privacy settings rather than collapsing them into one “SSL” diagnosis.

MSMQ objects involved

SubsystemMSMQ message authentication, certificate registration, signing, hashing, and encryption
Relevant conditioncertificate identity, key availability, provider capability, and message policy are independent checks
Code-specific focusCSP/provider is outside MSMQ supported set

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 CSP/provider is outside MSMQ supported set.

Triage data

  • Whether the failure occurred while preparing, sending, storing, or validating the message.
  • Certificate store location and security identity used by the process.
  • Provider name/type, hash algorithm, and privacy/authentication properties.

Correct response

Select a documented provider and algorithm pair; do not merely install another certificate.

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: CSP/provider is outside MSMQ supported set.

Example failure path

A certificate-registration utility 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.