Availability of Windows Server 2003 COM+ 1.5 Rollup Package 4

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

SUMMARY

This article lists the Microsoft COM+ bugs that are fixed in Microsoft Windows Server 2003 COM+ 1.5 Rollup Package 4. Each package contains all the fixes that were released in the previous Windows Server 2003 COM+ 1.5 rollup packages.

Back to the top

Issues that are fixed in this rollup package

The following issues are fixed in this rollup package. These issues were not documented in an earlier Microsoft Knowledge Base article.

When the COM+ Server application calls the Library application, and an exception error occurs, the COM+ Server application does not produce a stack dump file in Windows Server 2003.
The COM+ root component continues to make method calls to the secondary component after the secondary component has aborted the transaction. When this issue occurs, the following message is logged in the Application log:
You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting.
An endless loop in the comsvcs!CEventDispatcher::RemoveEventBuffer function causes the W3WP.exe process to stop responding.
When you install the Oracle FailSafe service, the service replaces the default access permission of the self account in DCOM with the user account permissions that you used to install the Oracle FailSafe service.
When Microsoft SQL Server becomes available online before Microsoft Distributed Transaction Coordinator (MSDTC) is online in an Active / Active Microsoft Cluster Server (MSCS) cluster environment, you may receive an error message that is similar to the following:
Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE.
The Dcomcnfg.exe utility incorrectly reports that network access is enabled on a Cluster service.
When the Distributed Transaction Coordinator (DTC) service is unavailable, you cannot access the properties of an individual COM component to configure the security for that component. For example, the DTC service may be unavailable because the startup type of the service is set to Disabled.
The COM+ Application service fails at startup after a computer restarts. This issue occurs when the service is configured for automatic startup.
The CImpIXaTransaction::TerminateYourSelf function fills the DTCInstall.log file with trace statements. This issue may cause other issues when free hard disk space has decreased.
The MSDTC.exe process crashes when you run out of log space. When this issue occurs, a message that is similar to the following is logged in the event log:
1) MS DTC Transaction Manager log write failed with error 0x8.
2) An MS DTC component has generated an exception. Error Specifics: The process 'C:\WINDOWS\system32\msdtc.exe' hit an exception in a MSDTC related component.
The COM:CStdMarshal::MarshalInterface function does not write a custom object reference to a stream when you choose wrapper marshaling.
The COM+ replication utility (COMREPL) does not synchronize the source computer with the destination computer when a COM+ Proxy application is installed on the source computer.
Earlier access violations in the user's code cause the DoThreadSpecificCleanup function to indefinitely call the CoUninitialize function.
This rollup package adds the COMBND_SERVER_LOCALITY option for the IRpcOptions::Query garbage collection method.
When the MSDTC service is disabled, the Setup process for the hotfix that is discussed in Microsoft Knowledge Base (KB) article 823230 stops responding during a call to the DtcGetTransactionManagerEx function. For more information about KB823230, click the following article number to view the article in the Microsoft Knowledge Base:
823230 (http://support.microsoft.com/kb/823230/ ) Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
When the CoEnterServiceDomain function is called from the context of an aborted transaction, an unrecoverable inconsistent state in the Services Without Components (SWC) infrastructure occurs. Additionally, the CoLeaveServiceDomain function will continue to fail with a CONTEXT_E_NOCONTEXT error.
When you use the Data Transformation Service (DTS) to transfer data between SQL Server and Oracle Database, MSDTC crashes.
When a deleted client set object remains in the list that the rpcss!gpClientSetLocalPList function maintains, an access violation occurs on this deleted memory.
After you apply the security update that is discussed in KB article 873333, the OleGetClipboardData function returns null for OLE objects. Also, clipboard operations do not function correctly. For more information about KB873333, click the following article number to view the article in the Microsoft Knowledge Base:
873333 (http://support.microsoft.com/kb/873333/ ) MS05-012: Vulnerability in OLE and COM could allow remote code execution

Back to the top

MORE INFORMATION

Service pack information

To resolve the issues that this article lists, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 (http://support.microsoft.com/kb/889100/ ) How to obtain the latest service pack for Windows Server 2003

Back to the top

Hotfix rollup package 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:

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

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

Microsoft Windows Server 2003

Restart information

You must restart the computer after you apply this rollup package.

Hotfix replacement information

This rollup package is not replaced by any later hotfix.

Bugs that are fixed in the Windows Server 2003 COM+ 1.5 rollup packages are cumulative. For more information about the previous rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

821751 (http://support.microsoft.com/kb/821751/ ) Availability of Windows Server 2003 COM+ 1.5 Rollup Package 1

Registry information

You do not have to create or modify any registry keys to enable any hotfixes that are contained in this rollup package.

Hotfix file information

This rollup package contains only those files that you must have to correct the issues that this article lists. This rollup package 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 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 Server 2003, 32-bit versions

   Date         Time   Version          Size       File name
   ------------------------------------------------------------
   15-Mar-2005  17:36  2001.12.4720.28    263,680  Catsrv.dll
   15-Mar-2005  17:36  2001.12.4720.28    587,264  Catsrvut.dll
   15-Mar-2005  17:36  2001.12.4720.28     98,304  Clbcatex.dll
   15-Mar-2005  17:36  2001.12.4720.28    493,056  Clbcatq.dll
   15-Mar-2005  17:36  2001.12.4720.28     58,880  Colbact.dll
   15-Mar-2005  17:36  2001.12.4720.28    189,440  Comadmin.dll
   15-Mar-2005  17:36  2001.12.4720.28     86,528  Comrepl.dll
   15-Mar-2005  17:36  2001.12.4720.28  1,206,272  Comsvcs.dll
   15-Mar-2005  17:36  2001.12.4720.28    566,272  Comuid.dll
   15-Mar-2005  17:36  2001.12.4720.28    226,816  Es.dll
   15-Mar-2005  17:36  2001.12.4720.28    445,440  Msdtcprx.dll
   15-Mar-2005  17:36  2001.12.4720.28    972,288  Msdtctm.dll
   15-Mar-2005  17:36  2001.12.4720.28    161,280  Msdtcuiu.dll
   15-Mar-2005  17:36  2001.12.4720.28     76,288  Mtxclu.dll
   15-Mar-2005  17:36  2001.12.4720.28    109,056  Mtxoci.dll
   15-Mar-2005  17:36  5.2.3790.288     1,193,984  Ole32.dll
   16-Mar-2004  03:17  5.2.3790.141        26,112  Rpcproxy.dll
   16-Mar-2004  03:17  5.2.3790.141       659,968  Rpcrt4.dll
   15-Mar-2005  17:36  5.2.3790.288       295,424  Rpcss.dll

Windows Server 2003, 64-bit version

   Date         Time   Version          Size       File name      Platform
   -----------------------------------------------------------------------
   15-Mar-2005  16:33  2001.12.4720.28    641,536  Catsrv.dll     IA-64
   15-Mar-2005  16:33  2001.12.4720.28  1,568,256  Catsrvut.dll   IA-64
   15-Mar-2005  16:33  2001.12.4720.28    263,680  Clbcatex.dll   IA-64
   15-Mar-2005  16:33  2001.12.4720.28  1,294,848  Clbcatq.dll    IA-64
   15-Mar-2005  16:33  2001.12.4720.28    180,224  Colbact.dll    IA-64
   15-Mar-2005  16:33  2001.12.4720.28    412,160  Comadmin.dll   IA-64
   15-Mar-2005  16:33  2001.12.4720.28    275,456  Comrepl.dll    IA-64
   15-Mar-2005  16:33  2001.12.4720.28  3,140,096  Comsvcs.dll    IA-64
   15-Mar-2005  16:33  2001.12.4720.28  1,873,408  Comuid.dll     IA-64
   15-Mar-2005  16:33  2001.12.4720.28    654,336  Es.dll         IA-64
   15-Mar-2005  16:33  2001.12.4720.28  1,309,184  Msdtcprx.dll   IA-64
   15-Mar-2005  16:33  2001.12.4720.28  3,167,232  Msdtctm.dll    IA-64
   15-Mar-2005  16:33  2001.12.4720.28    463,360  Msdtcuiu.dll   IA-64
   15-Mar-2005  16:33  2001.12.4720.28    203,776  Mtxclu.dll     IA-64
   15-Mar-2005  16:33  2001.12.4720.28    320,000  Mtxoci.dll     IA-64
   15-Mar-2005  16:33  5.2.3790.288     3,582,464  Ole32.dll      IA-64
   31-Mar-2004  02:25  5.2.3790.141        73,216  Rpcproxy.dll   IA-64
   31-Mar-2004  02:25  5.2.3790.141     2,150,400  Rpcrt4.dll     IA-64
   15-Mar-2005  16:33  5.2.3790.288       689,664  Rpcss.dll      IA-64
   15-Mar-2005  16:36  2001.12.4720.28    263,680  Wcatsrv.dll    x86
   15-Mar-2005  16:36  2001.12.4720.28    587,264  Wcatsrvut.dll  x86
   15-Mar-2005  16:36  2001.12.4720.28     98,304  Wclbcatex.dll  x86
   15-Mar-2005  16:36  2001.12.4720.28    493,056  Wclbcatq.dll   x86
   15-Mar-2005  16:36  2001.12.4720.28     58,880  Wcolbact.dll   x86
   15-Mar-2005  16:36  2001.12.4720.28    189,440  Wcomadmin.dll  x86
   15-Mar-2005  16:36  2001.12.4720.28  1,206,272  Wcomsvcs.dll   x86
   15-Mar-2005  16:36  2001.12.4720.28    226,816  Wes.dll        x86
   15-Mar-2005  16:36  2001.12.4720.28    445,440  Wmsdtcprx.dll  x86
   15-Mar-2005  16:36  2001.12.4720.28    161,280  Wmsdtcuiu.dll  x86
   15-Mar-2005  16:36  2001.12.4720.28     76,288  Wmtxclu.dll    x86
   15-Mar-2005  16:36  2001.12.4720.28    109,056  Wmtxoci.dll    x86
   15-Mar-2005  16:36  5.2.3790.288     1,193,984  Wole32.dll     x86
   31-Mar-2004  02:26  5.2.3790.141        26,112  Wrpcproxy.dll  x86
   31-Mar-2004  02:26  5.2.3790.141       544,256  Wrpcrt4.dll    x86

Back to the top

REFERENCES

For more information, 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

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