Memory Leaks Occur in MTX.exe When You Track MTSEvents (318051)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you track events, such as MTSSpy in Microsoft Transaction Server (MTS), Mtsevents.dll may leak memory. This occurs for packages that have objects that are enlisted in transactions and a resource that is being managed by the Dispenser Manager. An example is objects in transactions that make Open Database Connectivity (ODBC) calls to an SQL database. The Sample Bank objects that come with MTS software development kit (SDK) display this.

Additionally, memory may leak when the number of events in the MTS event queue exceeds the maximum. By default, the number of events in the MTS event queue is 1000.

CAUSE

A CComBstr object is leaked when a resource recycle event occurs because the CComBstr member of the event object is never freed when the event object is destroyed.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

A CComVariant object is leaked when the event queue is over the maximum, and a CUserEvent object is created to report that some of the events are lost. The size of the queue can be set in the registry at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Transaction Server\Extender

You can set the size of the queue if you add or if you modify the MaxQSize REG_DWORD value.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows NT service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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 tool in Control Panel.