What does HRESULT 0xC00E0095 (MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS) mean?

MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS

Operational meaning

When MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. Its diagnostic boundary is legacy PSC-owned object cannot be created here. Creation must occur through the historical primary-site-controller ownership path.

For MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, MSMQ uses directory services for public queues, machine configuration, security metadata, routing, aliases, and related enterprise objects. When diagnosing MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, private/direct queue operation can therefore succeed while a directory-dependent action fails.

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

Where to draw the boundary

When diagnosing MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, 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_CANNOT_CREATE_PSC_OBJECTS, the code-specific boundary is legacy PSC-owned object cannot be created here.

Evidence to preserve

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

1. Record the unsigned HRESULT, MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, and the native API or COM method before a framework replaces it with a generic exception.
2. Reproduce with the smallest queue/message/property set that still returns MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS; change one precondition at a time.
3. In the MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS path, verify the postcondition after the failed call: queue existence, message presence, directory object state, transaction outcome, or generated output may differ by result.
4. For this MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS result, capture DNS and LDAP reachability plus the distinguished name being accessed.
5. For MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, capture the directory object class, GUID, owner, and replication state.
6. When diagnosing MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, apply the code-specific recovery rule: Use migration-aware administration instead of ordinary queue creation APIs.

Handling and recovery

Use migration-aware administration instead of ordinary queue creation APIs.

When diagnosing MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, the retry decision must account for side effects that may already exist. In the MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS path, query queue, message, directory, or transaction state first whenever the result leaves completion uncertain.

Nearby failure boundaries

In the MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS 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_CANNOT_CREATE_PSC_OBJECTS remains legacy PSC-owned object cannot be created here.

• In the MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS 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_CANNOT_CREATE_PSC_OBJECTS result, granting broad queue or certificate permissions may mask the symptom while creating a security defect. For MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, test the exact identity and access needed by the operation.

Worked example

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

Automated coverage should preserve the original arrays/identities, confirm that cleanup is safe after MQ_ERROR_CANNOT_CREATE_PSC_OBJECTS, and test that a retry does not duplicate messages or directory objects.

References

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

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