You have Microsoft Host Integration Server 2010 or Microsoft Host Integration Server 2009 installed on server that is running 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 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.
This problem occurs because TI does not create the required registry parameters under the following registry subkey on 64-bit systems when the Host Integration Server Design Tools component is not installed:
The Design Tools component is not installed unless Microsoft Visual Studio is also installed on the system. If these registry parameters are missing, 32-bit TI and BAHA applications may experience application exceptions. Also, if these registry entries are missing, TI WIP tracing is not enabled correctly.
Cumulative update information
Host Integration Server 2010
The fix that resolves this issue is included in cumulative update package 5 for Host Integration Server 2010. To obtain Cumulative Update 5, see the following Microsoft Knowledge Base article:
2728515 Cumulative update package 5 for Host Integration Server 2010
Host Integration Server 2009
The fix that resolves this problem is included in cumulative update package 7 for Host Integration Server 2009. To obtain Cumulative Update 7, see the following Microsoft Knowledge Base article:
2975320 Cumulative Update 7 for Host Integration Server 2009
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
Instead, the following registry key is used for all TI and BAHA processes:
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.