Article ID: 811033 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
If Microsoft Message Queuing cannot resolve the name of the MQIS (Message Queue Information Store) or domain controller, it fails when it tries to open public queues. Message Queuing cannot initialize in offline mode (and cannot open local public queues) if it cannot resolve the name of the MQIS or domain controller server.
Each Message Queuing client keeps a list of MQIS servers in the registry (either Microsoft Windows NT 4.0 primary event collectors [PECs], primary site controllers [PSCs], backup site controllers [BSCs], or Windows 2000 domain controllers). When one of the servers in the list is not responding, Message Queuing jumps to the next server. However, if the IP address of the server cannot be resolved, Message Queuing quits and stops the name resolution process.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Date Time Version Size File name -------------------------------------------------------------- 04-Dec-2002 21:15 188.8.131.525 67,200 Mqac.sys 04-Dec-2002 21:16 184.108.40.2065 17,408 Mqbkup.exe 04-Dec-2002 21:47 220.127.116.115 44,032 Mqdscli.dll 04-Dec-2002 21:46 18.104.22.1685 611,328 Mqqm.dll 04-Dec-2002 21:46 22.214.171.1245 164,864 Mqrt.dll 04-Dec-2002 21:46 126.96.36.1995 89,088 Mqsec.dll 05-Dec-2002 18:33 188.8.131.52 1,018,216 Q811033_wxp_sp2_x86_enu.exe
The following information appears in the Message Queuing diagnostic log when this problem occurs:
0x7bc> Thu Nov 14 09:28:23 2002: QM Error: cqmgr/20, HR: 0x80072af9 0x7bc> Thu Nov 14 09:28:23 2002: QM Error: cqmgr/80, HR: 0x80072af9 0x7bc> Thu Nov 14 09:28:23 2002: QM Error: cqmgr/130, HR: 0x80072af9 0x7bc> Thu Nov 14 09:28:23 2002: QM Error: cqmgr/220, HR: 0x80072af9 0x7bc> Thu Nov 14 09:28:23 2002: QM Error: qmcommnd/20, HR: 0x80072af9