| Previous | Next |
| MQ_ERROR_CANNOT_DELETE_PSC_OBJECTS | MQ_ERROR_CANNOT_LOAD_MQAD |
MQ_ERROR_NO_MQUSER_OU
Retry and cleanup
Create/restore it according to the migration schema and delegate only required permissions.
Avoiding a false diagnosis
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: required MSMQ Users container missing during migration.
Example
A public-queue discovery service encounters it. It compares DNS, LDAP bind, object class, and replication on the exact domain controller used by MSMQ.
Migration container requirements
It is specifically tied to migration of MSMQ user objects and the expected MSMQ Users organizational unit. Confirm the target domain naming context, the OU distinguished name, object class, inheritance settings, and permissions granted to the migration account. Creating a similarly named container in the wrong domain or as the wrong AD DS class does not satisfy the migration code.
- Use LDAP tools to read the exact distinguished name from the same domain controller selected by the migration process.
- Allow for replication before rerunning migration on another site or domain controller.
- Document who owns the OU after migration so later cleanup does not remove objects still referenced by certificates or queue security metadata.
References
Looking for a different code? Search another status or error code.