Configuring MTS with Microsoft Cluster Server

[This product will work only on Windows NT 4.0 versions and earlier. For Windows 2000 and later, see COM+ (Component Services).]

Microsoft Cluster Server (MSCS) is the clustering solution for computers running Windows NT Server. MSCS version 1.0 supports clusters of two specially linked servers running Windows NT Server. If one server in a cluster fails or is taken offline, the other server takes over the failed server's operations.

If you wish to use Microsoft Transaction Server with MSCS, first install Windows NT Server 4.0 Enterprise. Then install Microsoft Cluster Server 1.0. Finally, install Microsoft Transaction Server 2.0 as described below.

Note MTS 2.0 cluster support does not work with pre-release versions of Microsoft Cluster Server 1.0. Installing MTS 2.0 with a pre-release version of Microsoft Cluster Server will prevent MSCS from functioning properly.

For more information on MSCS, see Windows NT Books Online.

To install Microsoft Transaction Server 2.0 with Microsoft Cluster Server 1.0

1. Install Windows NT Server 4.0 Enterprise.
2. Install MSCS 1.0 on all computers in the cluster.
3. Use the MSCS Cluster Administrator to configure a Group to contain a Network Name Resource and a Shared Disk Resource.
4. Install Microsoft Transaction Server 2.0 on the node that owns the Group configured above. See Setting Up Microsoft Transaction Server for more information.
5. When MTS setup detects that MSCS is present on the system, it will display a dialog box asking you to specify the name of the Virtual Server on which MS DTC should be installed. Specify the name of the Network Name Resource configured in step 3.
6. In the same dialog box, specify the location for the MS DTC log file on the shared disk configured in step 3.
7. Click NEXT to continue MTS setup.
8. Install MTS on the second computer in the cluster. You will not be prompted for the virtual server and log file location during setup.

Do not run MTS setup in parallel on cluster nodes. Completely install MTS on one node, then install MTS on the second node without rebooting the first node. When both nodes have MTS installed, reboot them.

Note You do not not need to uninstall Microsoft Transaction Server 1.0 before Microsoft Transaction Server 2.0 with Microsoft Cluster Server 1.0. Follow the instructions for installing MTS 2.0 with MCS 1.0.

To upgrade from Microsoft Transaction Server 1.1 to Microsoft Transaction Server 2.0 with Microsoft Cluster Server

1. Delete all Microsoft Transaction Server package resources that you created when using Microsoft Transaction Server 1.1 with Microsoft Cluster Server.
2. Run the Microsoft Transaction Server 2.0 setup program on the cluster node that owns the MS DTC resource. This will automatically perform the upgrade on this node. Ensure that Microsoft Transaction Server setup runs to completion before starting the next step.
3. Run the Microsoft Transaction Server 2.0 setup program on the second node of the cluster.
4. Reboot both cluster nodes.

Uninstalling Microsoft Cluster Server on an MTS Server

If you want to uninstall Microsoft Cluster Server from one of the nodes in a cluster, follow these steps:

1. Using the Cluster Administrator to take the MS DTC resource offline.
2. Uninstall Microsoft Cluster Server from the node and reboot the node.
3. Change the location of the MS DTC log file using the Transaction Server Explorer. The log file must be placed on a non-shared disk. Failing to do this may result in a corrupted log file or access violations in MS DTC.

Resetting the MS DTC Log File on Clustered Servers

To reset the MS DTC log file on a clustered server, you must run the MTS Explorer on the node that currently owns the shared disk containing the log file.

Starting and Stopping MS DTC on Clustered Servers

On a clustered server, you can start and stop MS DTC by either using the MTS Explorer or using the MSCS administrative utility. Using the "net start msdtc" or "net stop msdtc" command does not work. To start and stop MS DTC on an MSCS cluster from the command line, use "msdtc -start" and "msdtc -stop", respectively.

Calling MTS Objects after MSCS Failover

Microsoft Transaction Server client applications must always release all references to MTS components on the failing node, and re-instantiate the components. The components are instantiated on the second node.

Using the Remote Components Folder with Clustered Servers

You can use the Remote Components folder to pull components from a Microsoft Cluster Server (MSCS) node by following these steps:

1. On the server computer from which you will pull components, right-click on My Computer and select Properties.
2. Click the Options tab and enter the name of the virtual server in the Remote Server Name field. Click OK.
3. On the client computer to which you will pull components, add the MSCS computer to the Computers folder using the physical name of the server.
4. Select the Remote Components folder and choose New from the Action menu. You can also right-click the Remote Components folder, select New and then Component.
5. Follow the instructions in the remote component installation wizard. Note that during the installation of remote components, the physical name of the server will be displayed rather than the virtual name (as specified in the Remote Server Name field of the server computer).
6. Select the Remote Components folder and click the Property View button on the MTS Explorer toolbar. The Server column in the Property View window displays the virtual server name.

Note If you change the remote server name on the MSCS computer, you must also reinstall the remote components on client computers.

Replicating Empty Packages

MTS replication does not replicate empty packages.

MTS Package Identities Must Be in Administrator Group on MSCS Clusters

For MTS packages on MSCS clusters, the user account associated with the package identity must be a system administrator or must have Full Control cluster access permissions (as set in cluadmin). If you do not run the package under the identity of a system administrator, MTS will be unable to connect to MS DTC.

Shut Down MSCS Cluster Resources Before Installing MTS

You must shut down all MSCS cluster resources (such as SQL Server) that are affected by MTS setup prior to running the MTS setup program.

Remote Server Name Must Specify a Virtual Server on MSCS Servers

Clustered servers must set the Remote Server Name property to a virtual server name using the MTS Explorer. This enables remote clients to access MTS components within the cluster, and, in the event of failure, ensures that clients are referencing the cluster, not a specific node within that cluster.