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

[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

MORE INFORMATION

When you use TI with a clustered SQL Server database, you must follow these steps because the Host Integration Server 2004 Configuration Wizard is not designed to work with clustered servers that are running instances of SQL Server. To use TI with a clustered SQL Server environment, follow these steps:

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_HIP on the clustered instance of SQL Server.
2. Create HIS Administrators and HIS Runtime local user groups on each node in the cluster.
3. Create HISAdmin and HISRuntime roles in the newly created database.
4. On each node in the cluster, add the HIS Administrators and HIS Runtime user groups as logins to the newly created database. Additionally, add the user groups to the HISAdmin or HISRuntime role as appropriate.
5. Run the HIPTables.sql script to create the tables and the stored procedures in the database.
   
   Note By default, the HIPTables.sql script is located in the following folder:

   %root%\Program Files\Microsoft Host Integration Server\system\HIPTables.sql

6. Run the Host Integration Server 2004 Configuration Wizard on the host-initiated processing (HIP) server. First point the Host Integration Server 2004 Configuration Wizard to the local (non-clustered) instance of SQL Server.
7. Manually change the ConnectionString registry entry under the HKLM\Software\Microsoft\Host Integration Server\HIP 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\HIP\ConnectionString (REG_SZ):
   Provider=SQLOLEDB
   Server=ServerName
   Database=MSHIS60_HIP
   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 an example .reg file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Host Integration Server\HIP]
"ConnectionString"="Provider=SQLOLEDB;Server=ServerName;Database=MSHIS60_HIP;Integrated Security=SSPI"

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 server environments, click the following article numbers to view the articles in the Microsoft Knowledge Base: However, Transaction Integrator (TI) can be deployed as a cluster resource . For more information about how to cluster TI COM components, visit the following Microsoft Web site:Note This white paper only applies to Windows Initiated Processing (WIP) for TI COM.

If you are just going to use WIP with clustering, we recommend that you view this white paper. In this case, you do not have to cluster the Host Integration Server database because WIP configurations are not stored in the database. The Host Integration Server database is only needed by WIP to start TI Manager.

If you are only going to use HIP, we recommend that you cluster the MSHIS60_HIP database. You do not have to make any specific configuration changes in Host Integration Server to cluster HIP components. Just make sure that the incoming requests are routed to a listening HIP service. To do this, use Windows Load Balancing (WLB), Network Load Balancing (NLB), or clustering. If you must have redundancy for the HIP service, typically WLB or NLB is used.

Note If you change the server name after you install and configure Host Integration Server 2004 TI, you must update the MSHIS60_HIP database by using the new server name. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: