Microsoft KB Archive/307830

= Memory Leak When You Gather Performance Counter Information on a Remote Server =

Article ID: 307830

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2

-



This article was previously published under Q307830



SYMPTOMS
A custom performance-monitoring program that obtains thread-count counter information on a remote server by using Performance Data Helper functions may leak memory. The leak occurs not only in the custom client program but also in the Regsvc.exe process on the remote server.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

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.   Date         Time   Version        Size       File name --  28-Jan-2002  19:00  2000.2.3491.0    166,160  Catsrv.dll 28-Jan-2002 19:00  2000.2.3491.0    589,072  Catsrvut.dll 28-Jan-2002 19:00  2000.2.3491.0     96,016  Clbcatex.dll 28-Jan-2002 19:00  2000.2.3491.0    509,712  Clbcatq.dll 28-Jan-2002 19:00  2000.2.3491.0     37,648  Colbact.dll 28-Jan-2002 19:00  2000.2.3491.0    194,832  Comadmin.dll 28-Jan-2002 19:00  2000.2.3491.0  1,435,408  Comsvcs.dll 28-Jan-2002 19:00  2000.2.3491.0    625,936  Comuid.dll 28-Jan-2002 18:10  2000.2.3491.0    831,040  Dtcsetup.exe 28-Jan-2002 19:00  2000.2.3491.0    236,816  Es.dll 20-Mar-2002 21:05  5.0.2195.4750     20,752  Iasperf.dll 28-Jan-2002 19:00  2000.2.3491.0     88,848  Msdtclog.dll 23-Mar-2002 20:33  2000.2.3491.0    698,640  Msdtcprx.dll 28-Jan-2002 19:00  2000.2.3491.0  1,124,112  Msdtctm.dll 28-Jan-2002 19:00  2000.2.3491.0    146,192  Msdtcui.dll 28-Jan-2002 18:25  2000.2.3491.0    151,312  Mtstocom.exe 28-Jan-2002 19:00  2000.2.3491.0     52,496  Mtxclu.dll 28-Jan-2002 19:00  2000.2.3491.0     23,824  Mtxdm.dll 28-Jan-2002 19:00  2000.2.3491.0    106,256  Mtxoci.dll 28-Jan-2002 19:00  5.0.2195.4735    940,816  Ole32.dll 20-Mar-2002 21:05  5.0.2195.4952    152,848  Pdh.dll 28-Jan-2002 19:00  5.0.2195.4800    428,304  Rpcrt4.dll 28-Jan-2002 19:00  5.0.2195.4840    186,128  Rpcss.dll 28-Jan-2002 19:00  2000.2.3491.0    392,464  Txfaux.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

Keywords: kbbug kbfix kbqfe kbwin2000sp3fix kbhotfixserver KB307830

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.