| Previous | Next |
| MQ_ERROR_RESULT_BUFFER_TOO_SMALL | MQ_ERROR_NO_RESPONSE_FROM_OBJECT_SERVER |
MQ_ERROR_DELETE_CN_IN_USE
What this result actually narrows down
When MQ_ERROR_DELETE_CN_IN_USE appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. The result marks obsolete MQIS naming-object condition. The value documents a historical directory operation and is not a modern AD DS delete workflow.
Establish the originating binary, operating-system build, MSMQ generation, and migration phase. If those cannot be proved, treat the code as historical context rather than a current configuration prescription.
MSMQ objects involved
| Subsystem | a legacy MSMQ 1.0/enterprise setup or compatibility path retained in mq.h |
|---|---|
| Relevant condition | the symbolic value may describe an obsolete component rather than a supported modern recovery action |
| Code-specific focus | obsolete MQIS naming-object condition |
Compatibility names can outlive the component that once emitted them. Remediation must match the historical architecture, not only the symbolic text. The code-specific boundary is obsolete MQIS naming-object condition.
Triage data
- Installation or migration component name and original event text.
- Whether a current api returned the value or an old log merely contains it.
- Windows and msmq version where the code was captured.
Correct response
Use version and component evidence before applying any remediation.
What this code is not
Do not copy retired DLLs or recreate obsolete registry topology until the originating MSMQ generation and component are proved. Code-specific condition: obsolete MQIS naming-object condition.
Example failure path
Technical references
Looking for a different code? Search another status or error code.