FIX: MTS Explorer Crashes When Configured the Machine Uses Remote DTC

ID: Q232330

The information in this article applies to:

Microsoft Transaction Server 2.0

SYMPTOMS

Configuring the Distributed Transaction Coordinator (DTC) on a Microsoft Transaction Server (MTS) computer to run remotely on another machine results in an access violation in the MTS Explorer during startup.

CAUSE

Configuring DTC to run remotely on an MTS is not a tested configuration. However, many applications realize a significant performance improvement when DTC is configured to run remotely. As a result, Microsoft is doing its best to support this configuration, but there are bound to be problems. The following is an example of one such problem.

The problem is ultimately to the fact that MTS explorer was receiving data for a computer name that wasn't added to its list of computers. This is because the Microsoft DTC UI component wasn't transforming the results before passing it to the MTS explorer.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Who Should Install This Release

You should install hotfix 051099d if you are experiencing access violation in MTS Explorer as discussed above.

Installation:

This hotfix should only be installed on systems running Microsoft Windows NT version 4.0 (Service Pack 5). It should not be installed on other systems running Microsoft Windows NT version 3.51 or Microsoft Windows 2000.

Note that this hotfix is based on the version of Microsoft DTC included with the Windows NT 4.0 Service Pack 5 release. By installing this hotfix, you are upgrading Microsoft DTC to the Windows NT 4.0 Service Pack 5 release level in addition to correcting the problems described here.

How to Install on a Non-clustered System

Create an empty temporary directory on your system.

Run the self-extracting executable file (i051099d.exe (i386) or a051099d.exe (alpha)) and when prompted type the name of the temporary directory. The program unzips the following files into the temporary directory:
```
   Dtcsetup.exe
   Qfe051099d.txt 
```
Stop the Microsoft DTC Service, if it is running. Stop all services that depend on Microsoft DTC (including Microsoft Transaction Server, Microsoft SQL Server, Microsoft Message Queue, and Microsoft COM Transaction Integrator (COMTI)).

Close the Windows NT Control Panel, if it is open.

Run Dtcsetup.exe.

Restart the system.

Restart all services that depend on Microsoft DTC.

How to Install on a Cluster with an Already Clustered Microsoft DTC

Create an empty temporary directory on both nodes of the cluster.

Run the self-extracting executable file (i051099d.exe (i386) or a051099d.exe(alpha)) on both nodes of the cluster and type the name of the temporary directory when you are prompted to do so. The program unzips the following files into the temporary directory:
```
   Dtcsetup.exe
   Qfe051099d.txt 
```

Use the MSCS Cluster Administrator to stop the Microsoft DTC cluster resource, if it is running. Stop all services that depend on Microsoft DTC (including Microsoft Transaction Server, Microsoft SQL Server, Microsoft Message Queue, and Microsoft COMTI).

Close the Windows NT Control Panel on all systems in the cluster.

Run Dtcsetup.exe on the node that controls the Microsoft DTC cluster resource. When you are prompted to install Microsoft DTC on the other nodes in the cluster, run Dtcsetup.exe on those nodes.

Restart all systems.

Restart all services that depend on Microsoft DTC.

How to Install on a Cluster with a Non-clustered Microsoft DTC

Create an empty temporary directory on both nodes of the cluster.

Run the self-extracting executable file (i051099d.exe (i386) or a051099d.exe (alpha)) on both nodes of the cluster and when prompted type the name of the temporary directory when you are prompted to do so. The program unzips the following files into the temporary directory:
```
   Dtcsetup.exe
   Qfe051099d.txt 
```

Stop the Microsoft DTC Service on all systems in the cluster. Stop all services that depend on Microsoft DTC (including Microsoft Transaction Server, Microsoft SQL Server, Microsoft Message Queue, and Microsoft COMTI).

Close the Windows NT Control Panel on all systems in the cluster.

When you install this release on a clustered system, the Setup program automatically installs a clustered version of Microsoft DTC. The clustered version of Microsoft DTC requires an MSCS Resource Group that contains both a Network Name Resource and a Shared Disk Resource. Before installing this release, ensure that at least one such MSCS Resource Group exists. Dtcsetup.exe assigns Microsoft DTC to the first MSCS Resource Group that it finds that contains both a Network Name Resource and Shared Disk Resource. After you ensure that the necessary Resource Group exists, run Dtcsetup.exe on the node controlling that Resource Group.

When you are prompted to install Microsoft DTC on the other nodes in the cluster, run Dtcsetup.exe on those nodes.

Reboot all systems.

Restart all services that depend on Microsoft DTC.

MORE INFORMATION

Steps to Reproduce Behavior

On the MTS server machine:

net stop msdtc

mstdc -remove

In control panel, use MSTDC config and specify the name of the other DTC computer to use as well as TCP/IP.

Restart MTS explorer and open up MTS Explorer (MMC), you will get a access violation in MMC.exe.

Additional query words:

Keywords : kbDTC kbMTS200fix kbMTSExplorer NT4SP6Fix
Version : winnt:2.0
Platform : winnt
Issue type : kbbug