Article ID: 840999
Article Last Modified on 6/2/2006
APPLIES TO
- Microsoft COM+ 1.0, when used with:
- Microsoft Windows 2000 Service Pack 4
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 30. Each rollup package contains all the fixes that were released in the previous Windows 2000 COM+ 1.0 rollup packages.
Issues that are fixed in the hotfix package
The following issues were fixed in this hotfix rollup package but were not previously documented in Microsoft Knowledge Base articles:
- One or more xa_recover operations that are initiated on separate threads may cause the Distributed Transaction Coordinator (DTC) proxy to stop responding (hang).
This hotfix includes new code that serializes the xa_recover operation to avoid a race condition that may occur when more than one resource manager thread calls the xa_recover function. - A NonRoot COM+ component shutdown causes a transaction to end before the Tx Timeout expires.
This hotfix includes new code to allow the NonRoot component lifetime to extend the DLLHOST lifetime if a transaction is still active and if the component is enlisted. - The xa_rollback function call is not always sent when you perform a rollback with an Oracle-linked server from Microsoft SQL Server.
This hotfix includes new code to allow Oracle to release locks more quickly when you roll back XA transactions. - When you call the xa_open function in a client process while DTC is offline, a memory leak may occur.
This hotfix includes new code that does not allow an internal DTC object to leak when a connection to Transaction Manager is unavailable and an xa_open function call is in progress. - When you start 16-bit servers in a shared virtual DOS machine (VDM), COM uses a different VDM for every activation.
This hotfix includes new code to allow COM activation logic to automatically start 16-bit servers in a shared VDM. - Calls to the xa_commit function that use an invalid exchange identification (XID) in a client process may cause a memory leak.
This hotfix includes new code to prevent the leak of an internal DTC object when the client calls the xa_commit function and passes an invalid transaction ID. - Frame-based interception may no longer work in some scenarios. For example, when you call the ICallFrame::GetMarshalSizeMax method inside the ICallSink::OnCall method, the RPC_S_INVALID_TAG is returned. This problem occurs because a mismatch exists between the DCOM protocol version that the Rpcrt4.dll returns and the minimum DCOM protocol version that is required by Oleaut32.dll. This problem may occur if you have installed the MS04-012 cumulative update for Microsoft remote procedure call (RPC) and for DCOM.
- The following error messages may be logged in the application event logs: These errors are logged incorrectly. These errors do not indicate that any problems exist that may affect the system.
- A call to the IRunningObjectTable::Revoke method or to the RevokeActiveObject function on an active object in the running object table (ROT) returns E_INVALIDARG. This problem occurs only if this is a weak registration in the ROT. For example, this problem occurs if the ROTFLAGS_REGISTRATIONKEEPSALIVE flag is not passed into the IRunningObjectTable::Register method. This problem may occur if you have installed the MS04-012 cumulative update for Microsoft RPC and for DCOM.
- If you set the default impersonation level on a COM+ server application to Anonymous in Component Services on Windows 2000, and then you start the application, you may experience a high CPU utilization condition. The COM+ system application will use most of the CPU time. To work around this issue, do not set your impersonation level to Anonymous.
- When you make an In-Process method call in a COM+ application on Windows 2000, and you pass a user-defined type from a Visual Basic component, you may experience an access violation.
- When you move an unauthenticated COM+ Queued Component Message from a Dead Queue back to a Public Queue, the Queued Component Listener will loop infinitely and will generate an Event ID: 4214 application event log message for each iteration.
- The Comrepl.exe replication tool exports and installs the COM+ application as an "application proxy" from the remote computer to the local computer. When you try to set the identity of the “application proxy,” you may receive the following error message:
- The netsvcs process may stop responding, or an access violation may occur. You may experience these problems if heap corruption occurs in the Svchost.exe process that contains Netsvcs.dll.
- When you run a COM+ server application on Windows 2000, a high CPU utilization condition may occur. This problem is caused by excessive registry accesses to look up COM class information.
- An unhandled exception in the COM service may cause an application to stop responding.
- An unhandled exception may cause the COM+ system application to quit unexpectedly during the Windows Startup process.
- A COM Object Lifetime Management "pinging" mechanism may time out. When this problem occurs, you may receive an RPC_E_DISCONNECTED error code, and the server object may be released.
- On a computer that is running Windows 2000, when you make a call to create the first instance of a COM+ object, and the computer is part of a workgroup, you may experience very slow performance on the first call. All later initialization calls have typical performance speeds.
- When you make a DCOM call, and you set the RPC Authentication Level flag by using the RPC_C_AUTH_LEVEL_DEFAULT activation time or a later time, the client may receive a 0x8001011a (RPC_E_NO_GOOD_SECURITY_PACKAGES) error message.
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:
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.
back to the top
Prerequisites
- Microsoft Windows 2000
Restart information
You must restart your computer after you apply this hotfix.
back to the top
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 hotfix rollup packages are cumulative. The following Microsoft Knowledge Base article contains a list of the problems that are fixed in the earlier hotfix rollup package:
828748 Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 28
Registry information
You do not have to create or modify any registry keys to apply any hotfixes that are contained in this package.
back to the top
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 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 ------------------------------------------------------------ 02-Jun-2004 16:35 2000.2.3515.0 169,232 Catsrv.dll 02-Jun-2004 16:35 2000.2.3515.0 595,728 Catsrvut.dll 02-Jun-2004 16:35 2000.2.3515.0 97,040 Clbcatex.dll 02-Jun-2004 16:35 2000.2.3515.0 552,720 Clbcatq.dll 02-Jun-2004 16:35 2000.2.3515.0 41,744 Colbact.dll 02-Jun-2004 16:35 2000.2.3515.0 198,416 Comadmin.dll 02-Jun-2004 16:35 2000.2.3515.0 97,552 Comrepl.dll 02-Jun-2004 16:35 2000.2.3421.351 342,288 Comsetup.dll 02-Jun-2004 16:35 2000.2.3515.0 1,468,176 Comsvcs.dll 02-Jun-2004 16:35 2000.2.3515.0 625,936 Comuid.dll 01-Jun-2004 22:09 2000.2.3515.0 1,818,600 Dtcsetup.exe 02-Jun-2004 16:35 2000.2.3515.0 239,888 Es.dll 02-Jun-2004 16:35 2000.2.3515.0 96,016 Msdtclog.dll 02-Jun-2004 16:35 2000.2.3515.0 717,584 Msdtcprx.dll 02-Jun-2004 16:35 2000.2.3515.0 1,140,496 Msdtctm.dll 02-Jun-2004 16:35 2000.2.3515.0 153,872 Msdtcui.dll 01-Jun-2004 22:21 2000.2.3515.0 155,408 Mtstocom.exe 02-Jun-2004 16:35 2000.2.3515.0 52,496 Mtxclu.dll 02-Jun-2004 16:35 2000.2.3515.0 26,896 Mtxdm.dll 02-Jun-2004 16:35 2000.2.3515.0 35,600 Mtxlegih.dll 02-Jun-2004 16:35 2000.2.3515.0 122,640 Mtxoci.dll 02-Jun-2004 16:35 5.0.2195.6935 954,640 Ole32.dll 11-Mar-2004 21:29 5.0.2195.6904 449,808 Rpcrt4.dll 02-Jun-2004 16:35 5.0.2195.6935 212,240 Rpcss.dll 01-Jun-2004 21:22 5.0.2195.6934 5,880,832 Sp3res.dll 02-Jun-2004 16:35 2000.2.3515.0 398,608 Txfaux.dll 02-Jun-2004 16:35 2000.2.3515.0 18,704 Xolehlp.dll
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
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
Additional query words: kbWin2000preSP5COMRollup30Fix
Keywords: kberrmsg kbhotfixrollup kbwin2000presp5fix kbfix kbbug kbqfe kbhotfixserver KB840999
