Last updated: February 20, 2009

This Readme file contains up-to-date information about Microsoft® Host Integration Server 2009 and supplements the Microsoft Host Integration Server 2009 documentation.

You can download the latest version of this topic at


What's New in This Release

The following is an overview of the new features and enhancements in this release of Microsoft Host Integration Server and the BizTalk Adapters for Host Systems.


Support for Microsoft Visual Studio® 2008 - The developer design tools in this release have been updated to support Microsoft Visual Studio 2008, in addition to Microsoft Visual Studio 2005.

Support for Microsoft Windows Server® 2008 and Microsoft Windows Vista® - The platform support in this release has been extended to support Microsoft Windows Server 2008 and Microsoft Windows Vista.

Messaging Integration Support on x64 Systems - The Messaging Integration features in this release are now supported on x64 systems.  These features include the BizTalk Adapters for WebSphere MQ and the new WCF Channel for WebSphere MQ.

VSS Writer - This release includes a Host Integration Server-specific writer for the Volume Shadow copy service. This allows VSS requests, which includes most back-up software, to include the HIS writer in their snapshots.

Data Integration

ADO.NET Entity Provider for DB2 - The Entity Provider for DB2 is built on the foundation of the Managed Provider for DB2 and enables developers to integrate DB2 databases with the ADO.NET Entity Framework.

ADO.NET Provider for DB2 Enhancements - The MsDb2Client now offers a method to cancel a running query. This feature allows developers to programmatically cancel long-running queries.

Managed Provider for Host Files Offline Mode - The Managed Provider for Host Files was enhanced to allow access to mainframe and midrange files locally in a Microsoft Windows® workstation. This feature allows the offline processing of mainframe and midrange files that are transferred from the host platforms through well-known methods like FTP. All the data conversation and record-handling operations exposed by the Managed Provider for Host Files are available without the need of a live connection to the host.

Visual Studio Data Access Services for Host Files - The Managed Provider for Host Files extends the support of Visual Studio Database Explorer allowing developers and architects to view data and structure of mainframe and midrange files.

Features No Longer Supported

The following is a list of features, platforms, and interfaces that are no longer supported in Host Integration Server 2009.

  • Microsoft Windows NT® 4.0

  • MS-DOS®

  • Windows Millennium Edition

  • Windows 98

  • Windows 95

  • Windows 3.x

  • OS/2

  • SNA Remote Access Service (SNARAS)

  • AppleTalk

  • 16-Bit Thunking DLLs

  • Distributed Function Terminal (Coax DFT) Link Service

  • Twinaxial Link Service

  • VSAM File Transfer Utility (VSAM FTP)

  • APPC File Transfer (AFTP)

  • Banyan VINES

  • Shared Folders Gateway Service

  • Novell Netware

  • Transaction Integrator Test Console

Planned Obsolete Features

You can see a list of features being considered for deprecation in future versions of Microsoft Host Integration Server at the following location:

Documentation Notes

Finding the Product Documentation

To access the product documentation after you install Host Integration Server, click Start, point to All Programs, point to Microsoft Host Integration Server 2009, and then click Documentation.

Contacting Microsoft About Documentation Issues

The Host Integration Server 2009 documentation team solicits your feedback about the documentation. Are you finding the information you need quickly? Are there any gaps in content coverage? Please send your comments and suggestions to us by using the feedback link in the online Help.

Known Issues and Limitations

Installation and Configuration

Read the Installation Guide before you install - It is important to read the Host Integration Server Installation Guide carefully and make sure all prerequisites are complete before you run the installation program. The Installation Guide is located in the same CD directory as this Readme.

Before installing over another pre-release version - When you are installing this release on a computer that already has a pre-release version of Host Integration Server 2009, the Setup program might not remove all assemblies from the global assembly cache (GAC).

As a result, you must manually remove any Microsoft.HostIntegration.* assemblies from the GAC before you install the current release.

Installation will upgrade ENTSSO without notification - In this release, installing Host Integration Server will automatically upgrade any previous version of Enterprise Single Sign-On that exists on your computer.

