| Previous | Next |
| MQ_ERROR_WKS_CANT_SERVE_CLIENT | MQ_CORRUPTED_QUEUE_WAS_DELETED |
MQ_ERROR_DEPEND_WKS_LICENSE_OVERFLOW
Operational meaning
Applications should keep MQ_ERROR_DEPEND_WKS_LICENSE_OVERFLOW attached to the exact MSMQ call that produced it. In this case the relevant subject is dependent-client capacity limit reached. This reflects the historical licensing/topology ceiling of the serving MSMQ system.
Establish the originating binary, operating-system build, MSMQ generation, and migration phase. When diagnosing this result, if those cannot be proved, treat the code as historical context rather than a current configuration prescription.
A legacy code found in an event archive is evidence about the deployment generation. Copying old DLLs or registry settings into a current Windows installation can make the system less recoverable.
Where the condition occurs
| 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 | dependent-client capacity limit reached |
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 dependent-client capacity limit reached.
Evidence to preserve
- Whether a current api returned the value or an old log merely contains it.
- Windows and msmq version where the code was captured.
- Installation or migration component name and original event text.
Handling and recovery
Inventory clients and product versions instead of retrying connections.
Nearby failures
Do not copy retired DLLs or recreate obsolete registry topology until the originating MSMQ generation and component are proved. Code-specific condition: dependent-client capacity limit reached.
Worked example
Historical dependent-client capacity
It belongs to the old dependent-client deployment model, in which a supporting Message Queuing server served a bounded population of clients. The useful evidence is the count and identity of dependent clients, the product edition and license terms active at the time, and whether stale registrations remained after computers were retired or renamed. Modern retry logic cannot create capacity in that topology.
- Reconstruct the serving relationship from original administration data rather than from current DNS names alone.
- Check whether the application can be moved to an independent/full MSMQ installation or a supported server role.
- Preserve the historical configuration before migration because the same symbolic code may never be emitted by a current Windows release.
References
Looking for a different code? Search another status or error code.