| Previous | Next |
| MQ_INFORMATION_FORMATNAME_BUFFER_TOO_SMALL | MQ_INFORMATION_OWNER_IGNORED |
MQ_INFORMATION_INTERNAL_USER_CERT_EXIST
Operational meaning
Applications should keep MQ_INFORMATION_INTERNAL_USER_CERT_EXIST attached to the exact MSMQ call that produced it. In this case the relevant subject is idempotent certificate-registration condition. An MSMQ internal certificate is already associated with the user, so generating another one is not the next step.
Informational HRESULTs are especially easy to mishandle in wrappers that treat every nonzero value as an exception. When diagnosing this result, the caller must first determine whether the documented operation and its side effects already completed.
A warning returned from a queue or message property call can describe only one element while the other elements and the primary operation succeeded. Preserve both the returned object state and the element-level status.
Where the condition occurs
| Subsystem | the per-property status channel used by MSMQ APIs |
|---|---|
| Relevant condition | the call may complete while one array element is rejected, ignored, duplicated, or still pending |
| Code-specific focus | idempotent certificate-registration condition |
Unlike an error HRESULT, this informational value can accompany a completed operation. It must still be handled because ignored or duplicate properties can change the stored result. The code-specific boundary is idempotent certificate-registration condition.
Evidence to preserve
- The function result and every entry of the optional astatus array.
- The matching apropid and mqpropvariant index.
- Whether an output object or queue was nevertheless created.
Handling and recovery
Retrieve or use the existing registration and investigate only if it is unusable or mismatched.
Nearby failures
Do not treat a nonzero informational HRESULT as proof that the primary operation failed. Verify the completed effect and the individual property status. Code-specific condition: idempotent certificate-registration condition.
Worked example
A com-based administration utility encounters it. It records both the successful primary effect and the property warning, then corrects only the affected field.
References
Looking for a different code? Search another status or error code.