HOWTO: Install an MSMQ PSC on Microsoft Cluster Server

ID: Q188685

The information in this article applies to:
  • Microsoft Message Queue Server version 1.0

SUMMARY

Attempting to install a Microsoft Message Queue Server (MSMQ) Primary Site Controller (PSC) on Windows NT Server 4.0 Enterprise Edition with Microsoft Cluster Server installed fails. The installation succeeds on the first node but stops responding or reports that the site already exists when installing the second node.

This article documents the procedure to install am MSMQ PSC on a Windows NT Server 4.0 Enterprise Edition computer running Microsoft Cluster Server. The base system is a Cluster Server computer with Microsoft Internet Information Server (IIS) installed but Microsoft Transaction Server (MTS) not installed.

  • The version of MSMQ that comes with Windows NT Server 4.0 Enterprise Edition successfully installs to the first node of a cluster, but fails by reporting that the site already exists.


  • The version of MSMQ that comes with the Windows NT Option Pack does not automatically install the required SQL Server software so that the MSMQ PSC can build its local Message Queue Information Store (MQIS). Because of this, it cannot be used to install a PSC, Backup Site Controller (BSC), or Primary Enterprise Controller (PEC). This is true for both Cluster Server and Windows NT Server without clustering.


The first resolution to this problem is to delete the new site from the PEC after installing to the first node but before installing to the second node.

The second resolution to this problem is to first install MSMQ from the Windows NT Server 4.0 Enterprise Edition component CD to the first node and then to install the Windows NT Option Pack version to the second node.

If the Windows NT Option Pack has been installed on the cluster, you cannot install MSMQ over the MTS 2.0 Distributed Transaction Coordinator (DTC) that is installed. Trying to remove the Windows NT Option Pack so that a PSC can be installed is not a supported configuration, and may cause your cluster to be unusable. A complete rebuild starting with Windows NT Server 4.0 Enterprise Edition will be required if this is attempted.


MORE INFORMATION

The installation of MSMQ from Windows NT Server 4.0 Enterprise Edition to a cluster is documented in the Windows NT Server 4.0 Enterprise Edition Administrator's Guide and Release Notes. After installation on the first node completes successfully, follow the instructions in this article to complete the installation.

This procedure assumes that IIS 2.0 or IIS 3.0 (from Service Pack 3) is installed on the Windows NT Server computer. If IIS is not installed or is removed from the system, see the "If IIS Is Not Installed" section of this article. There could be some errors generated to the event log during some of the restarting. See the "Windows NT Event Log Errors" section at the end of this article for further information. This installation process should be done while logged on with a domain user ID.

