Microsoft KB Archive/254405

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


"Unable to establish connection with Active Directory" error when you open Message Queue Server 1.0

Article ID: 254405

Article Last Modified on 2/16/2006



APPLIES TO

  • Microsoft Message Queue Server 1.0



This article was previously published under Q254405

SYMPTOMS

When you attempt to open Microsoft Message Queuing in the Services and Applications category of the Windows 2000 Computer Management Microsoft Management Console (MMC), the following error may appear:

"ERROR:Unable to display all public queues. Only public queues cached locally can be displayed.
Error:Unable to establish connection with Active Directory. Please verify there are sufficient permissions to perform this operation."

CAUSE

The most likely cause is that the local computer cannot connect to a Microsoft Message Queueing server with Active Directory (AD) in the domain due to an invalid Domain Name System (DNS) search order. A connection with an Active Directory server requires that DNS be able to resolve to the domain suffix name of the AD server.

If your computer receives a Dynamic Host Configuration Protocol (DHCP) assigned address, it is likely that DNS and Windows Internet Name Service (WINS) server addresses are assigned along with the DHCP assigned address for the local computer. These DNS and WINS assigned addresses may be to a Microsoft Windows NT 4.0 DNS and WINS server that do not point to the necessary Windows 2000 Active Directory server.

If your computer is a member of a Microsoft Message Queuing 1.0 Enterprise, this problem can occur if the Microsoft Message Queuing Service on the Primary Site Controller (PSC) for the site of the computer has not been started or is stopped.

RESOLUTION

To resolve this problem, follow these steps:

  1. On the computer on which you receive this error, enter ipconfig /all at a command prompt. This displays the computer's IP address, as well as its assigned DNS and/or WINS server IP addresses.
  2. Determine if the DNS address displayed is that of a Windows 2000 DNS server in the domain forest of the local computer.
  3. If it is a Windows NT 4.0 or non-Windows DNS server, the DNS must be able to resolve the name and address of the Windows 2000 Domain Controller that hosts the Message Queuing service in Active Directory.


STATUS

This behavior is by design.


Additional query words: MSMQ

Keywords: kbtshoot kbprb KB254405