FIX: Error message when a serviced component in a COM+ application calls another serviced component in a second COM+ application: "0x8004E027"

Consider the following scenario:

• A serviced component in a Microsoft COM+ application calls another serviced component in a second COM+ application.
• Each serviced component connects to a data store in Microsoft SQL Server.
• The first serviced component is marked TX required.
• The second serviced component is marked TX supported.
• The computer has the critical update that is discussed in Microsoft Knowledge Base article 902400 installed.
• The computer has the Microsoft .NET Framework 2.0 installed.

In this scenario, you may receive an error message that is similar to the following:

This problem occurs because the .NET Framework 2.0 calls the FetchTransaction method in COM+. The FetchTransaction method requires a transaction. If a transaction is not present in the second serviced component, you receive the error message that is mentioned in the "Symptoms" section.

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

This problem is fixed in Microsoft Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 7. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

Prerequisites

You must have Windows Server 2003 installed on the computer to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

Windows Server 2003, Itanium architecture

Windows Server 2003 Service Pack 1 (SP1), Itanium architecture

Windows Server 2003 SP1, x64

Windows Server 2003, x86

Windows Server 2003 SP1, x86

To work around this problem, use one of the following methods.

Method 1: Mark the second serviced component TX required

Mark the second serviced component TX required instead of TX supported.

Method 2: Modify the registry

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To modify the registry, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\Software\COM3
3. On the Edit menu, point to New, and then click String Value.
4. Type DisablePromotableTransactions, and then press ENTER.
5. On the Edit menu, click Modify, type Y, and then click OK.
6. Quit Registry Editor.

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.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: