Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

List of the MS DTC issues that are fixed in Windows Server 2003 MS DTC Hotfix Rollup Package 15


View products that this article applies to.

INTRODUCTION

This article lists the Microsoft Distributed Transaction Coordinator (MS DTC) issues that are fixed in Windows Server 2003 MS DTC Hotfix Rollup Package 15. Each hotfix rollup package contains all the fixes that were released in the previous Windows Server 2003 MS DTC hotfix rollup package.

Issues that are fixed in this hotfix rollup package

This hotfix rollup package fixes the following two issues that were not previously documented in a Microsoft Knowledge Base article.

Issue 1

When a Transaction Internet Protocol (TIP) subordinate transaction manager pulls a transaction from Microsoft Distributed Transaction Coordinator (MS DTC) by using TIP, a memory leak may occur in the MS DTC service. When transactions are repeatedly pulled from MS DTC, the leaked memory may accumulate, and this eventually causes the MS DTC process to terminate.

Issue 2

Consider the following scenario:
  • MS DTC is deployed as a cluster resource on a dependent disk.
  • The disk has multiple partitions (volumes).
  • You create a new partition at the beginning of the disk.
In this scenario, the MS DTC resource may be unable to come online.

↑ Back to the top


Cause

Cause of Issue 1

When a TIP subordinate transaction manager pulls a transaction, it sends a PULL TIP command to an MS DTC service instance, and the command specifies the superior’s transaction identifier. Then, the MS DTC service tries to locate the transaction object according to the specified identifier, and the service responds to the TIP subordinate transaction manager by issuing the PULLED TIP command.

A memory leak occurs during the processing of the TIP PULL request. When repeated PULL TIP commands are sent to the MS DTC service, the leaked memory accumulates, and this eventually causes the MS DTC process to terminate.

↑ Back to the top


Cause of Issue 2

When an MS DTC resource is created in a cluster, the disk's first partition is used to store the DTC log files, and this partition is recorded in the registry. Every time that the clustered MS DTC resource comes online, it validates whether the path of the log files (as recorded in the registry) exists on the disk.

However, MS DTC checks only the first partition. This issue occurs if a new partition is created, and then the new partition becomes the first partition.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed to apply this hotfix rollup package.

Restart requirement

You must restart the MS DTC service after you apply this hotfix rollup package.

Hotfix replacement information

Bugs that are fixed in the Windows Server 2003 MS DTC hotfix rollup packages are cumulative. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

952943 List of the MS DTC bugs that are fixed in Windows Server 2003 MS DTC Hotfix Rollup Package 14


