| Previous | Next |
| MQ_ERROR_GUID_NOT_MATCHING | MQ_ERROR_PUBLIC_KEY_DOES_NOT_EXIST |
MQ_ERROR_PUBLIC_KEY_NOT_FOUND
Operational meaning
MQ_ERROR_PUBLIC_KEY_NOT_FOUND belongs to the Message Queuing HRESULT facility, but its useful meaning is narrower than a generic messaging failure. In this case the relevant subject is requested enhanced key unavailable on older-capability computer. The directory query succeeded, but the target supports only the legacy encryption capability.
Encryption capability and message authentication are related but distinct. When diagnosing this result, preserve provider, algorithm, certificate, key-container, and queue authentication/privacy settings rather than collapsing them into one “SSL” diagnosis.
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.
Where the condition occurs
| 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 | requested enhanced key unavailable on older-capability computer |
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 requested enhanced key unavailable on older-capability computer.
Evidence to preserve
- Certificate store location and security identity used by the process.
- Provider name/type, hash algorithm, and privacy/authentication properties.
- Whether the failure occurred while preparing, sending, storing, or validating the message.
Handling and recovery
Negotiate a compatible privacy level or upgrade the destination MSMQ capability.
Nearby failures
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: requested enhanced key unavailable on older-capability computer.
Worked example
A service sending authenticated messages encounters it. It tests store and private-key access under the production identity before changing queue security.
References
Looking for a different code? Search another status or error code.