Microsoft KB Archive/282860

= How To Apply SQL Server 7.0 Service Packs When MSMQ Is a Site Controller =

Article ID: 282860

Article Last Modified on 10/26/2007

-

APPLIES TO


 * Microsoft Message Queue Server 1.0

-



This article was previously published under Q282860



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
To successfully install Microsoft SQL Server 7.0 service packs, you must first uncluster SQL Server. Because a Microsoft Message Queue (MSMQ) Site Controller, which can be a Primary Enterprise Controller (PEC), Primary Site Controller (PSC), or Backup Site Controller (BSC), depends on SQL Server, you must follow the steps in this article to safely remove MSMQ's dependency on SQL Server in order to install the SQL Server service packs.



MORE INFORMATION
To install a SQL Server 7.0 service pack on an MSMQ Message Queue Information Store (MQIS) server that is installed on a cluster, follow these steps:

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

 Open Cluster Administrator. Take the MSMQ resource offline. Remove the dependencies of MSMQ on SQL Server and the SQL network name:  If you have another network name in the same group, configure MSMQ to depend on that network name. If you do not have another network name in the same group, create a temporary network name and IP address resources on the MSMQ resource and configure the MSMQ resource to depend on them. This is necessary because the MSMQ resource requires a dependency on a network name resource. </li> Make sure that no other cluster resources depend on any of the cluster resources that are related to SQL Server. There are five types of these resources:  SQL network name</li> SQL IP address</li> SQL server</li> SQL Agent</li> SQL VServer</li></ul> </li> Use the SQL Clustering Wizard to uncluster SQL Server. Make sure that the wizard removes all the resources and resource types that are related to SQL Server.</li> Apply the service pack.</li> Open Regedt32 and locate the following registry key:

HKLM\Software|Microsoft\MSMQ\Parameters\MachineCache\MQS

This key should have a value of 2 for BSC, 4 for PSC, or 8 for PEC. Write down the current value and change the value to 1.</li> Use the SQL Clustering Wizard to recluster SQL Server.</li> Open Regedt32, and restore the value of the following key

HKLM\Software|Microsoft\MSMQ\Parameters\MachineCache\MQS

to its original value.</li> Using Cluster Administrator, restore the dependencies of MSMQ on SQL Server and the SQL network name. Remove the dependencies on any other network name.</li> If you created a temporary network name and IP address resources in step 3, delete them.</li> Bring the MSMQ resource online.</li></ol>

<div class="references_section">