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

This article lists the Microsoft COM+ bugs that are fixed in Microsoft Windows Server 2003 Post-Service Pack 1 (SP1) COM+ 1.5 Hotfix Rollup Package 7. Each 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.

• 903087 FIX: An Office 2003 application stops responding for 10 to 15 seconds when you save a document that contains paths to resources that do not exist on the network on a computer that is running Windows Server 2003
• 904388 FIX: A COM+ application stops responding, and desktop icons and the taskbar may not appear as expected on a computer that is running Windows Server 2003
• 906677 FIX: The DCOM server settings revert to the default settings when you remove all users from the "Launch and Activation Permissions" area in the Component Services (DCOMCONFG) tool on a computer that is running Windows Server 2003
• 905430 FIX: Statistics may not display correctly for some COM+ applications on a computer that is running Windows Server 2003
• 908187 FIX: A 144-byte memory leak occurs in the Ole32.dll file when you start a COM+ application
• 910234 FIX: Error message when a serviced component in a COM+ application calls another serviced component in a second COM+ application: "0x8004E027"
• 910383 COM+ functionality may be disabled after you install the security update that is associated with security bulletin MS05-051 on a computer that is running a 64-bit edition of Windows Server 2003
• 910471 FIX: An access violation occurs in MS DTC when a client tries to create an enlistment
• 910695 FIX: The error message does not contain sufficient information to determine the cause of a DCOM error in Windows Server 2003

This hotfix rollup package also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• System events tracing fails because of a race condition.
• An object may be created in the wrong apartment because of a bug in the property matching code in Ole32.dll.
• Security is improved in COM processes.
• When you use asynchronous DCOM, a memory leak occurs every time that a call is handled by the server-side stub.
• When object access auditing is enabled, a Failure Audit event that has event ID 560 occurs.
• When a subordinate is removed from the subordinate list in the Transaction Manager because of a duplicate export error, the Distributed Transaction Coordinator does not decrement the total log record space that is being used.
• Files that are opened in read-only mode require more memory than files that are opened in read/write mode.

Service pack information

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:

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: 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

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:

• 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

Registry information

You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

Hotfix file information

This hotfix rollup package contains only those files that you must have to correct the issues that this article lists. This hotfix rollup package may not contain all the files that you must have to fully update a product to the latest build.

The English version of this 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, Itanium Architecture

Windows Server 2003 SP1, Itanium Architecture

Windows Server 2003 SP1, x64

Windows Server 2003, x86

Windows Server 2003 SP1, x86

For more information about software update terminology, 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.