You receive an error message when you install Microsoft Message Queuing 1.0/3.0 client against a Windows 2003 domain controller (324338)



The information in this article applies to:

  • Microsoft Message Queue Server (MSMQ) 1.0
  • Microsoft Message Queuing 3.0

This article was previously published under Q324338

SYMPTOMS

You may experience some or all of the following problems when you try to install a Microsoft Message Queuing (also known as MSMQ) 1.0 client against a Microsoft Windows Server 2003 domain controller:
  • You receive the following error message when you try to install a Message Queuing 1.0 client:
    An MSMQ Configuration (msmq) object with the GUID supplied cannot be created. In order to support the creation of an MSMQ Configuration object with a given GUID, Message Queuing Downlevel Client Support must be installed on a domain controller that is configured as a Global Catalog (GC) server.
  • You receive a dialog box during installation that contains the following error code:
    0xc00e008e (MQ_ERROR_GC_NEEDED)
  • Event ID 2162 is logged in the application log of Event Viewer: Message Queuing Downlevel Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer <Client Computer Name>. Creating MSMQ Configuration objects with given GUIDs may be required for Message Queuing clients during the setup of Windows NT 4.0 or Windows 9x computers and when a Windows 2000 computer joins a Windows Server 2003 domain. By default, a Windows Server 2003 forest does not support adding an object with a supplied GUID. You can solve this problem by upgrading Message Queuing on the client computer to a version that does not require creating an object with a given GUID. There are also alternative solutions.
  • The msmq config object for the MSMQ 1.0 client is not created in the Active Directory directory service.

CAUSE

The Message Queuing 1.0 Setup program assumes that the Message Queue Information Service (MQIS) server creates the MSMQ object with the GUID that the setup code provides. This is not valid for Windows Server 2003 domain controllers.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date 	    Time   Version 	Size 	File name 
-------------------------------------------------------
23-Sep-2002 08:51 		11,163 	Crdbsp7.sql 
23-Sep-2002 08:50 		19,968 	Mq2ndnd.exe 
02-Jul-2003 08:02  1.0.0.337 	61,584 	Mqac.sys 
23-Sep-2002 08:27  1.0.0.336 	34,064 	Mqcertui.dll 
02-Jul-2003 08:02  1.0.0.337 	34,064 	Mqdbmgr.dll 
02-Jul-2003 08:02  1.0.0.337 	59,152 	Mqdscli.dll 
02-Jul-2003 08:02  1.0.0.337 	56,592 	Mqdssrv.dll 
02-Jul-2003 08:02  1.0.0.337   227,088  Mqis.dll 
02-Jul-2003 08:02  1.0.0.337 	16,144 	Mqkeyhlp.dll 
02-Jul-2003 08:02  1.0.0.337   142,096  Mqoa.dll 
02-Jul-2003 08:02  1.0.0.337 	 8,464 	Mqperf.dll 
02-Jul-2003 08:02  1.0.0.337   509,200  Mqqm.dll 
02-Jul-2003 08:02  1.0.0.337   110,352  Mqrt.dll 
23-Sep-2002 08:45  1.0.0.336 1,831,320  Mqsetup.dll 
02-Jul-2003 08:02  1.0.0.337 	14,096 	Mqsvc.exe 
02-Jul-2003 08:02  1.0.0.337   106,768  Mqutil.dll 
23-Sep-2002 08:27  1.0.0.336 	62,224 	Msmq.cpl 
To implement this fix on the MSMQ 1.0 client machine before you install MSMQ, follow these steps:
  1. Create or locate the folder where you want to install MSMQ ( for example, C:\Program Files\MSMQ).
  2. Under the MSMQ folder, create a Setup folder (for example, C:\Program Files\MSMQ\Setup).
  3. Double-click the MSMQ335.exe file to extract the fix, and then copy the extracted Mqsetup.dll file in the Setup folder.
  4. Install MSMQ from the Microsoft Windows NT Option Pack. When you are prompted for the location, make sure that you select the MSMQ folder (for example, C:\Program Files\MSMQ).
  5. Apply Windows NT 4.0 Service Pack 6s (SP6a).
  6. Apply the fix to make sure that you have all the latest updates for MSMQ 1.0.
The hotfix package for this article will actually contain the fix for the following article in the Microsoft Knowledge Base:

822835 MSMQ: Event ID 2085 "Unable to create message file ..."

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB324338