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.
- 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.
- A NonRoot COM+ component shutdown causes a transaction to end before the Tx Timeout expires.
- The xa_rollback function call is not always sent when you perform a rollback with an Oracle-linked server from Microsoft SQL Server.
- 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 {clsid} to the user userAccount SID (sid). This security permission can be modified using the Component Services administrative tool. - 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
- 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. - 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.
- 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
- 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
Additionally, the following event is logged in the System log:
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 shpEvent 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. - 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
- 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.
- 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).
- You may experience heap corruption in RPCSS when a low-memory condition or an out-of-memory condition exists.
- 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.
- COM+ operations and DTC operations may take a long time to run during the commit phase of a transaction.
- A memory leak may occur in Ole32.dll when you use a proxy dynamic link library or a stub dynamic link library.
- 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.
- COM and DCOM object activation through a session moniker fails in a remote console session in Windows XP.