Event ID 2162 — Message Queuing Windows 2000 Client Support Active Directory Operation

  • Article

Applies To: Windows Server 2008 R2

You can use the Message Queuing Windows 2000 Client Support service to run Message Queuing in domain mode on Windows 2000 computers that are joined to a Windows Server 2003 domain or a Windows Server 2008 domain. This service must be able to interact with Active Directory Domain Services (AD DS) to operate properly.

Event Details

Product: Windows Operating System
ID: 2162
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_MQDS_GC_NEEDED
Message: Message Queuing Downlevel Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer %1. Creating MSMQ Configuration objects with given GUIDs may be required for Message Queuing clients when a Windows 2000 computer joins a Windows Server 2003 (or later) domain. By default, an Active Directory forest does not support adding an object with a supplied GUID.

Resolve

Add the Message Queuing Service to a domain controller that is also running as a global catalog server

The Message Queuing Service must be installed and started on a Windows Server 2008 domain controller that is also a global catalog server.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Manually determine if the domain controller has a global catalog

To manually determine if the domain controller is a global catalog server (Windows Server 2008):

  1. Open the Active Directory Users and Computers snap-in. To open Active Directory Users and Computers, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

  2. On the View menu, enable both Users, Contacts, Groups and Computers as containers and Advanced Features.

  3. In the console tree, under Domain Controllers, locate your computer. Right-click your computer, and then click Properties.

  4. Click the General tab.

  5. Determine whether DC Type is Global Catalog.

    If Global Catalog appears and you continue to receive this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (https://go.microsoft.com/fwlink/?LinkId=52267).

Add a global catalog

If your local domain controller is not a global catalog server, contact your domain administrator to set up your domain controller as a global catalog server.

If you are the domain administrator, use the following procedure.

To add the global catalog:

  1. On the domain controller where you want the new global catalog, open the Active Directory Sites and Services snap-in. To open Active Directory Sites and Services, click Start, point to Administrative Tools, and then click Active Directory Sites and Services.
  2. In the console tree, double-click Sites, and then double-click sitename.
  3. Double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties.
  4. On the General tab, select the Global catalog check box to assign the global catalog to this server.
  5. Restart the domain controller.

Verify

Verify that the Message Queuing Windows 2000 Client Support service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Message Queuing Windows 2000 Client Support service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Windows 2000 Client Support service.
  3. Verify that the Message Queuing Windows 2000 Client Support service is started.
  4. For further confirmation, run a test application that uses the Active Directory features that you require.

Message Queuing Windows 2000 Client Support Active Directory Operation

Message Queuing