| Previous | Next |
| MQ_ERROR_Q_DNS_PROPERTY_NOT_SUPPORTED | MQ_ERROR_CANNOT_OPEN_CERT_STORE |
MQ_ERROR_CANNOT_CREATE_CERT_STORE
Operational meaning
The important part of MQ_ERROR_CANNOT_CREATE_CERT_STORE is not only whether the call failed, but which MSMQ subsystem had enough information to return this specific result. In this case the decisive subject is current user profile cannot create MSMQ certificate store. Profile loading and store permissions are central; machine-wide certificate changes may be irrelevant.
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, 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.
Where to draw the boundary
| 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 | current user profile cannot create MSMQ certificate store |
| Primary recovery rule | Run under the real service identity and grant only the required profile/store access. |
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 current user profile cannot create MSMQ certificate store.
Evidence to preserve
- Certificate store location and security identity used by the process; associate it explicitly with this result.
- When diagnosing it, provider name/type, hash algorithm, and privacy/authentication properties; capture the value before cleanup or retry changes it.
- In the path, whether the failure occurred while preparing, sending, storing, or validating the message; 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.
Diagnostic sequence
- Record the unsigned HRESULT, it, and the native API or COM method before a framework replaces it with a generic exception.
- In the path, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
- 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: Run under the real service identity and grant only the required profile/store access.
Handling and recovery
Run under the real service identity and grant only the required profile/store access.
When diagnosing it, retry only after a measurable state change: corrected property data, resized storage, restored service/directory reachability, recreated handle, completed transaction recovery, or repaired certificate access., bound attempts and keep an idempotency key for sends or directory mutations.
Nearby failure boundaries
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 current user profile cannot create MSMQ certificate store.
- In the path, restarting MSMQ before collecting evidence can invalidate handles and erase the first useful event; it is a containment action, not a root-cause diagnosis.
- 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.
Worked example
A certificate-registration utility 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.
References
- 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.
- 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.
Looking for a different code? Search another status or error code.