Microsoft KB Archive/895200

= Availability of Windows XP COM+ Hotfix Rollup Package 9 =

Article ID: 895200

Article Last Modified on 12/5/2007

-

APPLIES TO

 Microsoft COM+ 1.5, when used with:  Microsoft Windows XP Professional

 Microsoft Windows XP Home Edition

 Microsoft Windows XP Media Center Edition 2002

 Microsoft Windows XP Embedded</li></ul> </li></ul>

-

<div class="notice_section">

<div class="notice_section">

ARTICLE CONTENTS

 * SUMMARY
 * Issues that are fixed in this hotfix rollup package
 * MORE INFORMATION
 * Hotfix rollup package information
 * Prerequisites
 * Restart information
 * Hotfix replacement information
 * Registry information
 * Hotfix file information
 * REFERENCES

<div class="summary_section">

SUMMARY
This article lists the COM+ bugs that are fixed in the Windows XP post-Service Pack 2 (SP2) COM+ Hotfix Rollup Package 9. Each package contains all the fixes that were released in the earlier Windows XP post-Service Pack 2 (SP2) COM+ hotfix rollup packages.

back to the top

Issues that are fixed in this hotfix rollup package
The following issues are also fixed in this hotfix rollup package. These issues were not documented in an earlier Microsoft Knowledge Base article:  When you call the xa_open function in a client process to open an XA connection, a memory leak occurs. This problem occurs when Microsoft Distributed Transaction Coordinator (DTC) is not online.</li> When you call the xa_commit function in a client process to perform a commit, a memory leak occurs. This problem occurs when the exchange identification (XID) is not valid.</li> A NonRoot COM+ component shutdown causes a transaction to end before the Tx Timeout expires.</li> The xa_rollback function call is not always sent when you perform a rollback with an Oracle-linked server from Microsoft SQL Server.</li>  When you try call a remote COM+ application, an event that is similar to the following is logged in the Application log on the client computer: Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10016

Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID { } to the user  SID. This security permission can be modified using the Component Services administrative tool. </li> On a computer that is running Microsoft Windows XP with SP2 installed, when you programmatically try to access a remote computer that is running Microsoft Internet Information Services (IIS) by using the IIS COM API, you cannot connect to the remote IIS service. When this problem occurs, you receive the following error message:

A secure communications channel could not be established with the target server. MD_ERROR_SECURE_CHANNEL_FAILURE 800CC806L -2146646010

</li> You experience a memory leak in the rpcss!RegisterAuthInfoIfNecessary process if Microsoft Remote Procedure Call Server Service (RPCSS) services are not registered. This problem occurs when you start a local COM server.

Note This problem may occur in Microsoft Windows XP Embedded. In Microsoft Windows XP Embedded, you can create an image without using RPCSS services.</li> Unhandled access violation (C0000005) COM calls may cause the CoUninitialize function to be repeatedly called. When this problem occurs, the COM+ application stops responding (hangs), and high CPU usage occurs.</li> If you call the Dispose method on a serviced component while the component is in a transaction state, a ComException (CONTEXT_E_ABORTING) is thrown. When this problem occurs, you receive the following error message:

You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. 8004e003 -2147164157

</li>  If your Windows XP SP2-base computer has a computer name that contains multibyte characters, and you try to perform a distributed transaction, the following event is logged in the Application log: Event Type: Error

Event Source: COM+

Event ID: 4863

Description:

TransactionManager->GetWhereabouts failed. If Distributed Transaction Coordinator is configured to use remote host to coordinate transactions, it is likely that remote host cannot be contacted. You can configure MSDTC to use local coordinator by clicking MSDTC toolbar button in Component Services MMC snap-in. Since further execution is impossible at this time, server process has been terminated. Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235} Server Application Instance ID: {914FC2C1-5A8B-452D-913D-C847292B6E36} Server Application Name: System Application Error Code = 0x8007007a : The data area passed to a system call is too small. COM+ Services Internals Information: File: d:\qxp_slp\com\com1x\src\comsvcs\txprop\dtcinfo.cpp, Line: 164 Comsvcs.dll file version: ENU 2001.12.4414.258 shp Additionally, the following event is logged in the System log: Event Type: Error

Event Source: Service Control Manager

Event ID: 7031

Description:

the COM+ System Application terminated unexpectedly. It has done this 1 time, the following corrective action will be taken in 1000 milliseconds:Restart the service. </li> When you call the CoEnterServiceDomain function in a context that includes an aborted transaction, the Services Without Components (SWC) infrastructure is left in an unrecoverable and inconsistent state. When this problem occurs, you receive the following error message:

