HRESULT 0xC00E0089 (MQ_ERROR_CANT_RESOLVE

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The sites where the computer resides cannot be resolved. Check that the subnets in your network are configured correctly in Active Directory Domain Services and that each site is configured with the appropriate subnet.

Previous	Next
MQ_ERROR_MESSAGE_NOT_FOUND	MQ_ERROR_NOT_SUPPORTED_BY_DEPENDENT_CLIENTS

MQ_ERROR_CANT_RESOLVE_SITES

What this result actually narrows down

When MQ_ERROR_CANT_RESOLVE_SITES appears, start with the queue operation and its property arrays rather than with a broad repair of the Message Queuing service. It applies to AD DS site cannot be derived from subnet configuration. MSMQ routing depends on mapping computer addresses to correctly configured AD sites and subnets.

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

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

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	AD DS site cannot be derived from subnet configuration

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 AD DS site cannot be derived from subnet configuration.

Triage data

The directory object class, guid, owner, and replication state.
Domain/workgroup mode, forest and domain names, and selected domain controller.
Dns and ldap reachability plus the distinguished name being accessed.

Correct response

Fix site/subnet associations and replication rather than hard-coding a route.

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: AD DS site cannot be derived from subnet configuration.

Example failure path

A public-queue discovery service 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.