Clustering ConnectR

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Revision as of 20:50, 30 November 2012 by Joe.Nyiri (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


  1. Before you begin, you must install the cluster and SQL server properly and ensure they are working normally on each node.
  2. You must also set the "Lock Pages in Memory" setting for the service account you are using for SQL.


Note that there is a utility located at C:\Program Files\IDX Systems Corporate\IDXConnectR v4.6\Processing\ClusterSetup.exe that can be run to avoid having to do some of the manual configuration below. This utility allows you to setup the cluster resource.


  1. Install ConnectR 4.6 following the above steps onto each node.
  2. The ServerDefinition table should be configured to use the SQL cluster name.
  3. Roll the cluster groups onto the active node you are installing into.
  4. Ensure it is working properly on each node.
  5. To cluster, set the IDXConnectR service to start manually on each node.
  6. Open the cluster administrator and create the following resource in the SQL Group.
  7. This must be in the same cluster group as the network name that is being used. This should be the SQL Server instance name.
  8. This service must be brought online and offline using cluster administrator. It will give you an error if you do it in the application or via the local services control page on each node.
  9. Set up and cluster the IDXConnectR service resource:
Type: Generic Service
Dependency: SQL Server, SQL IP Address, SQL Network Name
Service Name: IDXConnectR System Service4.0
Parameters: Check the box to Use Network Name as computer name
Registry Options: No Registry Copying, just click finish

Registry Settings

Registry settings that have to exist for System Service to fail over correctly on a cluster:

  • System Service Config (Front End) has to be saved on both nodes to save DSN, username and password to registry on each node. These 3 values should match on both nodes. You should also verify the DSN is set up correctly as well.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IDXConnectR System Service4.0\Parameters\Datasource
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IDXConnectR System Service4.0\Parameters\Password
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IDXConnectR System Service4.0\Parameters\Username
  • This value should also exist for a cluster:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IDXConnectR System Service4.0\Environment
  • If the above value does not exist, create it as a new multi-string value. The format of the value is shown below:
  • If the ConnectR server does not have SQL running, you need to disable that dependence.
  1. On both nodes open the registry.
  2. Add the value.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IDXConnectR System Service4.0\Parameters\NoDependencyFlag 
DWORD value = 1.


Symptoms: Interfaces will not start.

Cause: If the Connectr server is part of a cluster, and it does not have sql you must remove the dependency on sql

Resolution: Registry settings that have to exist for System Service to fail over correctly on a cluster. See above.