BUG: Cannot Create Private$ Queues Using MSMQ from Option Pack

Last reviewed: March 9, 1998
Article ID: Q182120
The information in this article applies to:
  • Microsoft Message Queue Server version 1.0

SYMPTOMS

After you perform a new installation of Microsoft Message Queue Server (MSMQ) from the Windows NT Server 4.0 Option Pack, you cannot create PRIVATE$ queues in a cluster.

CAUSE

After running Windows NT Server 4.0 Option Pack Setup on a cluster, the LastPrivateQueueId is not stored in the registry. When trying to create a PRIVATE$ queue, the Queue Manager fails to retrieve the data, and returns MQ_ERROR.

WORKAROUND

To work around this problem, obtain the hotfix mentioned in the STATUS section of this article.

NOTE: This hotfix only applies to a new installation of Windows NT Server 4.0 Option Pack on an MSMQ Routing Server or Independent Client on a cluster. It should not be used when the Windows NT Server 4.0 Option Pack is used to upgrade the version of MSMQ installed from Windows NT Server 4.0 Enterprise Edition.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Message Queue Server version 1.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

IMPORTANT: Read the NOTE in the WORKAROUND section before you attempt to install the hotfix.

MORE INFORMATION

After obtaining the hotfix from Microsoft Technical Support, perform the following steps to install it:

  1. Copy I0267.exe (for computers with an Intel processor) or A0267.exe (for computers with an Alpha processor) to an empty directory and then run it. The Readme.txt file contains these instructions, as well as descriptions of the problems corrected by the hotfix.

          Hotfix files
          ------------
    

          Mqqm.dll
          Readme.txt
    

  2. Stop any applications that depend on the Microsoft Message Queue service.

  3. To install the hotfix, you must stop the Microsoft Message Queue service. To do this, do either one of the following, depending on whether your computer is clustered:

        - On a computer running Microsoft Cluster Server, use Cluster
          Administrator to take the Microsoft Message Queue resource offline.
    

        - On a non-clustered computer, open Control Panel Services and stop the
          Microsoft Message Queue service.
    

  4. Copy or rename the Mqqm.dll file in the %windir%\System32 directory, so you can restore it if there are problems with the hotfix on your computer.

  5. Copy the Mqqm.dll file that was generated from the hotfix (in step 1 of this procedure) to the %windir%\System32 directory.

  6. Restart the Microsoft Message Queue Service, using either of the following methods (depending on whether your computer is clustered):

        - On a computer running Microsoft Cluster Server, use Cluster
          Administrator to bring the Microsoft Message Queue resource online.
    

        - On a non-clustered computer, open Control Panel Services and start
          the Microsoft Message Queue service.
    

  7. Restart any applications that depend on the Microsoft Message Queue service (that you had stopped in step 2 of this procedure).


Additional query words: QM winnt fix
Keywords : MQConfig MQInstall MQProg kbbug1.00
Version : WinNT:1.0
Platform : winnt
Hardware : ALPHA x86
Issue type : kbbug
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.