Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Failover Engine (FoE) > Failover Engine Service will not start because it is configured for NA + DR Trio in Server Configuration

Failover Engine Service will not start because it is configured for NA + DR Trio in Server Configuration

Created by Michael Almadova, last modified by Daniel Polaske on Nov 02, 2016

Views: 5 Votes: 0 Revisions: 10

Updated

Overview

Failover Engine Service will not start because it is configured for NA + DR Trio in Server Configuration. Error seen in event viewer Application logs:

SWREFID: 1195 or SWREFID: 985 

Environment

FOE 6.7

Resolution

 

 

Resolution 1:

 

In this scenario, the secondary server was Active and running without issues. The Primary server was the issue and was somehow setup in a NA + DR Trio configuration with SWREFID: 1195

 

 

  1. Download the latest FOE installer (6.7) from the Customer Portal and copy it to the Primary Failover Engine server.
  2. Running the installer should ask you to uninstall FOE first.  First uninstall Failover Engine, choosing the option to leave the server on the network, and then reboot the server as requested.
  3. You may now run the install as normal, again on the Primary Failover Engine server.
  4. First, change the IP addresses of both the public and the channel network adapters to any non-conflicting IP address other than what was used previously.  This will be done temporarily to allow the installation to continue and will be reverted back when the installation is complete.  This will then be used in the SolarWinds Failover Engine Setup when configuring the Network Adapters settings.  In addition to using a temporary, local pre-clone folder- you will also want to skip validation when the Setup reports that the Primary cannot access the secondary.
  5. After the install completes open Server Configuration application.
  6. Change the NIC settings back to the correct IP settings as used before the problem surfaced.
  7. Adjust the IP's to match the setup as well.
  8. Failover Engine should now start and connect back to the secondary server that is active.
  9. Once this is complete, you may need to repeat the above process on the Secondary to make sure the Solarwinds Failover Engine service starts again.

 

Resolution 2:

 

In this scenario, the Primary server was Active and running without issues. The secondary server was the issue and was somehow setup in a NA + DR Trio configuration throwing a license error SWREFID: 985 

 

1. Download the latest FOE installer (6.7) from the Customer Portal and copy it to the Primary Failover Engine server.

2. Running the installer should ask you to uninstall FOE first.  First uninstall Failover Engine, choosing the option to leave the server on the network, and then reboot the server as requested.

3. You may now run the install as normal, again on the Secondary Failover Engine server.

 

 

 

Last modified
14:32, 2 Nov 2016

Tags

Classifications

Public