| Previous | Next |
| MQ_ERROR_CANNOT_CREATE_HASH_EX | MQ_ERROR_CANNOT_DELETE_PSC_OBJECTS |
MQ_ERROR_FAIL_VERIFY_SIGNATURE_EX
Operational meaning
Applications should keep MQ_ERROR_FAIL_VERIFY_SIGNATURE_EX attached to the exact MSMQ call that produced it. It applies to received MSMQ 2.0 signature is invalid. Possible causes include message alteration, wrong certificate/key association, unsupported provider data, or malformed signature fields.
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.
Authenticated MSMQ messages combine a sender identity, certificate, private key, hash/signature algorithm, and queue policy. Successful certificate parsing does not prove that the key is accessible to the sending process.
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 | received MSMQ 2.0 signature is invalid |
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 received MSMQ 2.0 signature is invalid.
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
Quarantine the message and compare sender certificate registration before any replay.
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: received MSMQ 2.0 signature is invalid.
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.