You may be prompted to reboot if uninstall is performed when a product file being uninstalled is locked by any application - When performing uninstall, applications might be running that lock the product files being uninstalled. Ensure that these applications are closed before you uninstall the product. If you proceed with uninstall without closing these applications, you may be prompted to reboot after the uninstall operation is completed.

System binaries (ATL, VC) not removed after uninstall - During setup of both Host Integration Server and the BizTalk Adapters for Host Systems, the following files are placed in the \Windows\System32 directory: ATL80.dll, mfc80u.dll, msvcm80.dll, msvcp80.dll, and msvcr80.dll.

When the product is uninstalled, these files are not removed because they could be used by other products.

Network Integration: DLC driver files not removed after uninstall - During setup of both Host Integration Server and the BizTalk Adapters for Host Systems, selecting the DLC feature will cause the following two files to be installed:

  • dlcapi.dll in the \Windows\system32 directory

  • dlc.sys in the \Windows\system32\drivers directory

When the product is uninstalled, these files are not removed. If necessary, and if there are no other components using the driver, you can manually delete these files.

Restrictions when using Active Directory® - When you install and configure Host Integration Server with Active Directory support, the service account must have write access to the organizational unit.

If Setup fails to start - In this release, the Setup.exe program might fail to start. If this occurs, you must use the .msi file that is located on the download location at platform\Bootstrap. Select the correct processor architecture, and then run the Bootstrap.msi file located in the directory.

Unable to connect to a Microsoft SQL Server® 2005 database from the Configuration Wizard - When you are connecting from Windows 2000 to a remote SQL Server 2005 database, the SQL Server computer and the client must be configured to use matching network protocols. Refer to the Network Configuration topics in the SQL Server Books Online.

Microsoft SQL Server services running as a service account - On Windows XP, SQL Server may encounter authentication failures when running under a user account. If you install Microsoft SQL Server 2005 and Host Integration Server together on one of these operating systems, the SQL Server services must be configured to run under the Local System account.

User names that contain the @ symbol not supported - In this release, user names that contain an @ symbol (for example, domain\@user) are not supported for the service account.

Deploying Host Integration Server 2009 as a backup - If you are deploying Host Integration Server as a backup in an existing back-level Host Integration Server domain, you must make the following configuration changes:

  • Create a COMLOGS share pointing to <installdir>\system. Grant the service account and HIS administrators group Read access. This share is used by the SNA Manager when you are creating link services on remote computers.

  • Add any users who need to perform administrative tasks to the local HIS Administrators group on the Host Integration Server 2009 computer.

  • Users who create link services must be local administrators on the computer where the link services will be created.

  • Use the same service account for the Host Integration Server 2009 server as is used for the back-level Host Integration Server servers. This will ensure that all components have the appropriate rights to perform their necessary functions.

Some new features on Host Integration Server 2009 will not be available until all servers in the subdomain have been upgraded.

Changing administrator or runtime groups does not remove rights for old groups - When you change the HIS runtime or HIS admin groups, we recommend that the previous groups be deleted or manually removed from the permissions of the following objects:

Shares: snatrace$, comcfg, linkcfg$

Files: C:\Program Files\Microsoft Host Integration Server

Registry: HKEY_LOCAL_MACHINE \Software\Microsoft\SNA Server, SNAbase, SNA Print Server, Host Integration Server, Cedar

Enterprise Single Sign-On

Service account not recognized after being added - When a service account is added to the domain ENTSSO Administrators group, the SSO Service account may not detect the new service account, even after a restart. For the change to take effect, it is necessary to log out of the system, log in again, and then restart the configuration.

Host Security migration utility is not supported on x64 - To perform migration from Host Security in Host Integration Server 2000 to Enterprise SSO in this release, run the migration utilities on a Windows x86 computer. The migration utilities will not work on x64.

Enterprise Single Sign-On supported on Windows Vista - This version of Enterprise Single Sign-On is supported on current releases of Windows Vista.

