Microsoft KB Archive/934016

= Availability of Windows Server 2003 Post-Service Pack 2 COM+ 1.5 Hotfix Rollup Package 12 =

Article ID: 934016

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft COM+ 1.5
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition

-



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

Issues that are fixed in the hotfix package
The following issue is fixed in this hotfix package.  

933863 FIX: The account that is configured on the Identity tab in the Component Services snap-in may change when you select multiple COM+ server applications





The following issues are also fixed in this hotfix package but were not previously documented in a Microsoft Knowledge Base article:  Registration of COM+ components does not function correctly in Windows Server 2003 64-bit editions. When a network is disconnected from a Windows Server 2003-based computer, the remote procedure call (RPC) port that was used by DCOM remains open for several hours. Requests from clients for the remote COM object fail with a 0x800706BA error. If the Windows Server 2003-based computer is under heavy load conditions, the Microsoft Distributed Transaction Coordinator (MS DTC) may stop responding when it writes to the MS DTC log file. Additionally, the following error messages may be logged in the event log:

Error message 1

Event Type: None

Event Source: MSDTC

Event Category: TM

Event ID: 4171

Date:

Time:

User: N/A

Computer:

Description:

MS DTC Transaction Manager log write failed with error 0x8000d005.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Error message 2

Event Type: Error

Event Source: MSDTC

Event Category: LOG

Event ID: 4154

Date:

Time:

User: N/A

Computer:

Description:

The MS DTC log file is unreadable. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run &quot;msdtc -resetlog&quot; to reset the log file.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.





Hotfix 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
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, click the following article numbers to view the articles in the Microsoft Knowledge Base:

821751 Availability of Windows Server 2003 COM+ 1.5 Rollup Package 1

883955 Availability of Windows Server 2003 COM+ 1.5 Rollup Package 3

895250 Availability of Windows Server 2003 COM+ 1.5 Rollup Package 4

896729 Availability of Windows Server 2003 Post-Service Pack 1 COM+ Hotfix Rollup Package 5

897667 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6

910730 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 7

912818 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 8

924729 Availability of the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 10

927673 Availability of the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 11

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.

Windows Server 2003 SP1, Itanium-based systems
