INFO: Availability of Windows 2000 Post-Service Pack 4 COM+ Hotfix Rollup Package 27

View products that this article applies to.

SUMMARY

This article lists the Microsoft COM+ bugs that are fixed in the Microsoft Windows 2000 Post-Service Pack 4 (SP4) COM+ 1.0 rollup package 27. Each package contains all the fixes that were released in the previous Windows 2000 COM+ 1.0 rollup packages.

Back to the top

Issues That Are Fixed in the Hotfix Package

The following issues are fixed in this hotfix package:

813714 (http://support.microsoft.com/kb/813714/ ) Queued COM+ Application Cannot Start if the First Retry Queue Has Been Deleted
819575 (http://support.microsoft.com/kb/819575/ ) Access Violation May Occur in CoDisconnectObject
819978 (http://support.microsoft.com/kb/819978/ ) Replication Tools Fail When a COM+ Application Proxy Is Installed on the Source Computer
819989 (http://support.microsoft.com/kb/819989/ ) COM+ Services DLL Cannot Load Because Allocation of Thread Local Storage Fails
819995 (http://support.microsoft.com/kb/819995/ ) Valid Subscribers May No Longer Receive All Events When One Unregisters Its Subscription
821457 (http://support.microsoft.com/kb/821457/ ) FIX: COM Applications May Cause a Kernel-Mode Memory Leak
822473 (http://support.microsoft.com/kb/822473/ ) "MSDTC Is Unavailable" Error When a Stand-Alone Instance of SQL Server Is in a Cluster Environment
822544 (http://support.microsoft.com/kb/822544/ ) COM Components That Are Configured Correctly in a COM+ Server Application Can Be Loaded in the Client Process

The following issues are also fixed in this hotfix package but were not previously documented in a Microsoft Knowledge Base article:

An OLE32 exception occurs during a call to the CoCreateInstance function.
COM+ should store user security identifiers (SIDs) instead of user names in string format.
There is a security vulnerability in the RPCSS memory management model.
A race condition exists during startup or during shutdown of the multithreaded apartment (MTA).
The COM+ system tracker does not reset statistics for idle components.
A custom DLL is not overwritten in the COMPLUS\{GUID} folder if the application proxy is upgraded.
Microsoft Distributed Transaction Coordinator (MSDTC) XA thread pool cleanup may lead to a fake Windows Script Host (WSH) script error.
An RPCSS exception occurs if the computer name is greater than 16 characters
A race condition occurs between the Microsoft .NET Framework common language runtime garbage collector and ordinary COM+ transaction Commit operations.
Dead Letter Queue Listener for a COM+ queued component cannot be started under Message Queuing (also known as MSMQ) workgroup installation.
A first chance access violation rarely occurs when you debug a COM+ application.
The RPCSS memory management model uses an incorrect pinging message format.
COM+ may not allow administrators to configure certain valid EOAC_ values

Back to the top

MORE INFORMATION

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

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

http://support.microsoft.com/contactus/?ws=support (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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To install this hotfix, you must have Windows 2000 Service Pack 3 or later installed on your computer.

Restart Information

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:

817082 (http://support.microsoft.com/kb/817082/ ) INFO: Availability of Windows 2000 Post-Service Pack 3 COM+ Hotfix Rollup Package 26
Note Version 3504 is the same version as Microsoft Windows 2000 SP4.

Registry Information

You do not have to create or modify any registry keys to activate any hotfixes that are contained in this package.

Hotfix File Information

This hotfix contains only those files that you must have to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix 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
   ----------------------------------------------------------
   03-Jul-2003  17:54  3.0.0.3505       169,744  Catsrv.dll
   03-Jul-2003  18:39  3.0.0.3505       595,728  Catsrvut.dll
   03-Jul-2003  18:39  3.0.0.3505        96,528  Clbcatex.dll
   03-Jul-2003  18:39  3.0.0.3505       513,808  Clbcatq.dll
   03-Jul-2003  17:54  3.0.0.3505        41,232  Colbact.dll
   03-Jul-2003  18:39  3.0.0.3505       198,416  Comadmin.dll
   03-Jul-2003  18:39  3.0.0.3505        97,552  Comrepl.dll
   03-Jul-2003  18:39  3.0.0.3421       342,288  Comsetup.dll
   03-Jul-2003  18:39  3.0.0.3505     1,458,960  Comsvcs.dll
   03-Jul-2003  18:39  3.0.0.3505       625,936  Comuid.dll
   03-Jul-2003  17:44  3.0.0.3505         9,760  Dtcsetup.cat
   03-Jul-2003  17:44  5.0.522.0      1,809,760  Dtcsetup.exe
   15-Nov-2001  16:27  5.0.522.0          5,149  Empty.cat
   03-Jul-2003  18:39  3.0.0.3505       239,888  Es.dll
   03-Jul-2003  18:39  3.0.0.3505        96,016  Msdtclog.dll
   03-Jul-2003  18:39  3.0.0.3505       715,024  Msdtcprx.dll
   03-Jul-2003  18:39  3.0.0.3505     1,138,960  Msdtctm.dll
   03-Jul-2003  18:39  3.0.0.3505       153,872  Msdtcui.dll
   03-Jul-2003  17:55  3.0.0.3505       155,408  Mtstocom.exe
   03-Jul-2003  18:39  3.0.0.3505        52,496  Mtxclu.dll
   03-Jul-2003  18:39  3.0.0.3505        26,896  Mtxdm.dll
   03-Jul-2003  18:39  3.0.0.3505       120,592  Mtxoci.dll
   03-Jul-2003  18:39  5.0.2195.6768    944,912  Ole32.dll
   03-Jul-2003  18:39  5.0.2195.6753    432,400  Rpcrt4.dll
   03-Jul-2003  18:39  5.0.2195.6768    188,688  Rpcss.dll
   07-Jul-2003  10:48  5.3.18.5           6,656  Spmsg.dll
   07-Jul-2003  10:48  5.3.18.5         100,352  Spuninst.exe
   03-Jul-2003  18:39  3.0.0.3505       397,584  Txfaux.dll

Back to the top

REFERENCES

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:

824684 (http://support.microsoft.com/kb/824684/ ) Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Back to the top