IPv6: Servers MMC unable to write to registry using FQDN - When using Enterprise SSO Servers MMC snap-in to manage an SSO Server running on Windows Vista, you may not be able to modify certain configuration options that involve registry access even when you have admin rights to read/write from the registry on that server (for example: Changing the Audit Levels).

This is because the Remote Registry service is not running on that computer. To solve this, ensure that the Remote Registry service is running on the Windows Vista computer.

SSOClientUI cannot enter IPv6 address - In the Enterprise Single Sign-On Client UI, an IPv6 address cannot be specified. You can specify only the server name in NETBIOS or FQDN format. However, you can specify the IPv6 address using the SSOClient.exe command line utility.

Configuration files from earlier versions of ESSO not supported - The new Host Integration Server Configuration Tool is incompatible with configuration XML files that were generated with an earlier version of Enterprise Single Sign-On (for example, Host Integration Server 2004 or BizTalk Server 2004). Using files generated by an earlier version of ESSO will cause the configuration to fail. You must use the Configuration Tool again as described in the Installation Guide, and save the new XML file.

Single Sign-On Service times out and fails to start - You might encounter the following error while you are running the Configuration Wizard:

The Single Sign-On (SSO) Service on <servername> did not start within the time-out limit.

This problem is known to occur when a SQL Server account has been deleted and re-created. Because SQL Server does not update the IDs in this case, security checks will fail, causing this problem. As a workaround, after you have deleted the SQL Server account, also remove it from the SQL Server logons.

You can do this in SQL Server Enterprise Manager by following these steps:

  1. Expand the server group, and then expand the server.

  2. Expand Security, and then click Logins.

  3. In the Details pane, right-click the logon to remove, and then click Delete.

  4. Confirm the deletion.

Create mapping fails in a private Windows 2000 domain when Application Users account is of domain-local scope - Attempts to create mapping in a domain on Windows 2000 might cause the following error:

ERROR: 0x80070005 : Access is denied.

The problem occurs when the specified user is not a member of the Application Users account. Domain-Local groups cannot be used for any of the SSO groups in mixed-mode domain environments, unless all operations are being performed on the domain controller itself.

Enabling Password Sync from Windows - A new configuration option must be set to enable password sync from Windows to ENTSSO. You can enable this option for ENTSSO to either receive password changes from PCNS (Password Change Notification Service) or MIIS (Microsoft Identity Integration Server). This option must be set on the ENTSSO server that is configured to receive password changes from either PCNS or MIIS.

To enable or disable this, run the ssoconfig command-line utility:

\Program Files\Common Files\Enterprise Single Sign-On>ssoconfig -allowPS

ssoconfig -allowPS <PCNS> {<yes>|<no>} <MIIS> {<yes>|<no>}

Example: To enable sync from both sources, run ssoconfig -allowPS PCNS yes MIIS yes

Although this option is also available in the Servers snap-in, it does not function correctly in this release.

SSO Administration MMC snap-in does not refresh automatically - We recommend that you right-click and Refresh views in the Enterprise SSO Administration snap-in after you perform any operation for any node or object.

Network Integration

If 3270 emulator fails on startup - When running on a computer with the ISA Server 2004 client, the 3270 emulator might fail on startup. Ensure the latest version of the ISA Server client is installed

Enabling Windows Firewall Exceptions - If you are running Host Integration Server 2009 on Windows XP with Service Pack 2, certain Host Integration Server features will require Windows Firewall to be configured for exceptions.

You can do this by following these steps:

  1. In Control Panel, start Windows Firewall.

  2. On the Exceptions tab, select Add Program.

  3. Locate the Host Integration Server installation directory, find the appropriate program, and select the check box next to the program name.

  4. For IP-DLC, select SNALINK.EXE.

  5. For HIP, select HIPSERVICE.EXE.

  6. For DB2 Distributed Transaction, select DRDAResync.exe.

  7. For remote SNA Management, select MngAgent.exe.

Session Integrator might fail when you use two different user accounts - The Session Integrator features currently exhibit problems when the Client application and the Service component are running under two different user accounts. The problem is related to a DCOM callback that is made from the Server components to the client. The Server user account must have Local and/or Remote access to the DCOM classes.