File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, x86-based versions
File nameFile versionFile sizeDateTimeSP requirementService branch
Msdtc.exe2001.12.4720.33166,14430-Mar-200910:36SP1SP1QFE
Msdtclog.dll2001.12.4720.331676,28830-Mar-200915:24SP1SP1QFE
Msdtcprx.dll2001.12.4720.3316472,57630-Mar-200915:24SP1SP1QFE
Msdtcstp.dll2001.12.4720.331698,30430-Mar-200915:24SP1SP1QFE
Msdtctm.dll2001.12.4720.33161,053,69630-Mar-200915:24SP1SP1QFE
Msdtcuiu.dll2001.12.4720.3316166,40030-Mar-200915:24SP1SP1QFE
Mtxclu.dll2001.12.4720.331680,38430-Mar-200915:24SP1SP1QFE
Mtxoci.dll2001.12.4720.3316111,61630-Mar-200915:24SP1SP1QFE
Xolehlp.dll2001.12.4720.331610,75230-Mar-200915:24SP1SP1QFE
Msdtc.exe2001.12.4720.44856,14430-Mar-200911:35SP2SP2QFE
Msdtclog.dll2001.12.4720.448576,28830-Mar-200915:45SP2SP2QFE
Msdtcprx.dll2001.12.4720.4485470,01630-Mar-200915:45SP2SP2QFE
Msdtcstp.dll2001.12.4720.448598,30430-Mar-200915:45SP2SP2QFE
Msdtctm.dll2001.12.4720.44851,054,20830-Mar-200915:45SP2SP2QFE
Msdtcuiu.dll2001.12.4720.4485167,42430-Mar-200915:45SP2SP2QFE
Mtxclu.dll2001.12.4720.448579,87230-Mar-200915:45SP2SP2QFE
Mtxoci.dll2001.12.4720.4485111,10430-Mar-200915:45SP2SP2QFE
Xolehlp.dll2001.12.4720.448510,75230-Mar-200915:45SP2SP2QFE
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Msdtc.exe2001.12.4720.33166,65630-Mar-200913:53x64SP1SP1QFE
Msdtclog.dll2001.12.4720.3316142,33630-Mar-200913:53x64SP1SP1QFE
Msdtcprx.dll2001.12.4720.3316833,02430-Mar-200913:53x64SP1SP1QFE
Msdtcstp.dll2001.12.4720.3316131,07230-Mar-200913:53x64SP1SP1QFE
Msdtctm.dll2001.12.4720.33162,158,08030-Mar-200913:53x64SP1SP1QFE
Msdtcuiu.dll2001.12.4720.3316291,84030-Mar-200913:53x64SP1SP1QFE
Mtxclu.dll2001.12.4720.3316146,94430-Mar-200913:53x64SP1SP1QFE
Mtxoci.dll2001.12.4720.3316175,10430-Mar-200913:53x64SP1SP1QFE
Xolehlp.dll2001.12.4720.331610,75230-Mar-200913:53x64SP1SP1QFE
Wmsdtcprx.dll2001.12.4720.3316472,57630-Mar-200913:53x86SP1WOW
Wmsdtcuiu.dll2001.12.4720.3316166,40030-Mar-200913:53x86SP1WOW
Wmtxclu.dll2001.12.4720.331680,38430-Mar-200913:53x86SP1WOW
Wmtxoci.dll2001.12.4720.3316111,61630-Mar-200913:53x86SP1WOW
Wxolehlp.dll2001.12.4720.331610,75230-Mar-200913:53x86SP1WOW
Msdtc.exe2001.12.4720.44856,65630-Mar-200914:02x64SP2SP2QFE
Msdtclog.dll2001.12.4720.4485142,84830-Mar-200914:02x64SP2SP2QFE
Msdtcprx.dll2001.12.4720.4485835,07230-Mar-200914:02x64SP2SP2QFE
Msdtcstp.dll2001.12.4720.4485131,07230-Mar-200914:02x64SP2SP2QFE
Msdtctm.dll2001.12.4720.44852,158,08030-Mar-200914:02x64SP2SP2QFE
Msdtcuiu.dll2001.12.4720.4485290,81630-Mar-200914:02x64SP2SP2QFE
Mtxclu.dll2001.12.4720.4485146,94430-Mar-200914:02x64SP2SP2QFE
Mtxoci.dll2001.12.4720.4485175,10430-Mar-200914:02x64SP2SP2QFE
Xolehlp.dll2001.12.4720.448510,75230-Mar-200914:02x64SP2SP2QFE
Wmsdtcprx.dll2001.12.4720.4485470,01630-Mar-200914:02x86SP2WOW
Wmsdtcuiu.dll2001.12.4720.4485167,42430-Mar-200914:02x86SP2WOW
Wmtxclu.dll2001.12.4720.448579,87230-Mar-200914:02x86SP2WOW
Wmtxoci.dll2001.12.4720.4485111,10430-Mar-200914:02x86SP2WOW
Wxolehlp.dll2001.12.4720.448510,75230-Mar-200914:02x86SP2WOW
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Msdtc.exe2001.12.4720.33169,72830-Mar-200913:53IA-64SP1SP1QFE
Msdtclog.dll2001.12.4720.3316231,93630-Mar-200913:53IA-64SP1SP1QFE
Msdtcprx.dll2001.12.4720.33161,338,88030-Mar-200913:53IA-64SP1SP1QFE
Msdtcstp.dll2001.12.4720.3316241,15230-Mar-200913:53IA-64SP1SP1QFE
Msdtctm.dll2001.12.4720.33163,214,33630-Mar-200913:53IA-64SP1SP1QFE
Msdtcuiu.dll2001.12.4720.3316485,88830-Mar-200913:53IA-64SP1SP1QFE
Mtxclu.dll2001.12.4720.3316210,94430-Mar-200913:53IA-64SP1SP1QFE
Mtxoci.dll2001.12.4720.3316322,04830-Mar-200913:53IA-64SP1SP1QFE
X olehlp.dll2001.12.4720.331618,43230-Mar-200913:53IA-64SP1SP1QFE
Wmsdtcprx.dll2001.12.4720.3316472,57630-Mar-200913:53x86SP1WOW
Wmsdtcuiu.dll2001.12.4720.3316166,40030-Mar-200913:53x86SP1WOW
Wmtxclu.dll2001.12.4720.331680,38430-Mar-200913:53x86SP1WOW
Wmtxoci.dll2001.12.4720.3316111,61630-Mar-200913:53x86SP1WOW
Wxolehlp.dll2001.12.4720.331610,75230-Mar-200913:53x86SP1WOW
Msdtc.exe2001.12.4720.44859,72830-Mar-200913:59IA-64SP2SP2QFE
Msdtclog.dll2001.12.4720.4485232,96030-Mar-200913:59IA-64SP2SP2QFE
Msdtcprx.dll2001.12.4720.44851,340,92830-Mar-200913:59IA-64SP2SP2QFE
Msdtcstp.dll2001.12.4720.4485241,15230-Mar-200913:59IA-64SP2SP2QFE
Msdtctm.dll2001.12.4720.44853,216,38430-Mar-200913:59IA-64SP2SP2QFE
Msdtcuiu.dll2001.12.4720.4485486,91230-Mar-200913:59IA-64SP2SP2QFE
Mtxclu.dll2001.12.4720.4485210,94430-Mar-200913:59IA-64SP2SP2QFE
Mtxoci.dll2001.12.4720.4485322,04830-Mar-200913:59IA-64SP2SP2QFE
Xolehlp.dll2001.12.4720.448518,43230-Mar-200913:59IA-64SP2SP2QFE
Wmsdtcprx.dll2001.12.4720.4485470,01630-Mar-200913:59x86SP2WOW
Wmsdtcuiu.dll2001.12.4720.4485167,42430-Mar-200913:59x86SP2WOW
Wmtxclu.dll2001.12.4720.448579,87230-Mar-200913:59x86SP2WOW
Wmtxoci.dll2001.12.4720.4485111,10430-Mar-200913:59x86SP2WOW
Wxolehlp.dll2001.12.4720.448510,75230-Mar-200913:59x86SP2WOW

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about TIP transactions, visit the following Microsoft Web site:For more information about how to configure MS DTC on a Windows Server 2003 Cluster, click the following article number to view the article in the Microsoft Knowledge Base:

301600 How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster


For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbsurveynew, kbqfe, kbhotfixserver, kb

↑ Back to the top

Article Info
Article ID : 958013
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 163