Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Availability of the Windows XP COM+ Hotfix Rollup Package 8


View products that this article applies to.

Introduction

This article lists the COM+ bugs that are fixed in Microsoft Windows XP post-Service Pack 1 (SP1) COM+ Hotfix Rollup Package 8. Windows XP post-SP1 COM+ hotfix rollup packages are cumulative. Each package contains all the fixes that were released in the previous Windows XP post-SP1 COM+ hotfix rollup packages.

Issues that are fixed in the hotfix package

The following issues are fixed in this hotfix package but were not previously documented in a Microsoft Knowledge Base article:
  • Repeated calls to the CoInitialize function, the CoCreateInstance function, the Release function, and the CoUninitialize function on the same thread causes a memory leak.
  • Concurrent XA_RECOVER operations that are initiated on separate threads may cause the Microsoft Distributed Transaction Coordinator (DTC) proxy to stop responding.
  • A registry handle leak in the Rpcss.exe process causes profile unload failures.
  • Computer beeps continuously if an SC_SCREENSAVE event or an SC_MONITORPOWER event occurs during a pending COM call.
  • The Microsoft Distributed Transaction Coordinator (MSDTC) service quits unexpectedly, and the following event is logged:

    Event Type: Error
    Event Source: MSDTC
    Event ID: 4168
    Description:
    The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. Please contact PSS. (null) File: .\tmlufind.cpp, Line: 726


  • COM+ multithreaded apartment (MTA) thread pool logic causes increased CPU usage. Eventually, the Dllhost.exe process uses 100 percent of CPU resources.
  • A Remote Procedure Call service (RPCSS) token leak causes Client Service for NetWare (CSNW) not to close connections after clients log off.
  • Queued COM+ application stops responding during an idle shutdown.
  • When you add a Distributed File System (DFS) link to the system PATH variable, a long logon delay occurs.
  • You cannot debug COM+ components in Microsoft Visual Basic IDE in Microsoft Windows XP after you install the MS04-012 security update.
  • The MSDTC service may quit unexpectedly, and you receive the following access violation message on your Windows XP-based computer in some disabled network scenarios:
    Access violation - code c0000005
  • The MS04-012 security update may cause performance degradation because it disables catalog caching in RPCSS for COM+ class information.

↑ Back to the top


More information

Service pack information

To resolve these issues, obtain the latest service pack for Microsoft Windows XP. For additional information about how to obtain the latest service pack for Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must be running Microsoft Windows XP with Service Pack 1.

Restart information

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Bugs that are fixed in the Windows XP post-Service Pack 1 (SP1) COM+ hotfix rollup packages are cumulative. The following is a list of articles for the previous rollup packages:
  • 317926 Availability of Windows XP COM+ Hotfix Rollup Package 1
  • 330227 Availability of Windows XP COM+ Hotfix Rollup Package 5

Registry information

You do not have to create or modify any registry keys to enable any hotfixes that this package contains.

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 file attributes) 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
   --------------------------------------------------------------
   09-Jul-2004  19:54  2001.12.4414.54   225,280  Catsrv.dll       
   09-Jul-2004  19:54  2001.12.4414.54   594,944  Catsrvut.dll     
   09-Jul-2004  19:54  2001.12.4414.54   110,080  Clbcatex.dll     
   09-Jul-2004  19:54  2001.12.4414.54   499,712  Clbcatq.dll      
   09-Jul-2004  19:54  2001.12.4414.54    64,000  Colbact.dll      
   09-Jul-2004  19:54  2001.12.4414.54   187,904  Comadmin.dll     
   02-Jul-2004  20:54  2001.12.4414.54     8,192  Comrepl.exe      
   09-Jul-2004  19:54  2001.12.4414.54 1,195,520  Comsvcs.dll      
   09-Jul-2004  19:54  2001.12.4414.54   499,200  Comuid.dll       
   09-Jul-2004  19:54  2001.12.4414.54   227,328  Es.dll           
   02-Jul-2004  20:54  2001.12.4414.54     6,656  Migregdb.exe     
   09-Jul-2004  19:54  2001.12.4414.54   368,128  Msdtcprx.dll     
   09-Jul-2004  19:54  2001.12.4414.54   977,920  Msdtctm.dll      
   09-Jul-2004  19:54  2001.12.4414.54   150,528  Msdtcuiu.dll     
   09-Jul-2004  19:54  2001.12.4414.54    64,512  Mtxclu.dll       
   09-Jul-2004  19:54  2001.12.4414.54    82,432  Mtxoci.dll       
   09-Jul-2004  19:54  5.1.2600.1552   1,184,256  Ole32.dll        
   09-Jul-2004  19:54  3.50.5019.0       569,344  Oleaut32.dll     
   09-Jul-2004  19:54  5.1.2600.1551     535,552  Rpcrt4.dll       
   09-Jul-2004  19:54  5.1.2600.1550     265,728  Rpcss.dll        
   09-Jul-2004  19:54  5.1.2600.1547     681,472  Sxs.dll          
   09-Jul-2004  19:54  2001.12.4414.54    97,280  Txflog.dll       

↑ Back to the top


References

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbwinxpsp2fix, kbhotfixrollup, kbfix, kbbug, kbwinxppresp2fix, KB870769

↑ Back to the top

Article Info
Article ID : 870769
Revision : 8
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 565