This article lists the Microsoft COM+ bugs that are fixed in the Microsoft Windows 2000 Post-Service Pack 3 (SP3) COM+ 1.0 rollup package 26. Each package contains all the fixes that were released in the previous Windows 2000 COM+ 1.0 rollup packages.
Issues That Are Fixed in the Hotfix Package
The following issues are also fixed in this hotfix package but were not previously documented in a Microsoft Knowledge Base article:
- The Microsoft Distributed Transaction Coordinator (MSDTC) is vulnerable on MSDTC connection manager APIs.
- The MSDTC registry key is exposed to everyone when MSDTC is upgraded from Microsoft Windows NT 4 to Microsoft Windows Server 2003.
- A memory leak occurs when you use the Global Interface Table (GIT) from different threads.
- Failfast code gets in an endless loop.
- MSDTC shuts down after the timer object disappears.
- The DCOM client receives an RPC_E_DISCONNECTED error message when the client loses its callback connection.
- "MTXOCI Internal Error" event log message appears when the process is shutting down.
- The ProductVersion:FileVersion property of the Japanese version of Catsrvut.dll is different from the ProductVersion:FileVersion property of the English (United States) version of Catsrvut.dll.
Service Pack Information
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:
How to obtain the latest Windows 2000 service pack
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix is not replaced by any later hotfix.
Resolutions for problems that are fixed in the Windows 2000 COM+ 1.0 rollup packages are cumulative. This is a list of Microsoft Knowledge Base articles for the previous rollup packages after Windows 2000 Service Pack 3:
- QFE20.2, version:3497 (same as SP3)
- QFE21 Version:3498
- QFE22 Version:3499
- QFE23 Version:3500
- QFE24 Version:3501
- QFE25 Version:3503
- QFE26 Version:3504
You do not have to create or modify any registry keys to activate any hotfixes that are contained in this package.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was first corrected in Windows 2000 Service Pack 4.
For additional information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates
Article ID: 817082 - Last Review: February 27, 2014 - Revision: 2.1
- Microsoft COM+ 1.0, when used with:
- Microsoft Windows 2000 Service Pack 4
|kbnosurvey kbarchive kbbug kbfix kbwin2000presp4fix kbqfe kbhotfixrollup kbhotfixserver KB817082|