SolarWinds Failover Engine - Updating SolarWinds Failover Engine Servers with Java 8 Update 60 May Result in the Loss of SolarWinds Failover Engine Registry Configuration Information

Follow

Summary

This Knowledge base article provides information about the loss of registry configuration information that may occur as a result of updating SolarWinds Failover Engine servers with the x86 version of Java 8 Update 60.


More Information

After updating SolarWinds Failover Engine servers with Java 8 Update 60, some users have reported loss of registry configuration information on their system. Investigation of the issue has identified that the Java 8 Update 60 installer may inadvertently uninstall all HKLM\SOFTWARE\JavaSoft registry keys which are normally preserved during the upgrade process.

Important: If you have not yet upgraded to JAVA 8 Update 60, use the procedure listed below. If you have attempted to upgrade a single server and experienced a loss of registry configuration information, perform the procedure below on the appropriate server to resolve the issue.

As a result, the loss of registry configuration information on the SolarWinds Failover Engine system may require a complete redeployment of the server cluster(s).

To Prevent the SolarWinds Failover Engine Registry Configuration Loss:

To prevent registry configuration loss and safely update your x86 version of Java to jre-8u60-windows-i586

Note: These steps are NOT necessary for upgrading the jre-8u60-windows-x64 , but ARE necessary for uninstalling it.

  1. Stop the SolarWinds Failover Engine Service and SolarWinds Failover Engine Web Service services using the Service Control Manager.
  2. Using Regedit (the Registry Editor), export HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs to a file.
  3. Install (or uninstall as appropriate) your JRE.
  4. Import the exported registry file (just double-click from explorer).
  5. Start the SolarWinds Failover Engine Service and SolarWinds Failover Engine Web Service services using the Service Control Manager on all servers in the cluster.

If Registry Configuration Loss Occurs on the Active Server:

To correct the loss of registry configuration on the active server when the passive server has not experienced the registry configuration loss:

  1. Shutdown SolarWinds Failover Engine on the active server.
  2. Shutdown SolarWinds Failover Engine on passive server
  3. Using Regedit, export the registry key HKLM\Software\JavaSoft\Prefs\Neverfail from the passive server.
  4. Copy the <%name%>.reg file onto the active server.
  5. Import the <%name%>.reg file into the registry of the active server.
  6. Change the registry HKEY value on the active server to the following: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\neverfail\current\/Controller
    • value /is/Active/Partition from false to true .
    • value /Replication/Enabled from false to true .
  7. Start SolarWinds Failover Engine on passive server.
  8. Start SolarWinds Failover Engine on active server.

If Registry Configuration Loss Occurs on the Passive Server:

To correct the loss of registry configuration on the passive server when the active server has not experienced the registry configuration loss:
  1. Shutdown SolarWinds Failover Engine on the passive server.
  2. Shutdown SolarWinds Failover Engine on active server.
  3. Using Regedit, export the registry key HKLM\Software\JavaSoft\Prefs\Neverfail from the active server.
  4. Copy the <%name%>.reg file onto the passive server.
  5. Import <%name%>.reg file into the registry of the passive server.
  6. Change the registry HKEY value on the passive server to the following: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\neverfail\current\/Controller
    • value /is/Active/Partition from true to false .
    • value /Replication/Enabled from true to false .
  7. Start SolarWinds Failover Engine on passive server.
  8. Start SolarWinds Failover Engine on active server.

Note: If a trio is deployed and the tertiary server is passive, repeat the procedure for when registry configuration loss occurs on the active server and treat the tertiary as the passive server.


Applies To

SolarWinds Failover Engine v6.7.x


Related Information

None

KBID-2900

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.