Configuration Wizard error "Connection to Business Layer Service did not succeed" caused by Feature Service "License Mismatch" after migrating the SolarWinds Platform server to a new host

7/3/2026 9:29 PM

7/7/2026 4:19 PM

When you launch the Configuration Wizard (typically after an upgrade, a server migration, or a repair), it runs a series of verification tasks. On an affected server, the wizard completes the SolarWinds Information Service (SWIS) check successfully but then fails at the SolarWinds Orion Module Engine check after a long retry window (approximately 15 minutes), and the wizard is canceled.

What you see in the user interface

• The Configuration Wizard displays: Verifying that the SolarWinds Orion Module Engine is available FAILED
• The error dialog reports: Services configuration failed: Connection to Business Layer Service did not succeed.
• The web console may be inaccessible, or SolarWinds services may fail to start or stay running.

What you see in the logs

The failure is a chain that starts in the Feature Service, propagates to the Business Layer Host, and finally surfaces in the Configuration Wizard. Log messages are shown below with generic hostnames, IP addresses, ports, and timestamps.

ConfigurationWizard.log (the top-level symptom):

2026-01-01 10:15:22,000 [x] INFO  ExecutionEngine - Executing task Orion.EnsureBusinessLayerIsAvailable
2026-01-01 10:30:58,000 [x] ERROR SWEventLogging - Connection to SolarWinds Business Layer service did not succeeded after 18 retries. Please start SolarWinds Business Layer Service
2026-01-01 10:30:58,000 [x] DEBUG CoreBusinessLayerApiProxyFactory - Failed to connect to Core BL on engine 1. Error: ...TransientApiProxyException
2026-01-01 10:30:58,000 [x] ERROR System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://SERVER-HOSTNAME.example.local:17777/orion/core/businesslayer that could accept the message.
2026-01-01 10:30:59,000 [x] ERROR ExecutionEngine - Task Orion.EnsureBusinessLayerIsAvailable failed. Configuration Wizard has been canceled. Aborting...

BusinessLayerHost.log (the service that never comes up):

2026-01-01 10:20:00,000 [x] INFO  LicenseSeverAvailabilityAwaiter - Waiting for License Server...
2026-01-01 10:30:00,000 [x] ERROR LicenseSeverAvailabilityAwaiter - Maximal waiting time for License Server was exceeded - 00:10:00
2026-01-01 10:30:00,000 [x] FATAL BusinessLayerHostService - Failed to initialize: Error retrieving features from Feature Service on port 17734: ...Exception was thrown by handler

SolarWinds.Feature.Service.log (the true origin of the failure):

2026-01-01 10:20:05,000 [x] ERROR FeatureMapper - License Mismatch
System.InvalidOperationException: License Mismatch
Feature Mapper Variables:
    IsSocInRegistry = False
    IsAnyActiveLicensePresent = True
    IsSocLicenseFeatureActive = True

What is happening (in plain terms)

The failure looks like a network or service problem on port 17777, but it actually starts in the licensing layer:

1. The Feature Service cannot agree on the server's license state, so it stops responding to requests.
2. Because of that, the Business Layer Service cannot finish starting and never opens its endpoint on port 17777.
3. The Configuration Wizard waits for that endpoint, never finds it, and cancels after its retry window.

The important takeaway: this is a licensing state problem, not a network, firewall, or database problem. Once the licensing state is corrected, the Business Layer starts and the Configuration Wizard completes automatically.

Hybrid Cloud Observability

This issue is caused by a mismatch between the local license store and the server's registry/installation state. In the affected scenario, this most commonly occurs after the SolarWinds Platform server is migrated to a new server or given a new hostname.

Common contributing conditions:

