Select the product you need help with

FIX: A 32-bit Transaction Integrator or BizTalk Adapter for Host Applications application may fail when the application is run on a 64-bit version of Host Integration Server 2010

Article ID: 2729431 - View products that this article applies to.

Expand all | Collapse all

Symptoms

Consider the following scenario:

You have Microsoft Host Integration Server 2010 installed on a 64-bit version of Windows Server.
You use Transaction Integrator (TI) or the Microsoft BizTalk Adapter for Host Applications (BAHA) to integrate with an IBM host application.
The TI or BAHA application is running as a 32-bit process.

In this scenario, you may experience the following symptoms:

The 32-bit TI or BAHA application experiences application exceptions.
You do not receive TI trace data when TI Windows-Initiated Processing (WIP) trace options are enabled.

Back to the top | Give Feedback

This problem occurs because Transaction Integrator does not create the required registry parameters under the following registry subkey on 64-bit systems when the Host Integration Server 2010 Design Tools component is not installed:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Cedar

The Design Tools component is not installed unless Microsoft Visual Studio is also installed on the system. Thirty-two-bit TI and BAHA applications may experience application exceptions when these registry parameters are missing. TI WIP tracing is not enabled correctly when these registry entries are missing.

Back to the top | Give Feedback

Resolution

Cumulative update information

The fix that resolves this issue is included in cumulative update package 5 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2728515

(http://support.microsoft.com/kb/2728515/ )

Cumulative update package 5 for Host Integration Server 2010

Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

More information

After this update is applied, Transaction Integrator and the BizTalk Adapter for Host Applications no longer use the following registry subkey for configuration information for 32-bit processes on 64-bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Cedar

Instead, the following registry key is used for all TI and BAHA processes:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar

Back to the top | Give Feedback