There is no MTS object context CONTEXT_E_NOCONTEXT 8004E004 -2147164156

</li> When Microsoft Distributed Transaction Coordinator (DTC) is disabled on startup, you cannot use DCOM Config to change properties. When you try to change properties, the Properties option is not available.</li> A COM+ application stops responding at startup because a deadlock occurs with the Service Control Manager (SCM). This problem occurs when the COM+ application does not have dependencies set up for either the COM+ System Application or the Distributed Transaction Coordinator (DTC).</li> You may experience heap corruption in RPCSS when a low-memory condition or an out-of-memory condition exists.</li> If you call the GetClipboardData function to retrieve the contents of the clipboard, and the clipboard uses the OwnerLink data format, the function returns null.</li> <li>COM+ operations and DTC operations may take a long time to run during the commit phase of a transaction.</li> <li>A memory leak may occur in Ole32.dll when you use a proxy dynamic link library or a stub dynamic link library.</li> <li>This hotfix rollup package adds the COMBND_SERVER_LOCALITY option for the IRpcOptions::Query Windows Management Instrumentation (WMI) method. WMI uses this option to determine whether a WMI connection is local or remote.</li> <li>COM and DCOM object activation through a session moniker fails in a remote console session in Windows XP.</li></ul>

The following issues are also fixed in this hotfix rollup package. These issues are documented in Microsoft Knowledge Base articles. <ul> <li>Issue 1

312960 Cannot set a fixed endpoint for a COM+ application

</li> <li>Issue 2

819978 Replication tools fail when a COM+ application proxy is installed on the source computer

</li> <li>Issue 3

819575 Access violation may occur in CoDisconnectObject

</li></ul>

<div class="summary_section">

back to the top

<div class="moreinformation_section">

Hotfix rollup package information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix rollup package, you must be running Microsoft Windows XP with SP2. For more 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

back to the top

Restart information
You must restart your computer after you apply this hotfix rollup package.

back to the top

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

back to the top

Hotfix file information
The English version of this hotfix rollup package 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.

Windows XP, 32-bit versions
<pre class="fixed_text">  Date         Time   Version          Size       File name 09-Mar-2005 17:24  2001.12.4414.55    225,280  Catsrv.dll 09-Mar-2005 17:24  2001.12.4414.55    584,192  Catsrvut.dll 09-Mar-2005 17:24  2001.12.4414.55    110,080  Clbcatex.dll 09-Mar-2005 17:24  2001.12.4414.55    499,712  Clbcatq.dll 09-Mar-2005 17:24  2001.12.4414.55     64,000  Colbact.dll 09-Mar-2005 17:24  2001.12.4414.55    187,904  Comadmin.dll 09-Mar-2005 00:13  2001.12.4414.55      8,192  Comrepl.exe 09-Mar-2005 17:24  2001.12.4414.55  1,180,160  Comsvcs.dll 09-Mar-2005 17:24  2001.12.4414.55    499,200  Comuid.dll 09-Mar-2005 17:24  2001.12.4414.55    227,328  Es.dll 09-Mar-2005 00:13  2001.12.4414.55      6,656  Migregdb.exe 09-Mar-2005 17:24  2001.12.4414.55    368,128  Msdtcprx.dll 09-Mar-2005 17:24  2001.12.4414.55    978,432  Msdtctm.dll 09-Mar-2005 17:24  2001.12.4414.55    150,528  Msdtcuiu.dll 09-Mar-2005 17:24  2001.12.4414.55     64,512  Mtxclu.dll 09-Mar-2005 17:24  2001.12.4414.55     83,456  Mtxoci.dll 09-Mar-2005 17:24  5.1.2600.1639    1,190,400  Ole32.dll 06-Mar-2004 02:16  5.1.2600.1361      535,552  Rpcrt4.dll 09-Mar-2005 17:24  5.1.2600.1639      275,456  Rpcss.dll 09-Mar-2005 17:24  2001.12.4414.55     97,280  Txflog.dll 09-Mar-2005 17:24  2001.12.4414.55     11,776  Xolehlp.dll 09-Mar-2005 17:18  2001.12.4414.30    229,888  Catsrv.dll 09-Mar-2005 17:18  2001.12.4414.30    627,712  Catsrvut.dll 09-Mar-2005 17:18  2001.12.4414.30    110,080  Clbcatex.dll 09-Mar-2005 17:18  2001.12.4414.30    501,248  Clbcatq.dll 09-Mar-2005 17:18  2001.12.4414.30     62,464  Colbact.dll 09-Mar-2005 17:18  2001.12.4414.30    195,584  Comadmin.dll 08-Mar-2005 01:29  2001.12.4414.30      9,728  Comrepl.exe 09-Mar-2005 17:18  2001.12.4414.30  1,250,816  Comsvcs.dll 09-Mar-2005 17:18  2001.12.4414.30    540,160  Comuid.dll 09-Mar-2005 17:18  2001.12.4414.30    243,200  Es.dll 08-Mar-2005 01:29  2001.12.4414.30      7,680  Migregdb.exe 09-Mar-2005 17:18  2001.12.4414.30    425,472  Msdtcprx.dll 09-Mar-2005 17:18  2001.12.4414.30    948,736  Msdtctm.dll 09-Mar-2005 17:18  2001.12.4414.30    161,280  Msdtcuiu.dll 09-Mar-2005 17:18  2001.12.4414.30     66,560  Mtxclu.dll 09-Mar-2005 17:18  2001.12.4414.30     91,136  Mtxoci.dll 09-Mar-2005 16:18  5.1.2600.2626    1,285,632  Ole32.dll 09-Mar-2005 17:18  5.1.2600.2626      396,288  Rpcss.dll 09-Mar-2005 17:18  2001.12.4414.30    101,376  Txflog.dll 09-Mar-2005 17:18  2001.12.4414.30     11,776  Xolehlp.dll 25-Feb-2005 03:53  6.1.22.4           371,936  Updspapi.dll

