Environment
Reflection for Secure IT Server for Windows 8.2 SP1 U1
Situation
Reflection for Secure IT Windows Server (RSIT) is installed and running on a Windows 2012 R2 Failover Cluster. After an upgrade from version 8.2.1.x to build 8.2.1.1100, the sshconsole crashes with the following message:
“Secure Shell Server Configuration Tool has stopped workingâ€
Problem details:
Problem Event Name: APPCRASH
Application Name: sshconsole.exe
Application Version: 8.2.1100.0
…
Fault Module Name: MSVCR100.dll
Problem only effects the sshconsole. Micro Focus Reflection for Secure IT server service continues to work correctly within the Failover Cluster.
“Secure Shell Server Configuration Tool has stopped workingâ€
Problem details:
Problem Event Name: APPCRASH
Application Name: sshconsole.exe
Application Version: 8.2.1100.0
…
Fault Module Name: MSVCR100.dll
Problem only effects the sshconsole. Micro Focus Reflection for Secure IT server service continues to work correctly within the Failover Cluster.
Resolution
Workaround:
1. In Failover Cluster Manager, expand the cluster RSIT is running under, click on Roles.
2. Select the RSIT role/Generic Service that RSIT is configured under. Take note of the IP address.
3. Right click on the same role and choose properties. Take note of the settings under both General and Failover tabs. Click OK.
4. Left pane, Storage, Disks, check if any disk(s) are currently assigned to the RSIT role.
5. Right click on the role and choose “Stop Roleâ€.
6. Right click on role and select “Removeâ€.
7. On the passive server, use Control Panel to uninstall RSIT, reboot.
8. On the active server, use Control Panel to uninstall RSIT, reboot.
9. Install RSIT build 8.2.1.1100 on the passive server, reboot.
10. Verify that RSIT service is not running under Windows’ Services.
11. Install RSIT build 8.2.1.1100 on the active server, reboot.
12. Verify that RSIT service is not running under Windows’ Services.
13. In Failover Cluster Manager, expand the cluster RSIT will run under.
14. Right click on Roles and choose “Configure Roleâ€.
15. Under “Select Roleâ€, choose “Generic Servicesâ€. Click Next.
16. Choose “Micro Focus Reflection for Secure IT Server†from the list.
17. Enter a name for the Cluster role and the IP address it is using (Step 2).
18. When prompt to “Replicate Registry Settingsâ€, add this HKEY_LOCAL_MACHINE key: SOFTWARE\Micro Focus\RSecureServer
19. Check the new RSIT role properties, match it to what was noted (step 3).
20. On the active server, ensure that the RSIT console opens.
21. Test the connect.
22. Failover to passive server, test step 20 and 21 on the new active server.
1. In Failover Cluster Manager, expand the cluster RSIT is running under, click on Roles.
2. Select the RSIT role/Generic Service that RSIT is configured under. Take note of the IP address.
3. Right click on the same role and choose properties. Take note of the settings under both General and Failover tabs. Click OK.
4. Left pane, Storage, Disks, check if any disk(s) are currently assigned to the RSIT role.
5. Right click on the role and choose “Stop Roleâ€.
6. Right click on role and select “Removeâ€.
7. On the passive server, use Control Panel to uninstall RSIT, reboot.
8. On the active server, use Control Panel to uninstall RSIT, reboot.
9. Install RSIT build 8.2.1.1100 on the passive server, reboot.
10. Verify that RSIT service is not running under Windows’ Services.
11. Install RSIT build 8.2.1.1100 on the active server, reboot.
12. Verify that RSIT service is not running under Windows’ Services.
13. In Failover Cluster Manager, expand the cluster RSIT will run under.
14. Right click on Roles and choose “Configure Roleâ€.
15. Under “Select Roleâ€, choose “Generic Servicesâ€. Click Next.
16. Choose “Micro Focus Reflection for Secure IT Server†from the list.
17. Enter a name for the Cluster role and the IP address it is using (Step 2).
18. When prompt to “Replicate Registry Settingsâ€, add this HKEY_LOCAL_MACHINE key: SOFTWARE\Micro Focus\RSecureServer
19. Check the new RSIT role properties, match it to what was noted (step 3).
20. On the active server, ensure that the RSIT console opens.
21. Test the connect.
22. Failover to passive server, test step 20 and 21 on the new active server.