FIX: Memory Leak When Calling Between Configured Components

This article has been archived. It is offered "as is" and will no longer be updated.
A memory leak can occur when you make calls between components that reside in different contexts in a Component Services application. The memory leak occurs only when the call is made through the IDispatch interface.
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 theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.The English version of this fix should have the following file attributes or later:
   Date        Time    Version         Size      Filename   ----------------------------------------------------------   01/05/2001  06:01p  2000.2.3468.2    165,648  catsrv.dll   01/05/2001  05:50p  2000.2.3468.2    570,640  catsrvut.dll   01/05/2001  06:01p  2000.2.3468.2     95,504  clbcatex.dll   01/05/2001  06:01p  2000.2.3468.2    508,176  clbcatq.dll   01/05/2001  06:01p  2000.2.3468.2     37,648  colbact.dll   01/05/2001  05:50p  2000.2.3468.2  1,398,544  comsvcs.dll   01/05/2001  05:00p  2000.2.3468.2    805,120  dtcsetup.exe   01/05/2001  06:01p  2000.2.3468.2    234,256  es.dll   01/05/2001  05:50p  2000.2.3468.2    641,296  msdtcprx.dll   01/05/2001  05:50p  2000.2.3468.2  1,120,528  msdtctm.dll   01/05/2001  06:01p  2000.2.3468.2     52,496  mtxclu.dll   01/05/2001  06:01p  2000.2.3468.2     23,824  mtxdm.dll   01/05/2001  05:50p  2000.2.3468.2    104,208  mtxoci.dll   01/05/2001  06:01p  5.0.2195.2815    939,792  ole32.dll   01/05/2001  06:01p  5.0.2195.2815    184,592  rpcss.dll   01/05/2001  05:50p  2000.2.3468.2    382,736  txfaux.dll				

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 2.
compluskb com+

Article ID: 265379 - Last Review: 01/10/2015 12:40:27 - Revision: 6.0

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbgraphxlinkcritical KB265379