• The license store files (lease.dat and license.dat) were carried over from, or activated under, a previous server, and no longer match the fresh installation's registry state on the new host.
• An Observability / subscription (SOC) license feature is flagged active in the license store, while the new installation's registry reflects a standard (non-SOC) install, producing the IsSocInRegistry = False while IsSocLicenseFeatureActive = True condition.
• A leftover or expired evaluation license is present in the store alongside perpetual/commercial module licenses, leaving the licensing state in a conflicting, half-applied condition.
• The database from a previous installation was reused, so the stored license assignments do not match the new server identity.

In short: the license store and the registry disagree about the server's license state after the move, and the Feature Service will not serve features until they match.

Resetting the local license store and reactivating the correct license clears the mismatch. Perform the steps in order and verify after each stage.

Before you begin:

• Take a backup / snapshot of the server if possible.
• Have your correct commercial/perpetual (or subscription) license keys available for reactivation.
• Confirm whether this server has internet access to the SolarWinds activation servers, or whether you must use offline/manual activation.

Step 1 — Stop all SolarWinds services

1. Open SolarWinds Platform Service Manager on the affected server.
2. Choose Shutdown Everything and wait until all services are stopped.

Step 2 — Back up and remove the local license store files

1. Navigate to C:\ProgramData\SolarWinds\.
2. Move (do not just copy) the following files to a backup folder outside of C:\ProgramData\SolarWinds\:
• lease.dat
• license.dat
3. This forces the licensing subsystem to rebuild a clean local store on next start.

Step 3 — Start services and re-check

1. In SolarWinds Platform Service Manager, choose Start Everything.
2. Wait 1 to 3 minutes for the services to initialize.
3. Review SolarWinds.Feature.Service.log and confirm the License Mismatch errors have stopped and a normal feature map is applied. A healthy, clean install shows the flags in agreement, for example:
   

    Feature Mapper Variables:
        IsSocInRegistry = False
        IsAnyActiveLicensePresent = False
        IsSocLicenseFeatureActive = False
    Full Feature Map is applied

Step 4 — If the mismatch persists, expire the license store

1. Stop all services again (SolarWinds Platform Service Manager, Shutdown Everything).
2. Open a Command Prompt as Administrator and change to the SolarWinds Platform install folder (for example, C:\Program Files\SolarWinds\Orion\).
3. Run:
   

    migration.exe /ExpireAll

4. This expires and resets the license activation state. The server will temporarily fall back to evaluation licenses, which allows the Business Layer to start.
5. Start all services again.

Step 5 — Reactivate the correct license

1. Open License Manager on the server.
2. Reactivate only the intended commercial/perpetual (or subscription) licenses so that the store and registry are consistent. Do not reintroduce a stray or expired evaluation license.
3. If the server has no internet access to the SolarWinds activation servers, use the offline / manual activation method.
4. Confirm in SolarWinds.Feature.Service.log that IsAnyActiveLicensePresent becomes True and the intended modules are reported as Licensed (not Evaluation).

Step 6 — Re-run the Configuration Wizard

1. Launch the Configuration Wizard and complete the Database, Services, and Website steps.
2. The Business Layer Service now binds on net.tcp://SERVER-HOSTNAME.example.local:17777/orion/core/businesslayer, the Orion Module Engine check passes, and the wizard completes successfully:
    The configuration wizard completed successfully

Important — do not manually edit database tables:

Do not attempt to fix this by editing the Engines, OrionServers, or Licensing_LicenseAssignments tables (for example, swapping ServerName/IP/ServerType values or deleting engine rows). The EngineID (Engines table) and OrionServerID (OrionServers table) are separate, independently numbered identifiers; a matching number in each table can refer to two different servers (for example, the main poller versus a remote collector). License assignments reference the OrionServers table, not the Engines table, so hand-editing these tables does not fix the mismatch and can break polling and referential integrity. Manual edits to the SolarWinds database are unsupported.

Post-resolution note:

After running migration.exe /ExpireAll, the server runs on evaluation licenses until you reactivate. Reactivate your commercial licenses promptly (Step 5) to avoid a later evaluation-expiry outage.