HRESULT 0xC00E0042 (MQ_ERROR_DS_IS_FULL): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Obsolete, kept for backward compatibility

Previous	Next
MQ_ERROR_ILLEGAL_MQQMPROPS	MQ_ERROR_DS_ERROR

MQ_ERROR_DS_IS_FULL

Operational meaning

When MQ_ERROR_DS_IS_FULL appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. Interpret it as MSMQ 1.0 information-store capacity condition, not as a general transport outage. This value belongs to the legacy MQIS architecture and should be interpreted with the original product version.

For MQ_ERROR_DS_IS_FULL, A domain join, a successful DNS lookup, and an LDAP bind are separate checkpoints. When diagnosing MQ_ERROR_DS_IS_FULL, directory errors must be correlated with the exact naming context, object class, GUID, and domain controller used by MSMQ.

When diagnosing MQ_ERROR_DS_IS_FULL, global catalog searches and writes to a writable domain naming context have different capabilities. In the MQ_ERROR_DS_IS_FULL path, record whether the operation was discovery, read, create, update, or delete before choosing a domain controller.

Where to draw the boundary

Subsystem	MSMQ integration with Active Directory Domain Services and the global catalog
Decisive boundary	public queue metadata and MSMQ configuration objects depend on directory reachability, schema, class, ownership, and domain credentials
Code-specific focus	MSMQ 1.0 information-store capacity condition
Primary recovery rule	For modern systems, verify that the value was not preserved from migration logs or translated by compatibility code.

When diagnosing MQ_ERROR_DS_IS_FULL, A queue can exist locally while its public registration or MSMQ configuration object is absent, stale, wrong-class, or visible only on some domain controllers. For MQ_ERROR_DS_IS_FULL, the code-specific boundary is MSMQ 1.0 information-store capacity condition.

Evidence to preserve

Dns and ldap reachability plus the distinguished name being accessed; associate it explicitly with MQ_ERROR_DS_IS_FULL.
When diagnosing MQ_ERROR_DS_IS_FULL, the directory object class, guid, owner, and replication state; capture the value before cleanup or retry changes it.
In the MQ_ERROR_DS_IS_FULL path, domain/workgroup mode, forest and domain names, and selected domain controller; compare it with a known-good call using the same account and queue type.
For this MQ_ERROR_DS_IS_FULL 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_DS_IS_FULL, 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.

Diagnostic sequence

Record the unsigned HRESULT, MQ_ERROR_DS_IS_FULL, and the native API or COM method before a framework replaces it with a generic exception.
When diagnosing MQ_ERROR_DS_IS_FULL, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
In the MQ_ERROR_DS_IS_FULL path, capture the directory object class, GUID, owner, and replication state.
For this MQ_ERROR_DS_IS_FULL result, capture domain/workgroup mode, forest and domain names, and selected domain controller.
Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_DS_IS_FULL; change one precondition at a time.
When diagnosing MQ_ERROR_DS_IS_FULL, apply the code-specific recovery rule: For modern systems, verify that the value was not preserved from migration logs or translated by compatibility code.

Handling and recovery

For modern systems, verify that the value was not preserved from migration logs or translated by compatibility code.

When diagnosing MQ_ERROR_DS_IS_FULL, do not hide this HRESULT behind an unlimited framework retry. In the MQ_ERROR_DS_IS_FULL path, require a verified precondition change and preserve the original correlation identifier across the next attempt.

Nearby failure boundaries

In the MQ_ERROR_DS_IS_FULL path, local private-queue success does not prove that public-queue registration, global catalog discovery, or the required AD DS object is healthy. The specific focus for MQ_ERROR_DS_IS_FULL remains MSMQ 1.0 information-store capacity condition.

In the MQ_ERROR_DS_IS_FULL path, restarting MSMQ before collecting evidence can invalidate handles and erase the first useful event; it is a containment action, not a root-cause diagnosis.
For this MQ_ERROR_DS_IS_FULL result, granting broad queue or certificate permissions may mask the symptom while creating a security defect. For MQ_ERROR_DS_IS_FULL, test the exact identity and access needed by the operation.

Worked example

A public-queue discovery service encounters MQ_ERROR_DS_IS_FULL. For MQ_ERROR_DS_IS_FULL, it compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ. When diagnosing MQ_ERROR_DS_IS_FULL, the acceptance test then changes only the decisive precondition and confirms both the HRESULT and the actual queue/message state.

A regression test should force MQ_ERROR_DS_IS_FULL, assert the raw value and relevant outputs, then correct only the documented precondition and verify the intended success or neighboring HRESULT.

References

IETF RFC 4511: LDAP protocol — source used for the MQ_ERROR_DS_IS_FULL analysis.
Microsoft: destination queues — source used for the MQ_ERROR_DS_IS_FULL analysis.
Microsoft: Message Queuing error and information codes — source used for the MQ_ERROR_DS_IS_FULL analysis.
Microsoft Open Specifications: MSMQ and directory services — source used for the MQ_ERROR_DS_IS_FULL analysis.
Microsoft Open Specifications: MSMQ protocols overview — source used for the MQ_ERROR_DS_IS_FULL analysis.

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