IBM Support

Fresh installation of Image Services on Windows Microsoft Cluster (MSCS)

Troubleshooting


Problem

(Known issue) When you try to install IBM FileNet Image Services in the following environments, the installation program does not recognize a cluster shared drive as a shared drive when the resource name of the shared drive begins with 'Cluster Disk', which is the default Microsoft Windows 2008 Cluster prefix:
Image Services 4.1.2 or 4.2.0 in the following environment:
  • Windows 2008 or Windows 2008 R2 (32-bit or 64-bit), or
  • Windows Server 2012 or Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022
Image Services 4.2.0 in the Windows 2003 R2 cluster environment

Symptom

By default, Microsoft Windows 2008 or Windows 2008 R2 Cluster software names a cluster shared drive with the cluster resource name beginning with 'Cluster Disk'. This naming convention prevents the Image Services installation program from recognizing the drive as a shared drive.

Note
The examples in this document use Windows 2008 and Windows 2008 R2, but the principles and scenarios mentioned here also apply to the Windows 2012, Windows 2012 R2, Windows 2016, Windows 2019 and Windows 2022 environments.

Issues

  1. The Image Services 4.1.2 or 4.2.0 installation programs do not recognize the cluster disk on which the shared folder fnsw_loc for Image Services is to be created.
  2. When installing Image Services 4.2.0, an error message is generated about the database type Db2 not being supported even when the RDBMS database MS-SQL is selected.
  3. After the Image Services 4.2.0 installation is completed, the 'ClusterName' entry is missing in the Windows registry.
  4. On Windows Cluster 64-bit, Image Services 4.2.0 fails to load fn_autoconfig when Image Services is started.
Workaround in Image Services 4.1.2
To resolve this issue and any other issues that might occur during a fresh installation of Image Services 4.1.2 in a Windows 2008 or Windows 2008 R2 (32-bit or 64-bit) cluster environment, perform the following:
  1. Change the cluster disk for fnsw_loc to the name that the Image Services installation program can recognize:
    1. Start the Failover Cluster Manager from Administrative Tools. Under Failover Cluster Manager,
      expand the cluster system intended for Image Services and select Storage.
    2. Right-click the Cluster Disk intended for the shared folder fnsw_loc and select Properties on the
      Summary of Storage.
    3. Change the Resource Name from 'Cluster Disk #' to 'Disk x:' on the Cluster Disk Properties, where x is the drive letter where the fnsw_loc shared folder is located. The drive letter MUST be in lower case.
      Click OK to close the window.
  2. Start the Image Services 4.1.2 installation program.
    See the IBM FileNet Image Services High Availability Procedures and Guidelines for 4.1.2 document available on Product Documentation for IBM FileNet Image Services to finish the installation and configuration.
Workaround in Image Services 4.2.0
To resolve this issue and any other issues that might occur during a fresh installation of Image Services 4.2.0 in any supported Windows cluster environment, perform the following:
  1. Run the following command to start the Image Services installation program:
    is_4.2.0_win.exe –D$USE_DC$=Windows domain name
    Where Windows domain name is the name of the Windows domain that a domain user belongs to and that will be used for starting or stopping the IS Control Service.
    For example, if the domain user is \isqa\fnsw, the Windows domain name is isqa.
  2. Perform the installation as if the Image Services system were a non-clustered system:
    1. Do not select the Enable cluster support check box.
    2. Do not select the Enable auto-start IS check box.
  3. When the installation completes, select No, restart the server later.
    Click OK to exit the installation program.
  4. Run the regedit.exe to open the Windows registry:
    Windows 32-bit: Select the HKEY_LOCAL_MACHINE\Software\FileNet\IMS\CurrentVersion folder.
    Windows 64-bit: Select the HKEY_LOCAL_MACHINE\Software\Wow6432Node\FileNet\IMS\CurrentVersion folder.
  5. Create a new String Value 'ClusterName' as Value name and specify the cluster network name used for Image Services.
  6. Restart the cluster node and repeat the previous steps on the other cluster node.
  7. Refer to the IBM FileNet Image Services High Availability Procedures and Guidelines for 4.2.0 document available on Product Documentation for IBM FileNet Image Services to finish the rest of the system configuration.
  8. Windows 64-bit Cluster: Before starting Image Services (by running the initfnsw start command), create an empty file and name it no_autoconfig.txt in the \fnsw_loc\sd folder.

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVUD","label":"FileNet Image Services"},"ARM Category":[{"code":"a8m50000000Cdy8AAC","label":"FileNet Image Services"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.1.2;4.2.0"}]

Document Information

Modified date:
14 October 2022

UID

swg21499534

Page Feedback