What does HRESULT 0xC00E0035 (MQ_ERROR_BAD_SECURITY_CONTEXT) mean?

MQ_ERROR_BAD_SECURITY_CONTEXT

What this result actually narrows down

When MQ_ERROR_BAD_SECURITY_CONTEXT appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. The result marks invalid cached MSMQ security context handle. A context created for certificate/SID reuse is stale, malformed, or belongs to another lifecycle.

For MQ_ERROR_BAD_SECURITY_CONTEXT, encryption capability and message authentication are related but distinct. When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, preserve provider, algorithm, certificate, key-container, and queue authentication/privacy settings rather than collapsing them into one “SSL” diagnosis.

When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, authenticated MSMQ messages combine a sender identity, certificate, private key, hash/signature algorithm, and queue policy. In the MQ_ERROR_BAD_SECURITY_CONTEXT path, successful certificate parsing does not prove that the key is accessible to the sending process.

MSMQ objects involved

When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, queue ACLs, certificate trust, private-key access, provider support, and destination authentication policy are independent. Test the layer named by the evidence. For MQ_ERROR_BAD_SECURITY_CONTEXT, the code-specific boundary is invalid cached MSMQ security context handle.

Triage data

• Provider name/type, hash algorithm, and privacy/authentication properties; associate it explicitly with MQ_ERROR_BAD_SECURITY_CONTEXT.
• When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, whether the failure occurred while preparing, sending, storing, or validating the message; capture the value before cleanup or retry changes it.
• In the MQ_ERROR_BAD_SECURITY_CONTEXT path, certificate store location and security identity used by the process; compare it with a known-good call using the same account and queue type.
• For this MQ_ERROR_BAD_SECURITY_CONTEXT result, record the queue path or format name, local/remote placement, transactional flag, caller SID, process build, and UTC correlation ID when they apply.

For MQ_ERROR_BAD_SECURITY_CONTEXT, 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.

A safe investigation order

1. Record the unsigned HRESULT, MQ_ERROR_BAD_SECURITY_CONTEXT, and the native API or COM method before a framework replaces it with a generic exception.
2. Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_BAD_SECURITY_CONTEXT; change one precondition at a time.
3. In the MQ_ERROR_BAD_SECURITY_CONTEXT path, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
4. For this MQ_ERROR_BAD_SECURITY_CONTEXT result, capture whether the failure occurred while preparing, sending, storing, or validating the message.
5. For MQ_ERROR_BAD_SECURITY_CONTEXT, capture certificate store location and security identity used by the process.
6. When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, apply the code-specific recovery rule: Discard and recreate the security context; never serialize or reuse it across unsupported boundaries.

Correct response

Discard and recreate the security context; never serialize or reuse it across unsupported boundaries.

When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, the retry decision must account for side effects that may already exist. In the MQ_ERROR_BAD_SECURITY_CONTEXT path, query queue, message, directory, or transaction state first whenever the result leaves completion uncertain.

What this code is not

In the MQ_ERROR_BAD_SECURITY_CONTEXT path, authentication failure is not synonymous with queue access denial. For this MQ_ERROR_BAD_SECURITY_CONTEXT result, certificate stores, private keys, providers, signatures, and queue policy must be tested separately. The specific focus for MQ_ERROR_BAD_SECURITY_CONTEXT remains invalid cached MSMQ security context handle.

• In the MQ_ERROR_BAD_SECURITY_CONTEXT path, granting broad queue or certificate permissions may mask the symptom while creating a security defect. For this MQ_ERROR_BAD_SECURITY_CONTEXT result, test the exact identity and access needed by the operation.
• For this MQ_ERROR_BAD_SECURITY_CONTEXT result, changing queue names, deleting directory objects, or recreating certificates without reconciliation can create a second object while callers still reference the first.

Example failure path

A service sending authenticated messages encounters MQ_ERROR_BAD_SECURITY_CONTEXT. For MQ_ERROR_BAD_SECURITY_CONTEXT, it tests store and private-key access under the production identity before changing queue security. When diagnosing MQ_ERROR_BAD_SECURITY_CONTEXT, the acceptance test then changes only the decisive precondition and confirms both the HRESULT and the actual queue/message state.

For MQ_ERROR_BAD_SECURITY_CONTEXT, include a negative test for the nearest misleading diagnosis so monitoring and user guidance do not collapse distinct MSMQ failures into one alert.

Technical references

• Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_BAD_SECURITY_CONTEXT analysis.
• Microsoft: authenticated MSMQ message with an external certificate — source used for the MQ_ERROR_BAD_SECURITY_CONTEXT analysis.
• Microsoft: MSMQMessage object and message properties — source used for the MQ_ERROR_BAD_SECURITY_CONTEXT analysis.
• Microsoft: Windows certificate stores — source used for the MQ_ERROR_BAD_SECURITY_CONTEXT analysis.
• IETF RFC 5280: Internet X.509 PKI certificate profile — source used for the MQ_ERROR_BAD_SECURITY_CONTEXT analysis.

Looking for a different code? Search another status or error code.