| Previous | Next |
| MQ_ERROR_FAIL_VERIFY_SIGNATURE_EX | MQ_ERROR_NO_MQUSER_OU |
MQ_ERROR_CANNOT_DELETE_PSC_OBJECTS
What this result actually narrows down
MQ_ERROR_CANNOT_DELETE_PSC_OBJECTS means legacy primary-site-controller ownership blocks delete. The object is governed by an old enterprise ownership model, not merely an ACL on a current queue.
A domain join, a successful DNS lookup, and an LDAP bind are separate checkpoints. When diagnosing this result, directory errors must be correlated with the exact naming context, object class, GUID, and domain controller used by MSMQ.
MSMQ uses directory services for public queues, machine configuration, security metadata, routing, aliases, and related enterprise objects. Private/direct queue operation can therefore succeed while a directory-dependent action fails.
MSMQ objects involved
| Subsystem | MSMQ integration with Active Directory Domain Services and the global catalog |
|---|---|
| Relevant condition | public queue metadata and MSMQ configuration objects depend on directory reachability, schema, class, ownership, and domain credentials |
| Code-specific focus | legacy primary-site-controller ownership blocks delete |
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. The code-specific boundary is legacy primary-site-controller ownership blocks delete.
Triage data
- Domain/workgroup mode, forest and domain names, and selected domain controller.
- Dns and ldap reachability plus the distinguished name being accessed.
- The directory object class, guid, owner, and replication state.
Correct response
Perform migration-aware cleanup through the owning controller/tooling.
What this code is not
Local private-queue success does not prove that public-queue registration, global catalog discovery, or the required AD DS object is healthy. Code-specific condition: legacy primary-site-controller ownership blocks delete.
Example failure path
An enterprise migration tool encounters it. It compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ.
Technical references
Looking for a different code? Search another status or error code.