You can follow these steps as a workaround:

  1. Start DCOMCNFG.

  2. Expand Component Services.

  3. Right-click My Computer.

  4. On the COM Security tab, click Edit Default under Access Permissions.

  5. In the Access Permission dialog box, click Add to add the Server user context.

  6. If the Server is not on the same computer as the client, you must allow Remote Access to the user.

  7. Click OK twice.

Session Integrator Server service starts in incorrect order - The installation program does not start the Session Integrator Server service in the correct order after an initial installation. You may need to stop the Session Integrator Server by using the Service control manager MMC Snap-in.

You can follow these steps as a workaround:

  1. At a command prompt, type Net Stop SISERVER.

  2. After the SNA Transaction Session Server has stopped, issue a net stop snabase.

  3. After the Snabase program has stopped, issue a net start snabase.

  4. After the Snabase service has started successfully, issue a net start SISERVER.

Dependent PU Definitions - When configuring dependent connections over an IP-DLC Link Service, you must enter unique values for the IDBLK and IDNUM fields in the local node ID in the System Identification dialog box. These connections will not support PU definitions on VTAM that have been configured using only Fully Qualified CP names (Network Name plus CP Name).

SNA node service and IP-DLC link service must have distinct CP names - The SNA node service and IP-DLC link service must have distinct control point names in the APPN network. If they do not, the IP-DLC link service might fail to initialize.

UDP Ports must be configured as 12000-12004 - The IP-DLC Link Service uses the five well-known ports for the HPR/IP protocol, which are numbers 12000 to 12004. The port numbers are not configurable. If you are connecting the IP-DLC Link Service across a firewall, you must allow traffic through these ports.

Virtual Private Networks must use WAN Miniport Adapter - When connecting the IP-DLC Link Service to a Network Node Server and remote host or peer system located across a VPN, you must configure the link service Local Address to use the WAN Miniport Adapter listed in the Adapter Address list. The VPN connection must be active to view and select the VPN adapter in this list.

DLC Driver - Versions of Windows beyond Windows 2000 do not contain a driver for the DLC network protocol. To ensure that users of Host Integration Server 2009 can continue to use 802.2 Link services for SNA communication on those versions of Windows, the DLC driver is provided in the Host Integration Server 2009 installation. This version of the DLC driver is only supported for use with Host Integration Server 2009 on x86 platforms. The x64 version of DLC is not currently available. Please check for updates.

The DLC driver is now a selectable feature in the Host Integration Server 2009 server Setup. It appears under SNA Application Support, SNA Server in the Windows Installer feature tree.

Third-party link services - IP-DLC, DLC (802.2), Demo, and Distributed Link services are automatically installed with the Host Integration Server 2009 SNA service.

To receive updates for third-party link services, contact your vendor.

Using a custom mode for Resync partnering - A new feature of Host Integration Server 2009 allows the administrator to partner the LUs to be used for two-phase commit. This feature uses an existing mode definition. If the user changes this to use a different mode, the LU6.2 Resync service must be stopped and restarted for the change to take effect.

Resource location by SubDomain name no longer supported in Host Integration Server - Resource location by SubDomain name is no longer supported in Host Integration Server. This configuration will not be carried forward during an upgrade. The client will need to be configured to use a specific sponsor server.

Netview services unavailable - The NValert, NVRUNCMD and SNANETNM services are unavailable in the beta release.

Data Integration

SQL Server Integration Services: Package Designer - When you are using SQL Server Integration Services with the Microsoft OLE DB Provider for DB2 within the Package Designer in Visual Studio 2005, SSIS might raise the following warning:

"Warning at {9C6AC00C-13CF-4EF8-B44A-72055CC508C2} [OLE DB Source [262]]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used."

SQL Server Integration Services supports the option of specifying a per-column Locale Identifier for string data types, such as DB2 CHARACTER and DB2 VARYING CHARACTER. The Microsoft OLE DB Provider for DB2 does not support this option.

