| Previous | Next |
| MQ_INFORMATION_OPERATION_PENDING | MQ_INFORMATION_INTERNAL_USER_CERT_EXIST |
MQ_INFORMATION_FORMATNAME_BUFFER_TOO_SMALL
What this result actually narrows down
MQ_INFORMATION_FORMATNAME_BUFFER_TOO_SMALL means successful queue creation with truncated output capacity. The queue exists even though the caller did not receive its complete format name.
MSMQ property structures can include an optional status array parallel to the property identifiers and values. When diagnosing this result, A nonfatal top-level result therefore does not replace inspection of individual entries.
Informational HRESULTs are especially easy to mishandle in wrappers that treat every nonzero value as an exception. The caller must first determine whether the documented operation and its side effects already completed.
MSMQ objects involved
| 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 | successful queue creation with truncated output capacity |
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 successful queue creation with truncated output capacity.
Triage data
- The matching apropid and mqpropvariant index.
- Whether an output object or queue was nevertheless created.
- The function result and every entry of the optional astatus array.
Correct response
Discover the created queue using its path name or request a larger format-name buffer; do not blindly create it again.
What this code is not
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: successful queue creation with truncated output capacity.
Example failure path
A com-based administration utility encounters it. It records both the successful primary effect and the property warning, then corrects only the affected field.
Technical references
Looking for a different code? Search another status or error code.