Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

Home > Success Center > Failover Engine (FoE) > Loss of FOE registry configuration information after updating FOE servers with Java 8 update 60

Loss of FOE registry configuration information after updating FOE servers with Java 8 update 60

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 617 Votes: 1 Revisions: 11

Overview

Loss of registry configuration information may occur as a result of updating SolarWinds Orion Failover Engine servers with the x86 version of Java 8 Update 60.  

Environment

  • FoE any version

Cause 

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.

 

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

Resolution

Prevent the registry configuration loss of the FoE

Follow this procedure 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. Shut down the SolarWinds Failover Engine 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 (double-click the file in 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.

Correct the loss of registry configuration on the active server

Follow these steps to correct the loss of registry configuration on the active server when the passive server has not experienced the registry configuration loss.

 

  1. Shut down the SolarWinds Failover Engine using the Service Control Manager.


     
  2. Using Regedit on the passive server, export the registry key HKLM\Software\JavaSoft\Prefs\Neverfail to a file.
  3. Copy the file onto the active server.
  4. Import the file into the registry of the active server.
  5. 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.
  6. Start SolarWinds Failover Engine on the passive server.
  7. Start SolarWinds Failover Engine on the active server.

Correct the loss of registry configuration on the passive server

Follow these steps to correct the loss of registry configuration on the passive server when the active server has not experienced the registry configuration loss.

 

  1. Shut down the SolarWinds Failover Engine using the Service Control Manager.


     
  2. Using Regedit on the active server, export the registry key HKLM\Software\JavaSoft\Prefs\Neverfail to a file.
  3. Copy the file onto the passive server.
  4. Import the file into the registry of the passive server.
  5. 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.
  6. Start SolarWinds Failover Engine on the passive server.
  7. Start SolarWinds Failover Engine on the 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.   

 

 

Last modified
19:29, 22 Jun 2016

Tags

Classifications

Public