To work around this limitation, when using the SSIS Package Designer, follow these steps:

1. In the Data Flow Task design surface, add a new OLE DB Source or OLE DB Destination, to use with the Microsoft OLE DB Provider for DB2.

2. Right-click the OLE DB source or destination object, and then select Show Advanced Editor.

3. In the Advanced Editor, click the Component Properties page.

4. Set AlwaysUseDefaultCodePage to True.

5. Click OK to save this setting for use with this OLE DB source or destination object within this SSIS package.

Parameterized Statements - When using SQL Server Integration Services with SQL commands containing parameters (WHERE clauses), you must set the optional OLE DB data source initialization property “Derive Parameters” to TRUE. This property instructs the provider to discover the parameter's data type from the data source prior to command execution, upon request of the consumer. You can set this property from the Advanced Options page of the Data Source Wizard, or the All tab of the Data Links dialog box. You can specify this property in an OLE DB initialization string (connection string) using the “Derive Parameters=TRUE” argument.

Set this value to TRUE when using SQL Server Integration Services with parameterized statements that include a WHERE clause (for example, SELECT, INSERT, UPDATE DELETE).

The default value is FALSE for use with SQL Server Replication Services and other generic consumers that cannot support the derive parameter property with DB2.

Managed Provider for Host Files Offline Mode is Read-only - The Managed Provider for Host Files offline mode only supports read-only access to data.

Managed Provider for Host Files metadata files should be registered in the global assembly cache - Metadata files used by the Managed Provider for Host Files should be registered in the GAC using the GACUTIL tool as well the REGASM tool. You must register the metadata assemblies created using the Host Files project within Visual Studio 2005, using the REGASM tool.

Managed Provider for Host Files doesn’t support 8-byte integers (BIGINT) - When using the Managed Provider for Host Files, 8-byte integers are not supported.

Visual Studio Server Explorer for DB2 and Server Explorer for Host Files are not enabled on an x64 computer - In this release, the Visual Studio Server Explorer for DB2 and Server Explorer for Host Files will not be enabled on an x64 computer.

Verify SQL Syntax option not supported - The Visual Studio Verify SQL Syntax option is not supported in this release.

Connections with database are Read/Write only - The option to configure a Read-only connection with the database is not supported. Although this option appears in the user interface, selecting it will not create a Read-only connection. All connections with the database are Read/Write. This option appears in the following locations:

  • Data Access Tool, Data Source Wizard, Advanced Options page

  • BizTalk Adapter for DB2 Connection Configuration Wizard

Microsoft OLE DB Provider for AS/400 and VSAM - The Microsoft OLE DB Provider for AS/400 and VSAM is not supported in the WOW64 on the IA-64 or X64 platform.

Stored Procedures - The OLE DB Provider for DB2 does not support executing stored procedures on behalf of the SQL Server Integration Services consumer.

Two-Phase Commit fails over APPC connection - In this release, Two-Phase Commit is not supported over an APPC connection.

UDLs Used by the Managed Provider for Host Files should be created using the Data Access Tool - The Data Access Tool is the preferred method to create UDLs to be used with the Managed Provider for Host Files.

APPC connection not supported to SQL Server Linked Server - This release does not support APPC connections to a SQL Server Linked Server. You must use the TCP/IP transport instead.

Connections - When you create a HostFileDataAdapter object with a valid connection string, the HostFileDataAdapter will create a connection to the remote host file server. There are two valid ways to close this connection:

  • HostFileDataAdapter.Dispose(); and

  • HostFileDataAdapter.SelectCommand.Connection.Close().

MaxPoolSize Property - This property is only supported in the Managed Provider for DB2.

Server Explorer for Host Files - The server explorer for Host Files only supports metadata defined in Host Files Assembly format and not HCD format.

Managed Provider for Host Files Offline Mode – When accessing host files in offline mode, make sure the mainframe or midrange file is downloaded from the host in binary format without any data conversion.

Transaction Integrator

Transaction Integrator does not support COM clients under the X64 platform.

Using TI Client Context with the BizTalk Adapter for Host Applications - The BizTalk Adapter for Host Applications supports the following TI ClientContext keywords:

USERID, PASSWORD, SendTimeOut and RecvTimeOut.

See the online documentation for detailed definitions of the TI ClientContext keywords.

To use ClientContext, you must add them as part of your XML document. One way to do this is to use BizTalk Server to generate an instance of the XML document based on XSD that the TI Designer generated at the same time the assembly was generated. When it is generated, edit the TIClientContext element, <ns0:TIClientContext TIContextKeyword="TIContextKeyword_0" TIContextValue="TIContextValue_1" />, replacing "TIContextKeyword" with a valid TI ClientContext keyword and the "TIContextValue" with valid data for that keyword.

You do not have to remove TI ClientContext elements from your document even if you are not using ClientContext.


<ns0:DPC_WGB__GetBalance__WGBANK__Request xmlns:ns0="">
    <ns0:name>Kim Akers</ns0:name>
  <ns0:TIClientContext TIContextKeyword=" SendTimeOut " TIContextValue="10"/>
<ns0:TIClientContext TIContextKeyword="TIContextKeyword_0"TIContextValue="TIContextValue_1" />

TI components created using the Component Services snap-in appear as WIP objects but are unassigned - If you use the Component Services snap-in to add WIP components to a new COM application, the components will be created and will appear in the WIP Objects node. However, if you try to assign the object to a remote environment, you might receive the following (or similar) error message: (5037) Property hosted by the object has not been set.

Test Console has been discontinued in this release - The Test Console has been discontinued in this release.

Type library properties are altered during migration - After you import a COM type library into a .NET assembly, Currency data types will be changed to Decimal types. Because of differences between COM Currency and .NET Decimal, the precision and scale for Decimal is set to the default value of (9,9). This default may differ from the precision and scale on the Currency data item. To resolve this issue, change the precision and scale properties on each Decimal element in the .NET assembly.

Listing deployed assembly - To see a list of deployed assemblies, click Windows Initiated Processing, click Objects, and then refresh (F5).

Designer reply message schema - The Designer does not create an XSD reply schema when the method contains only input parameters.

Designer request - The Designer does not generate a Request section XSD if the method contains no input or input\output parameters.

Auto Refresh set to off - By default, the Auto Refresh feature in the Designer is set to off.

Pasted union parameter loses DVT & Discriminant - If a parameter of union type (with DVT/Discriminant defined before Copy command) is copy/pasted in a method, the DVT & Discriminant are lost. The workaround is to fill in DVT manually after paste.

Icon in TI Manager - In TI Manager, an object that has a yellow triangle icon indicates that the object is in a Rapid Deployment State.

"Program Library" field set in Client Library Wizard for AS/400 doesn't propagate to new methods - A new method's "Library Name" property doesn't get set to the library name specified in the Client Library Wizard as expected. The workaround is to enter the Library manually on the created method.

TI Designer has a dependency on the following Visual Studio 2005 C++ components (midl, cl, rc) - If these components are not installed you will be able create TI projects but will not be able to save them. To resolve this issue you need to either install the C++ feature of Visual Studio 2005 or contact PSS for help on how to install the Windows Platform SDK.

TI WIP & HIP perfmon counters do not show up on remote computers - This is scheduled to be fixed in the first service pack.

TI no longer adds 1-byte filler to transaction names of 8 bytes over IMS Connect as it did in previous versions - If your application is written to work with the filler you can enable this behavior of adding the 1-byte filler by adding the following registry entry:


The value is unimportant; only the existence of the key is required.

MSMQ-MQSeries Bridge

Encryption feature - The MSMQ-MQSeries Bridge encryption feature is only supported in a pure AD environment (either Windows 2000 domain or Windows 2003 domain). This feature will not be supported in a mixed environment with MSMQ running on Windows NT 4.0.

Bridge Service Account does not have access to configuration information - You must ensure that the Bridge service account has read/write permissions given on the HKLM\Software\Microsoft\MQBridge key on the computer where the Bridge service is configured.


Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, BizTalk, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.