FIX: Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 28

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 28. 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:

829211 (http://support.microsoft.com/kb/829211/ ) MiniJIT allows just-in-time activated COM+ components to join the context of caller
828743 (http://support.microsoft.com/kb/828743/ ) FIX: You receive an access violation when you try to queue work on a thread that has exited
829212 (http://support.microsoft.com/kb/829212/ ) A memory leak occurs in COM+ when you try to marshal user-defined types from one thread to another
829202 (http://support.microsoft.com/kb/829202/ ) The IRunningObjectTable::EnumRunning method returns a null IEnumMoniker variable
829201 (http://support.microsoft.com/kb/829201/ ) The Dllhost.exe process crashes if you pass by value a user-defined type that contains a BSTR type
829181 (http://support.microsoft.com/kb/829181/ ) The Component Services MMC snap-in may crash when it tries to import COM+ components that are already registered
829180 (http://support.microsoft.com/kb/829180/ ) A race condition in the COM+ Event System can cause the detection of a corrupted IEventSubscription object
829179 (http://support.microsoft.com/kb/829179/ ) The Microsoft Distributed Transaction Service crashes when DTS is used to transfer data between SQL Server and Oracle Database
829178 (http://support.microsoft.com/kb/829178/ ) Microsoft Distributed Transaction Service crash can cause the loss of COM+ Queued Component messages
829159 (http://support.microsoft.com/kb/829159/ ) FIX: The Mtxoci.dll module of the MSDTC XA Transaction Manager may leak threads

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

Msdtcprx.dll leaks a lock in the session list and causes Msdtc.exe to stop responding (hang).
Mtxoci.dll blocks new transactions in the Microsoft Distributed Transaction Service (MSDTC) because Mtxoci.dll waiting on an abort request.

To enable this hotfix, you must manually enter the QueueOciWork registry entry. To do this, following these steps:
1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:
  HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type QueueOciWork, and then press ENTER.
5. On the Edit menu, click Modify.
6. Click Decimal, type 1 in the Value data box, and then click OK.
Queued Components (QCs) cannot process messages.
Comsvcs.dll causes a Microsoft Visual Basic .NET console application to stop responding (hang).
A race condition causes COM Load Balancing to activate an object on the wrong server.
The CTransactionVoter class incorrectly ignores a Transaction Abort notification.
In-doubt transactions are not correctly removed from the in-doubt transactions list.

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 4 (SP4) 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. The following Microsoft Knowledge Base article contains a list of the problems that are fixed in the previous rollup package:

822618 (http://support.microsoft.com/kb/822618/ ) INFO: Availability of Windows 2000 Post-Service Pack 4 COM+ Hotfix Rollup Package 27

Registry information

You do not have to create or to modify any registry keys to open 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 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
   ------------------------------------------------------------
   26-Jan-2004  18:21  2000.2.3510.0      169,232  Catsrv.dll
   26-Jan-2004  18:21  2000.2.3510.0      595,728  Catsrvut.dll
   26-Jan-2004  18:21  2000.2.3510.0       96,528  Clbcatex.dll
   26-Jan-2004  18:21  2000.2.3510.0      552,720  Clbcatq.dll
   26-Jan-2004  18:21  2000.2.3510.0       41,744  Colbact.dll
   26-Jan-2004  18:21  2000.2.3510.0      198,416  Comadmin.dll
   26-Jan-2004  18:21  2000.2.3510.0       97,552  Comrepl.dll
   26-Jan-2004  18:21  2000.2.3421.351    342,288  Comsetup.dll
   26-Jan-2004  18:21  2000.2.3510.0    1,467,664  Comsvcs.dll
   26-Jan-2004  18:21  2000.2.3510.0      625,936  Comuid.dll
   23-Jan-2004  00:04  2000.2.3510.0    1,812,968  Dtcsetup.exe
   26-Jan-2004  18:21  2000.2.3510.0      239,888  Es.dll
   26-Jan-2004  18:21  2000.2.3510.0       96,016  Msdtclog.dll
   26-Jan-2004  18:21  2000.2.3510.0      716,560  Msdtcprx.dll
   26-Jan-2004  18:21  2000.2.3510.0    1,139,984  Msdtctm.dll
   26-Jan-2004  18:21  2000.2.3510.0      153,872  Msdtcui.dll
   23-Jan-2004  00:20  2000.2.3510.0      155,408  Mtstocom.exe
   26-Jan-2004  18:21  2000.2.3510.0       52,496  Mtxclu.dll
   26-Jan-2004  18:21  2000.2.3510.0       26,896  Mtxdm.dll
   26-Jan-2004  18:21  2000.2.3510.0       35,600  Mtxlegih.dll
   26-Jan-2004  18:21  2000.2.3510.0      120,592  Mtxoci.dll
   26-Jan-2004  18:21  5.0.2195.6892      953,616  Ole32.dll
   26-Jan-2004  18:21  5.0.2195.6890      435,472  Rpcrt4.dll
   26-Jan-2004  18:21  5.0.2195.6892      211,216  Rpcss.dll
   26-Jan-2004  18:21  2000.2.3510.0      398,608  Txfaux.dll
   26-Jan-2004  18:21  2000.2.3510.0       18,704  Xolehlp.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

828741 (http://support.microsoft.com/kb/828741/ ) MS04-012: Cumulative Update for Microsoft RPC/DCOM

Back to the top