SolarWinds - Resolve an invalid Orion Failover Engine License



This Knowledge Base article discusses the occurrence of an invalid Orion Failover Engine license including the symptoms, causes, and resolutions.

More Information

The Orion Failover Engine license is generated using the HBSIG (Heartbeat Signature) of the host machine. This unique signature is generated by examining select components on the primary server. The license key must match the HBSIG in order to be seen as valid.


During normal operations, you receive an error message stating your Orion Failover Engine license key has expired or Orion Failover Engine fails to start after rebooting the server or stopping Orion Failover Engine.


A license key can become invalid for any of the following reasons:

  • The domain name of the server has been changed.
  • The server has been removed from the domain and re-added.
  • The Security Identifier (SID) has been changed.
  • A new plug-in has been installed since the last license key was generated.

The Orion Failover Engine license has expired:

Should a licensing problem arise during an implementation, SolarWinds may provide a temporary or time-limited license so that the implementation can proceed. Temporary or time-limited licenses have a defined expiration date, and when the date is exceeded, will not allow Orion Failover Engine to start.

Windows Management Instrumentation (WMI) hung or not running:

Orion Failover Engine uses WMI to validate the license on the primary server and if WMI is hung or not running, validation cannot complete.


  1. If the cause of the invalid license key is the result of a change to the domain credentials of the server, the addition of a new plug-in, or expiration of a temporary or time-limited Orion Failover Engine license key, simply request a new license key for the primary server from SolarWinds Support Representative.
  2. If the cause of an invalid license error is not the result of a domain credentials change, or expiration of a temporary or time-limited Orion Failover Engine license key, check the Windows Services and ensure that WMI is running. If WMI is running, stop the WMI Service, restart it, and then attempt to start Orion Failover Engine.

Applies To

All Versions

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.