Windows XP, 64-bit version (IA-64)
<pre class="fixed_text">  Date         Time   Version          Size       File name     Platform --  09-Mar-2005  16:25  2001.12.4414.54    695,808  Catsrv.dll    IA-64 09-Mar-2005 16:25  2001.12.4414.54  2,127,360  Catsrvut.dll  IA-64 09-Mar-2005 16:25  2001.12.4414.54    360,960  Clbcatex.dll  IA-64 09-Mar-2005 16:25  2001.12.4414.54  1,554,432  Clbcatq.dll   IA-64 09-Mar-2005 16:25  2001.12.4414.54    202,752  Colbact.dll   IA-64 09-Mar-2005 16:25  2001.12.4414.54    478,720  Comadmin.dll  IA-64 02-Feb-2005 16:57  2001.12.4414.54     20,992  Comrepl.exe   IA-64 09-Mar-2005 16:25  2001.12.4414.54  3,594,752  Comsvcs.dll   IA-64 09-Mar-2005 16:25  2001.12.4414.54  1,817,600  Comuid.dll    IA-64 09-Mar-2005 16:25  2001.12.4414.54    742,912  Es.dll        IA-64 02-Feb-2005 16:57  2001.12.4414.54     12,800  Migregdb.exe  IA-64 09-Mar-2005 16:25  2001.12.4414.54  1,512,960  Msdtcprx.dll  IA-64 09-Mar-2005 16:25  2001.12.4414.54  3,484,160  Msdtctm.dll   IA-64 09-Mar-2005 16:25  2001.12.4414.54    513,024  Msdtcuiu.dll  IA-64 09-Mar-2005 16:25  2001.12.4414.54    194,048  Mtxclu.dll    IA-64 09-Mar-2005 16:25  2001.12.4414.54    286,720  Mtxoci.dll    IA-64 09-Mar-2005 16:25  5.1.2600.1639    4,356,608  Ole32.dll     IA-64 06-Mar-2004 01:07  5.1.2600.1361    2,317,824  Rpcrt4.dll    IA-64 09-Mar-2005 16:25  5.1.2600.1639      784,896  Rpcss.dll     IA-64 09-Mar-2005 16:25  2001.12.4414.54    346,112  Txflog.dll    IA-64 09-Mar-2005 16:25  2001.12.4414.54     27,136  Xolehlp.dll   IA-64 09-Mar-2005 16:24  2001.12.4414.55    227,328  Wes.dll       X86 09-Mar-2005 16:24  2001.12.4414.55     64,512  Wmtxclu.dll   X86 09-Mar-2005 16:24  5.1.2600.1639    1,190,400  Wole32.dll    X86 06-Mar-2004 01:16  5.1.2600.1361      509,440  Wrpcrt4.dll   X86 09-Mar-2005 16:24  2001.12.4414.55     97,280  Wtxflog.dll   X86 25-Feb-2005 02:50  6.1.22.4           639,712  Updspapi.dll  IA-64 Note This hotfix rollup package contains only those files that you must have to correct the issues that this article lists. This hotfix rollup package may not contain of all the files that you must have to fully update a product to the latest build.

back to the top

<div class="references_section">