This article lists the Microsoft COM+ bugs that are fixed in the Microsoft Windows Server 2003 COM+ 1.5 Hotfix Rollup Package 10. Each hotfix rollup package contains all the fixes that were released in the previous Windows Server 2003 COM+ 1.5 hotfix rollup packages.
Issues that are fixed in this hotfix rollup package
This hotfix rollup package fixes the following issues:
FIX: Event ID: 4811 occurs when you try to start a queued COM+ application that has a long name and Microsoft Message Queuing is configured for Workgroup mode in Windows Server 2003
FIX: A CustomAttributeFormatException exception may occur when you try to install a COM+ application proxy on a Windows Server 2003-based computer that is running the .NET Framework 2.0
FIX: The size of DTC log file cannot be changed in Microsoft Windows Server 2003 Service Pack 1
This hotfix rollup package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
If a COM+ application contains a .NET assembly or a .NET ServicedComponent class that is compiled for 32-bit processors, you cannot export this COM+ application. Additionally, you receive the following error message:
The files could not be imported because they were compiled for a different processor type than the components already installed in the application
Indigo transaction tests do not work correctly after you apply the hotfix that is described in Microsoft Knowledge Base article 921981.
The Microsoft Distributed Transaction Coordinator (MS DTC) intermittently crashes on a IA-64-based cluster computer.
The client breaks into the debugger and throws an ArgumentException exception.
DCOM may cause TCP port exhaustion on the client side. This behavior occurs when DCOM is in nonsecure mode (AuthLevel="none").
Data is sent according to the length that is returned by the GetBuffer method instead of the buffer length that is returned by the SendReceive method.
A "notregistered" item is incorrectly stored in the ClassInfo cache.
Streams in transaction sets do not have their caches emptied after consolidation occurs.
Memory fragmentation occurs in the Msdtcprx.dll library.
The MS DTC shuts down because an inconsistent state occurs.
You cannot view or edit the MachineLaunchRestriction and MachineAccessRestriction settings in the Distributed COM Configuration (Dcomcnfg.exe) tool.
A race condition occurs between the marshaling and release of ole32!CStdWrapper objects. This race condition causes the ole32!CtxEntry objects to be incorrectly reference counted.
If you call the DeleteTimerQueueTimer method, the COM+ System Application stops responding (hangs).
To resolve this problem, 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:
How to obtain the latest service pack for Windows Server 2003
Hotfix rollup package information
Prerequisites
You must have Windows Server 2003 installed to apply this hotfix rollup package.
Restart information
You must restart the computer after you apply this hotfix rollup package.
Hotfix replacement information
Bugs that are fixed in the Windows Server 2003 COM+ 1.5 hotfix rollup packages are cumulative. For more information about the previous hotfix rollup packages, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 8
Registry information
You do not have to create or modify any registry keys to enable any hotfixes that are contained in this hotfix rollup package.
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 item in Control Panel.
For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
Back to the top
