How to install the Windows NT Option Pack on MSCS 1.0 with SQL Server 6.5 or 7.0

This article was previously published under Q223258
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
Summary
This article describes new installation instructions for installing theWindows NT Option Pack (NTOP) on a Microsoft Cluster Server (MSCS) withSQL Server 6.5 (with Windows NT SP4 or SQL Server SP5a) or SQL Server 7.0installed. This allows for proper fail-over of the WWW and FTPservices.

These instructions are a supplement to the general instructions providedin the following Microsoft Knowledge Base article:
191138 How to Install WindowsNT Option Pack on Microsoft Cluster Server
If the Microsoft Cluster Server has had Windows NT Service Pack 4 MSDTC,SQL Server 6.5 SP5a, or SQL Server 7.0 installed at any time, then it isnecessary to use a new installation sequence to successfully install theNT Option Pack on the cluster. After following the new installationsequence provided below, you can use the remainder of article 191138 to complete the Windows NTOption Pack installation on Microsoft Cluster Server 1.0.

A slight change to the Microsoft Distributed Transaction Coordinator(MSDTC) files that are upgraded by Windows NT Service Pack 4, SQL ServerSP5a and SQL Server 7.0 prevents the Windows NT Option Pack installationdocumented in 191138 frominstalling successfully on the second node of a Microsoft Cluster Serversystem. This article describes the steps necessary to get the Windows NTOption Pack successfully installed on both nodes of the Cluster Serverwith the updated MSDTC files.

Note: This issue with the newer MSDTC components and the Windows NTOption Pack Setup program has added some additional complexity to theinstallation sequence. Please read this entire article and make sure thatyou understand the instructions before beginning your Windows NT OptionPack installation on the Cluster Server system.
More information
If you have not yet attempted to install the Windows NT Option Pack ontoyour Microsoft Cluster Server, then you can use the following steps todetermine whether you should use the standard installation sequence fromQ191138 or whether you will need to use the new installation sequencedocumented below.

Microsoft only supports the running of MSDTC on cluster nodes as a clustered resource. MSDTC running in stand-alone mode on a cluster is not a recommended or a supported configuration. Using MSDTC in a non-clustered resource on an MSCS cluster is a problematic configuration because transactions might be orphaned, and data corruption might occur in the event of a cluster failover.
  1. The Windows NT Option Pack setup for a cluster requires that setup is runon both of the nodes in the cluster. Setup must first complete on one nodebefore setup on the second node begins. The first node that setup is runon, for the purposes of this document, will be called Node A. The secondnode of the cluster that setup is run will be called Node B.

    The designation of Node A and Node B is arbitrary as long as they are usedconsistently throughout this article and 191138.

    On whichever node that is chosen to be Node B (the last node on which yourun the Option Pack Setup program) check the version of the following twofiles:
    %windir%\system32\msdtc.exe
    %windir%\system32\msdtc.dll
  2. If the version of both of these two files is 1997.11.532.0, then you canuse the installation sequence from 191138, as it is written.
  3. If the version of either of these two files is newer than version1997.11.532.0, then you will need to use the new installation sequencedocumented below.
When you attempt to install the NTOP onto your Microsoft Cluster Serversystem that has the newer MSDTC files installed, the following errormessages occur during the installation process on Node B:
The command "C:\Winnt\System32\msdtc.exe" -join failed
Error Code = 0xffffffff
An exception occurred while installing MSDTC service.
Error Code = 0x80004005
Setup of "Transaction Server Core Components" failed. The specific errorcode is 0x748dd88.
Setup will continue but the component may not function properly.
(You will receive eight of the following errors in a row.)
CreateIISPackage or DeleteIISPackage, 0x80040154
Class not registered.
(If you had chosen to install Index Server you will see the followingerror.)
Setup could not set webhits OOP.
(At the end of the NTOP installation you will see the followingerror.)
Microsoft Transaction Server Setup was not completed successfully.
These messages mean that the installation of the NTOP on Node B has failed and IIS, MTS, and MSDTC will not run properly on Node B. To install the NTOP properly on Node B, remove the NTOP from Node B and reinstall it. Use the following steps to properly remove the NTOP from Node B:
  1. Stop the Cluster Service on Node B.
  2. On Node B, click the Add/Remove icon in Control Panel.
  3. Choose Windows NT 4.0 Option Pack from the list, and then click the Add/Remove button.
  4. When the NTOP Setup is started, choose Remove All to uninstall the Option Pack.
  5. Go to step 6 below and restart the installation process on Node B.