Procedure for Installing MSMQ PSC When IIS 2.0 or 3.0 Is Installed

  1. Install Microsoft Internet Explorer 4.01 from the Windows NT Option Pack on both nodes of the cluster.


  2. Verify that the Cluster group is on Node1.


  3. On Node1 use Cluster Administrator to disable the following services:

    • MSDTC


    • MSSQLServer


    • SQLExecutive


    • MSMQ Service




  4. On Node1, run the Windows NT Option Pack installation program, using the Upgrade Only option. This will install the base product set for the Windows NT Option Pack.

    If the Gopher service was installed as part of the IIS installation, you will get a message indicating that it is no longer supported. Click OK to continue.

    If you get an MSMQ prompt for "IP Address Assignment to Connection Network", confirm that it is the Connection Network (CN) you defined when MSMQ from the Windows NT Server 4.0 Enterprise Edition CD was installed. If it is, click Continue; otherwise, change it so it is correct.


  5. When the installation completes, you will receive a message directing you to install the Windows NT Option Pack on the other nodes of the cluster. Before clicking OK on this node, perform the next step.


  6. On Node2, run the Windows NT Option Pack installation, using the Upgrade Only option.

    If the Gopher service was installed as part of the IIS installation, you will get a message indicating that it is no longer supported. Click OK to continue. When the setup is completed, allow Node2 to restart.


  7. After Node2 has restarted, go to Node1 and click OK to restart it.


  8. Start Cluster Administrator on either node and ensure that the cluster group is on Node1. Verify that all services in the cluster are online EXCEPT the MS Message Queueing service, which needs to be disabled. Move the cluster group to Node2.

    NOTES:

    • When starting the Cluster Administrator, you may get an error with an error ID of 126 (0x0000007e). Click Yes to ignore this error, and the Cluster Administrator will work properly. This error will go away after both nodes are updated and restarted, but it may take a couple of restarts for it to go away completely.


    • f you do not disable the MSMQ service before moving the cluster group to Node2 it will fail to initialize properly on Node2, and will fail back to Node1.




  9. On Node2, open the Start menu on the taskbar. Point to Programs, then point to Windows NT 4.0 Option Pack, and click Windows NT 4.0 Option Pack Setup.


  10. Click Add/Remove, and then click to place a check in the box for the Microsoft Message Queue component. Click Next.


  11. Select Primary Site Controller for the node type. After selecting Primary Site Controller, you will be prompted for a New Site Name. Use the same name you used when you installed the MSMQ PSC on Node1 from the Windows NT Server 4.0 Enterprise Edition component CD.


  12. Type the name of the PEC. You will also need to change the installation folder to the cluster share drive. This is the same name as when you installed the MSMQ PSC on Node1 from the Windows NT Server 4.0 Enterprise Edition component CD. You will get a message that "Information Server Database Exists".


  13. Select Update The Existing Database and continue. You will get an MSMQ prompt for "IP Address Assignment to Connection Network"; confirm that it is the CN you defined when MSMQ from the Windows NT Server 4.0 Enterprise Edition CD was installed. If it is, click Continue; otherwise, change it so it is correct.


  14. Continue with the installation until it completes. Click Yes to restart the node when the installation is complete.


  15. After restarting, start Cluster Administrator and start the MS Message Queue resource if it is not online.

    NOTES:

    • When starting the Cluster Administrator, you may get an error with an error ID of 126 (0x0000007e). Click Yes to ignore this error, and the Cluster Administrator will work properly. This error will go away after both nodes are updated and restarted, but it may take a couple of restarts for it to go away completely.


    • If you fail to take the Message Queue service offline from Cluster Administrator, you will get an error window stating that the install program was "Unable to create MSMQ service" with an error of 0x430. This may also cause the cluster to fail over to Node2. Using Cluster Administrator, take the MSMQ service offline, move the cluster group back to Node1 and run Windows NT Option Pack Setup again. The second time, you may not get the message about detecting a previous version. If so, you may also get an error message with a 0xC00E0013 error code. If this is the case, rerun the installation one more time.




    16. If IIS Is Not Installed

    If IIS is not installed, or removed before the Windows NT Option Pack is installed, the Windows NT Option Pack installation options screen changes. In this case, running the Windows NT Option Pack install will not give you a window with the options of Upgrade Only or Upgrade Plus. Instead, you will get a window with three buttons: Minimum, Typical, and Custom. Use the Typical option instead of the Upgrade Only option to change the items selected for installation.

    The Typical installation will not upgrade MSMQ on Node1 like the Upgrade Only option does. Therefore, it is necessary to do additional steps after completing the procedure outlined above:

  16. On Node1, open the Start menu on the taskbar. Point to Programs, then point to Windows NT 4.0 Option Pack, and click Windows NT 4.0 Option Pack Setup.


  17. Click Add/Remove and then click to place a check in the box in the list for Microsoft Message Queue component. You will get a message that a previous version of MSMQ was found. It also asks if you want to upgrade it. Click OK to continue.

    Setup will report that it cannot find Msmqocm.cab. Point it to the Ntoptpk\En\X86\Winnt.srv directory on the CD or the folder where you have downloaded the Windows NT Option Pack. Click OK to continue.


  18. The MSMQ window "IP Address Assigned to Connection Network" appears next. Check that the CN assigned is correct and click Continue. Note that this window sometimes pops up behind the Windows NT Option Pack Setup window. Look at the taskbar for the window if you do not see the progress bar in the Setup window progressing. When prompted, restart the computer.


Windows NT Event Log Errors

During this installation process there may be restarts that generate entries in the Windows NT Event Log. The known entries that have been verified, and can be ignored, are listed below. If this install process is followed, these event log entries will only appear once and then go away.
event 7000 - SCM - The MSSQLServer service failed to start due to the following error: The system cannot find the file specified.
event 7001 - SCM - The Microsoft Message Queue Service service depends on the MSSQLServer service which failed to start because of the following error: The system cannot find the file specified.


REFERENCES

For additional information, please click the article number below to view the article in the Microsoft Knowledge Base:

Q237431 INFO: MSMQ Site Controller Availability and MSCS

Additional query words: hang hangs hung IE reboot reboots

Keywords :
Version : winnt:1.0
Platform : winnt
Issue type : kbhowto


Last Reviewed: September 14, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.