You perform a "nodeless" installation of Microsoft Host Integration Server 2009. To do this, you install only the Transaction Integrator feature under the Server component during the setup process.
You run the Host Integration Server 2009 Configuration Tool to configure the Host Integration Server 2009 system to communicate with a back-end Host Integration Server system.
You run Transaction Integrator (TI) Manager to create a Remote Environment (RE) that has a Logical Unit (LU) 6.2 type.
In this scenario, the New Remote Environment Wizard exits when you click Next on the Configure Host Environment and Programming Model panel. Additionally, event messages that resemble the following may be logged when this problem occurs:
Event ID: 1000 Source: Application Error Description: Faulting application mmc.exe, version 6.0.6002.18005, time stamp 0x49e02760, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000005, fault offset 0x0000000000086996, process id 0x%9, application start time 0x%10.
This issue occurs because the Transaction Integrator Manager tries to issue several Windows Management Instrumentation
(WMI) queries to obtain a list of Advanced Program-to-Program Communications (APPC) 6.2 Logical Units and APPC mode names that are configured in the Host Integration Server subdomain. The Host Integration Server WMI namespace is not installed when you perform a "nodeless" Host Integration Server installation. The result is that the WMI queries that are issued by the Transaction Integrator Manager fail. The Transaction Integrator Manager exits unexpectedly when it tries to format the underlying WMI errors.
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 the problem described in this article. 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 website:
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.
There are no prerequisites for installing this hotfix package.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.
For Microsoft Host Integration Server 2009, 32-bit editions