To eliminate the chance of a failed installation of the NTOP on MicrosoftCluster Server with SQL Server, install the following products in theorder they are listed for a fresh installation:
  • Windows NT Server 4.0 Enterprise Edition
  • Windows NT Service Pack 3
  • Microsoft Cluster Server 1.0
  • SQL Server 6.5 Enterprise Edition
  • SQL Server Cluster Service
  • Internet Explorer 4.01
  • Windows NT Option Pack
(OPTIONAL)
  • Uncluster the SQL Server Service
  • SQL Server Service Pack 5a
  • Recluster the SQL Server Service
(RECOMMENDED)
  • Windows NT Service Pack 4(If SQL Server SP5a or Windows NT SP4 is applied before the NTOPinstallation, errors will occur.)
Use the following sequence for the Windows NT Option Pack and SQL Server7.0 on Microsoft Cluster Server 1.0:
  • Windows NT 4.0 Server Enterprise Edition
  • Windows NT Service Pack 3
  • Microsoft Cluster Server 1.0
  • Internet Explorer 4.01
  • Windows NT Option Pack
  • Windows NT Service Pack 4
  • SQL Server 7.0 Enterprise Edition
  • SQL Server Cluster Service
Perform the following steps for systems with newer MSDTC files:

Note: Windows NT must reside in the same location on both Node Aand Node B. For example, if you install Windows NT to C:\Winnt on Node A,then you need to have Windows NT installed to C:\Winnt on Node B as well.If the Windows NT %SystemRoot% folder is not identical on both Node A andNode B, you will not be able to perform fail-over of IIS.

  1. Move all Cluster Resource Groups to Node A.
  2. Start the Windows NT Option Pack installation on Node A. On the "MicrosoftInternet Information Server" setup screen, accept the default location forthe WWW, FTP, and the Application Installation Point settings. During theinstallation of Transaction Server, on the "Microsoft Transaction Server2.0" screen, the Windows NT Option Pack Setup program attempts to locatethe MSDTC transaction log on a cluster disk resource in any resourcegroups currently owned by that node. The MSDTC Resource should reside inthe resource group that SQL Server is currently located in. When you areprompted for the resource group to install the MSDTC log to and thelocation for the MSDTC log file, choose the SQL Server Resource GroupNetwork Name you have created from the drop-down list and place the MSDTCLog directory on the Disk Resource that belongs to that SQL ServerResource Group. For example, if your SQL Server Resource Group NetworkName is called "SQLGroup" and the Disk Resource assigned to that group isassigned drive letter S:, you would specify "SQLGroup" in the VirtualServer drop-down list, and S:\MSDTCLog as the path to the MSDTC Logdirectory.

    DO NOT INSTALL ANYTHING INTO THE DEFAULT CLUSTER GROUP.
  3. At the end of the Windows NT Option Pack installation, a dialog box isdisplayed that instructs you to start the installation on Node B and toclick OK when the setup is complete. Disregard this message and click OKon this dialog box to continue running setup.
  4. When you are prompted to reboot on Node A, choose No. Do not restart NodeA at this point.
  5. Do not move the Resource Groups from Node A to Node B. Leave the resourcegroups running on Node A.
  6. Switch to Node B and stop the Microsoft Cluster Service by opening acommand prompt and typing the following:
    NET STOP CLUSSVC
  7. Start the Windows NT Option Pack installation on Node B. On the "MicrosoftInternet Information Server" setup screen, accept the default location forthe WWW, FTP, and the Application Installation Point settings. Thisinstallation does not prompt for the transaction log location. When thisinstallation is complete, restart Node B.
  8. If Windows NT Service Pack 4 is installed on Node B, then the ClusterServer service will not start after the NTOP is installed and the computeris restarted. This is a known issue. Please see the following article inthe Microsoft Knowledge Base for details:
    218922 Installing NTOP onCluster Server with SP4 Causes Event IDs 1009 and 1058
    You must re-apply SP4 on Node B and restart the computer again before theMicrosoft Cluster Server service will start.
  9. Move the Resource Groups from Node A to Node B.
  10. Restart Node A.
  11. If Windows NT Service Pack 4 is installed on Node A, then the clusterservice will not start after the NTOP is installed. This is a known issue.Please see the following article in the Microsoft Knowledge Base fordetails:
    218922 Installing NTOP onCluster Server with SP4 Causes Event IDs 1009 and 1058
    You must re-apply SP4 on Node A and restart the computer again before theMicrosoft Cluster Server service will start.The following 7 steps are used to ensure that MSDTC is configuredproperly for use on a clustered system.

  12. Move the resource groups from Node B to Node A. Leave the resource groupsrunning on Node A.
  13. From a command prompt on Node A, type the following:
    msdtc -remove
  14. From a command prompt on Node B, type the following:
    msdtc -remove
  15. If there is an MSDTC resource in any of the Cluster Server ResourceGroups, please delete this resource from the group that it is in. It canbe in only one resource group if it is installed. If there is no MSDTCresource in any resource groups, this is OK.
  16. From a command prompt on Node A, type the following:
    msdtc -install -d %windir%\system32 -l <location of DTC log file on SQLshared disk> -v <SQL Group Virtual Server Name>
    Note: Make sure that the directory you specify for the DTC log fileexists on the shared disk. For example, if you entered S:\MSDTCLog for the-l variable, check to be sure an MSDTCLog directory exists on the root ofthe S drive. If it does not exist, create the directory before running theabove command(for example, for SQLGroup, you would type msdtc -install -d %windir%\system32 -l S:\MSDTCLog -vSQLGroup)

  17. From a command prompt on Node B, type the following:
    msdtc -join %windir%\system32
    At this point, MSDTC will be properly installed on the Cluster and anMSDTC Resource will now exist in the SQL Server Resource Group in ClusterAdministrator. For fail-over of the SQL Server group to function properly,make sure to do step 18. Failure to perform step 18 will cause SQL ServerGroup fail-over to take up to five minutes to move from one node to theother.

  18. In the Cluster Administrator, highlight the MSDTC Resource in the SQLServer Resource Group you specified, right-click on it and chooseProperties. Click the Dependencies tab and click the Modify button. In theleft-hand frame of the Modify Dependencies Window, highlight the SQLServer Virtual Server Network Name resource and double-click on it. Thisshould move the Virtual Server Name from the left frame to the right frameand list it as a "dependency." Click OK, click Apply, and then click OK.
  19. At this point, the Web or FTP fail-over sites need to be created. InternetInformation Server (IIS) virtual servers in this configuration require aresource group with an IP address at minimum; however, it is recommendedthat you also have a disk resource to store the Web pages on aswell.

    DO NOT USE THE DEFAULT CLUSTER GROUP.
  20. Move the Resource Group that you intend on creating the IIS Instance in toNode A, if it is not already running on Node A. If you have not created aResource Group for your World Wide Web sites, create one now and give it adisk resource and IP address resource that your WWW site will use (forexample, if your Resource Group for your Web Sites is called WWWGroup,move the WWWGroup to Node A).
  21. In the Microsoft Management Console (MMC) on Node A, expand the InternetInformation Server tree, right-click on the computer name, and create anew Web (or FTP) site.
  22. In the properties for this new site, set the IP address of the site to bethe same as the IP address resource for the resource group thatthis Web site will reside in (for example, if you have an "IP Address"Resource in your WWWGroup, and it is configured as 10.5.5.1, configure thenew Web site to use this address in the MMC).
  23. Select the directory, Universal Naming Convention (UNC) connection, orredirection that the site should use as the home directory. If you areselecting a drive, it should be a disk resource that is in the sameResource Group that the IP address is in.
  24. Repeat Steps 21 through 23 for each WWW of FTP site that you want toprovide fail-over capabilities to.
At this point in the installation process, you can refer back to 191138 and proceed through the restof that article without problems, beginning at "Synchronize the IIS UserAccounts."

For more information, please see the following Web page:
Properties

Article ID: 223258 - Last Review: 10/26/2013 13:02:00 - Revision: 5.0

  • kbnosurvey kbarchive kbhowto KB223258
Feedback