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.

A memory leak occurs when an application or service calls the DTCGetTransactionManagerEx function for each transaction in Windows Server 2008 or in Windows Vista


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 or Windows Vista.
  • You run an application or service that calls the DTCGetTransactionManagerEx function for each transaction.
In this scenario, the memory usages of the application or service and of the Msdtc.exe process keep increasing.

Note You can verify this increasing memory usage in Performance Monitor by monitoring the private bytes of the application or service and the private bytes of the Msdtc.exe process.

↑ Back to the top


Cause

This issue occurs because of a memory leak in the Microsoft Distributed Transaction Coordinator (MSDTC) service when the application calls the DTCGetTransactionManagerEx function many times.

↑ 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 the problem described in this article. 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

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    1.
    22xxx
    Windows Vista and Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.6932.22479562,17601-Sep-201021:05x86
Xolehlp.dll2001.12.6932.2247938,91201-Sep-201021:07x86
Msdtctm.dll2001.12.6932.224791,054,72001-Sep-201021:05x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.6932.22479729,08801-Sep-201020:26x64
Xolehlp.dll2001.12.6932.2247948,64001-Sep-201020:28x64
Msdtctm.dll2001.12.6932.224791,499,64801-Sep-201020:26x64
Msdtcprx.dll2001.12.6932.22479562,17601-Sep-201021:05x86
Xolehlp.dll2001.12.6932.2247938,91201-Sep-201021:07x86
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.6932.224791,629,18401-Sep-201020:36IA-64
Xolehlp.dll2001.12.6932.22479100,35201-Sep-201020:39IA-64
Msdtctm.dll2001.12.6932.224792,837,50401-Sep-201020:36IA-64
Msdtcprx.dll2001.12.6932.22479562,17601-Sep-201021:05x86
Xolehlp.dll2001.12.6932.2247938,91201-Sep-201021:07x86

↑ Back to the top


Workaround

To work around this issue, call the DTCGetTransactionManagerEx function only one time to handle all transactions. To do this, store the returned interface pointer in a global variable, and then reuse it for each transaction. This global variable can be released before the application or service ends.

↑ 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 the DtcGetTransactionManagerEx function, visit the following Microsoft website:For more information about the MSDTC service, visit the following Microsoft website:For more information about software update terminology, 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

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size3,078
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameX86_0f1cc502af2546a7626b59dbbf6f0b17_31bf3856ad364e35_6.0.6002.22479_none_d3af4a29ecaf56f3.manifest
File versionNot applicable
File size702
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameX86_b6fb42383c19bdd4ae545d09aba67571_31bf3856ad364e35_6.0.6002.22479_none_a5097f4d5b9d537d.manifest
File versionNot applicable
File size706
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameX86_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.0.6002.22479_none_4f205af3cfc25425.manifest
File versionNot applicable
File size15,959
Date (UTC)01-Sep-2010
Time (UTC)21:30
PlatformNot applicable
File nameX86_microsoft-windows-com-dtc-runtime-tm_31bf3856ad364e35_6.0.6002.22479_none_9bc5fb5f31346e00.manifest
File versionNot applicable
File size70,177
Date (UTC)01-Sep-2010
Time (UTC)21:31
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_70cc8f350f660c282afe42bfa0d55dee_31bf3856ad364e35_6.0.6002.22479_none_e0de35a17cf9be3c.manifest
File versionNot applicable
File size1,054
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameAmd64_aedb1e23b3f15e74e80296ed6dd50227_31bf3856ad364e35_6.0.6002.22479_none_c2bf0f57ed0bbe3a.manifest
File versionNot applicable
File size710
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameAmd64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.0.6002.22479_none_ab3ef677881fc55b.manifest
File versionNot applicable
File size15,993
Date (UTC)01-Sep-2010
Time (UTC)20:48
PlatformNot applicable
File nameAmd64_microsoft-windows-com-dtc-runtime-tm_31bf3856ad364e35_6.0.6002.22479_none_f7e496e2e991df36.manifest
File versionNot applicable
File size70,217
Date (UTC)01-Sep-2010
Time (UTC)20:49
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,102
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameWow64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.0.6002.22479_none_b593a0c9bc808756.manifest
File versionNot applicable
File size15,781
Date (UTC)01-Sep-2010
Time (UTC)21:13
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_aca41e558773a27eca2cf32a501bb096_31bf3856ad364e35_6.0.6002.22479_none_45958a7830aad4dc.manifest
File versionNot applicable
File size708
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameIa64_baa233c9bd018a31fa845b8ab5985453_31bf3856ad364e35_6.0.6002.22479_none_4e81f0ea60059179.manifest
File versionNot applicable
File size1,052
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameIa64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.0.6002.22479_none_4f21fee9cfc05d21.manifest
File versionNot applicable
File size15,976
Date (UTC)01-Sep-2010
Time (UTC)20:55
PlatformNot applicable
File nameIa64_microsoft-windows-com-dtc-runtime-tm_31bf3856ad364e35_6.0.6002.22479_none_9bc79f55313276fc.manifest
File versionNot applicable
File size70,197
Date (UTC)01-Sep-2010
Time (UTC)20:56
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,256
Date (UTC)02-Sep-2010
Time (UTC)09:11
PlatformNot applicable
File nameWow64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.0.6002.22479_none_b593a0c9bc808756.manifest
File versionNot applicable
File size15,781
Date (UTC)01-Sep-2010
Time (UTC)21:13
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2385261
Revision : 2
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 307