Microsoft KB Archive/910312

= How to allow Host Integration Server 2004 distributed transactions in a clustered SQL Server environment =

Article ID: 910312

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2004 Standard Edition

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SUMMARY
This article describes how to install the databases and set the configuring permissions to allow Microsoft Host Integration Server 2004 distributed transactions over TCP/IP to work in a clustered Microsoft SQL Server environment.



INTRODUCTION
When you run Host Integration Server 2004 Transaction Integrator (TI) in a clustered SQL Server environment, it is a supported configuration. However, the Host Integration Server 2004 Configuration Wizard (ConfigFramework.exe) cannot configure databases in a clustered SQL Server environment. When you try to configure required Host Integration Server groups for access control, you may receive the following error message:

The domain group  \  e specified for the HIS Admin (or HIS Runtime) Group is not supported. Please specify a local group.

Entries that are similar to the following are listed in the Host Integration Server 2004 configuration log: [6:12:10 PM Info DatabaseHelper] Configuring HISAdmin database role. [6:12:10 PM Info DatabaseHelper] Executing database stored procedure: [6:12:10 PM Info DatabaseHelper] sp_grantlogin ' ServerName \HIS Administrators' [6:12:10 PM Error ConfigHelper] Windows NT user or group ' ServerName \HIS Administrators' not found. Check the name again. [6:12:10 PM Error ConfigHelper] SQL error: 42000 Native error code: 15401

Note The name of the Host Integration Server 2004 configuration log file is formatted as Config.log.

For more information about how to find the configuration log, click the following article number to view the article in the Microsoft Knowledge Base:

885651 You cannot find the Host Integration Server 2004 Setup and configuration log files in the %TEMP% folder



MORE INFORMATION
The Host Integration Server 2004 Configuration Wizard is not designed to work with clustered servers that are running instances of SQL Server. Follow these steps when you use DB2 distributed transactions with a clustered SQL Server environment:

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.
 * 1) Manually create a database that is named MSHIS60_DATA on the clustered instance of SQL Server.
 * 2) Create HIS Administrators groups and HIS Runtime local user groups on each node in the cluster.
 * 3) Create HISAdmin roles and HISRuntime roles in the newly created database.
 * 4) On each node in the cluster, add the HIS Administrators groups and the HIS Runtime user groups as logins to the newly created database. Additionally, add the user groups to the HISAdmin role or the HISRuntime role, as appropriate.
 * 5) Run the DuwTcpSetup.sql script to create the tables and the stored procedures in the database.

Note By default, the DuwTcpSetup.sql script is located in the %root%\Program Files\Microsoft Host Integration Server\system folder.
 * 1) Run the Host Integration Server 2004 Configuration Wizard on the DATA server. First, point the Host Integration Server 2004 Configuration Wizard to the local (non-clustered) instance of SQL Server.
 * 2) Manually change the SqlLogConnectionString registry entry under the HKLM\Software\Microsoft\Host Integration Server\Data Integration key to point to the clustered SQL Server database.

The registry entry will appear similar to the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Host Integration Server\Data Integration\SqlLogConnectionString (REG_SZ) :

Provider=SQLOLEDB

Server=

Database= MSHIS60_DATA

Integrated Security=SSPI

You can create your own .reg file, and then merge the .reg file into the registry on each of your servers that are running Host Integration Server. If you do this, the data should be the same for each server.

The Server= setting must point to the computer name of your instance of SQL Server. The following is a sample .reg file. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Host Integration Server\ Data Integration] &quot; SqlLogConnectionString&quot;=&quot;Provider=SQLOLEDB;Server= ServerName ;Database=MSHIS60_DATA;Integrated Security=SSPI&quot; Host Integration Server 2004 is not cluster-aware. Therefore, you cannot install Host Integration Server 2004 as a resource. However, you can install Host Integration Server 2004 on each node.

For more information about Host Integration Server load balancing and Cluster service environments, click the following article numbers to view the articles in the Microsoft Knowledge Base:

128244 SNA Server load balancing and hot backup

190151 SNA Server in a Cluster Server environment

231865 SNA Server interoperability with Windows Load Balancing

909370 How to install Host Integration Server 2004 Transaction Integrator in a clustered SQL Server environment

Keywords: kbhowto kbinfo kbhis2004 KB910312

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.