Configuration Wizard fails with ‘Connection to Business Layer Service did not succeed’ because Feature Service is using an unsupported TLS protocol during upgrade to 2026.1 in Solarwinds Self-Hosted Platform

This article discusses an issue where the SolarWinds Configuration Wizard fails at “Verifying that the SolarWinds Orion Module Engine is available FAILED” and “Connection to Business Layer Service did not succeed. Last error: Exception of type ‘SolarWinds.ApiProxyFactory.TransientApiProxyException’ was thrown.”

From Business Layer Host log:

2026-03-16 15:44:41,090 [8] FATAL SolarWinds.BusinessLayerHost.BusinessLayerHostService - Failed to initialize: System.Exception: Failed to retrieve features from Feature Service: The requested security protocol is not supported. ---> System.NotSupportedException: The requested security protocol is not supported.
at System.Net.Http.HttpClientHandler.SecurityProtocol.ThrowOnNotAllowed(SslProtocols protocols, Boolean allowNone)

Feature Service gRPC client is attempting to use an unsupported TLS protocol (for example SSL 3.0) as defined in the SolarWinds SecurityProtocols settings and/or Windows SChannel. This causes a System.NotSupportedException: The requested security protocol is not supported. in GrpcWebClientWithCertificateManagementFactory, prevents Business Layer from retrieving features, and stops the Business Layer Host from initializing.

A. Resolution when Advanced Configuration is accessible (recommended pre‑upgrade)

Use this path if the web console still works and you can open Advanced Configuration / Centralized Settings before running the upgrade or Configuration Wizard.

1. Enable TLS 1.2 in Windows SChannel (OS level)

•  Open regedit.
• Ensure these keys exist (create if necessary):
• HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
• HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server
• In each key, set:
• Enabled (REG_DWORD) = 1
• DisabledByDefault (REG_DWORD) = 0

Repeat on all scalability engines(APEs, HA Standbys, Additional Web Servers).

2. Disable unsupported protocols in SChannel

1. Under the same Protocols hive, ensure SSL 3.0 are disabled according to your security policy, for both Client and Server subkeys.

   • Typical pattern: Enabled = 0, DisabledByDefault = 1.

2. Reboot the server if you changed SChannel protocol keys.

Repeat on all scalability engines.

Alternative Tool

1. Log in to the computer hosting SolarWinds Platform Server as an administrator.

2. Download and install IIS Crypto from Nartac.

3. Open the tool.

4. Click on Best Practices
5. Make sure TLS 1.2 is only enabled in Server and Client
6. Reboot the server
7. Repeat steps 3-7 on all SolarWinds servers (on the HA backup of the main polling server if available, then on any additional polling servers, additional web servers, and any other HA servers).

2. Disable SSL 3.0 / unsupported protocols in the Centralized Settings via Advanced Configuration

• In a browser, open Advanced Configuration on the main poller:

  • http://<orion-server>/Orion/Admin/AdvancedConfiguration/Global.aspx

• In the search/filter, locate section:
  SolarWinds.Orion.SecurityProtocols

• Adjust the settings:

  • Uncheck  or set to False:
    
    • EnableSsl3
    • (Optional hardening) EnableTls10, EnableTls11
  • Ensure checked or set to True:
    
    • EnableTls12
• Save the changes in Advanced Configuration.

3. Run the upgrade / Configuration Wizard.

B. Resolution when Advanced Configuration is NOT accessible (Configuration Wizard already failing) 

Use this path when the upgrade has already started, Configuration Wizard is failing at Services, and the web UI or Advanced Configuration page is no longer accessible. 

1. Ensure TLS 1.2 is enabled in SChannel

Same as in Scenario A:

• Confirm TLS 1.2 Client/Server keys exist and are enabled (Enabled = 1, DisabledByDefault = 0).
• Confirm SSL 3.0  are disabled at the OS level if applicable.

2. Disable SSL 3.0 in SolarWinds SecurityProtocols via SQL query

1. Connect to the SolarWinds Platform server.
2. Open Database Manager from the SolarWinds Platform folder of the start menu.
3. Select Add Orion Server and expand the SQL server in bold.
4. Right-click the SolarWindsOrion database and select New Query.
5. Paste the SQL query below into the window on the right and select Execute query:

--Note: Replace <OrionServerID> with the OrionServerID of the MainPolling Engine from OrionServers table

Insert INTO SettingOverride VALUES('SolarWinds.Orion.SecurityProtocols.EnableSsl3',<OrionServerID>,'False')

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

3. Remove stale Settings cache 

On the main poller,

Make sure all services are stopped

Delete C:\ProgramData\SolarWinds\Settings\Settings.json
This forces Settings.json to be regenerated from Centralized Settings / DB on next service start, so DB changes take effect.

4. Re‑run Configuration Wizard 

Expected outcome:

• Business Layer Host now initializes without:
  • System.NotSupportedException: The requested security protocol is not supported.
  •  Configuration Wizard finishes the Services step successfully.

At this point, Advanced Configuration should be accessible. Disable SSL 3.0  unsupported protocols via Advanced Configuration. Please follow A. 2. Disable SSL 3.0 / unsupported protocols in the Centralized Settings via Advanced Configuration.

C. If the Configuration Wizard continues to fail.

- Review the Feature Service log, as you may observe the following entry:

2026-04-13 12:10:59,368 [.NET TP Worker] ERROR SolarWinds.Orion.Feature.Service.Mapping.FeatureMapper - (null)	 License Mismatch
2026-04-13 12:10:59,372 [.NET TP Worker] ERROR Grpc.AspNetCore.Server.ServerCallHandler - (null)	 Error when executing service method 'GetFeatures'.

- Review the Business Layer logs as you may observe the following entry:

2026-04-13 12:21:25,883 [10] ERROR SolarWinds.BusinessLayerHost.LicenseSeverAvailabilityAwaiter - Maximal waiting time for License Server was exceeded - 00:10:00. Rethrowing the original exception.
2026-04-13 12:21:25,883 [10] FATAL SolarWinds.BusinessLayerHost.BusinessLayerHostService - Failed to initialize: System.Exception: Error retrieving features from Feature Service on port 17734: Unknown ---> Grpc.Core.RpcException: Status(StatusCode="Unknown", Detail="Exception was thrown by handler.")
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Grpc.Net.Client.Internal.HttpClientCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method`2 method, String host, CallOptions options, TRequest request)
   at Grpc.Core.Interceptors.InterceptingCallInvoker.<BlockingUnaryCall>b__3_0[TRequest,TResponse](TRequest req, ClientInterceptorContext`2 ctx)
   at Grpc.Core.ClientBase.ClientBaseConfiguration.ClientBaseConfigurationInterceptor.BlockingUnaryCall[TRequest,TResponse](TRequest request, ClientInterceptorContext`2 context, BlockingUnaryCallContinuation`2 continuation)
   at Grpc.Core.Interceptors.InterceptingCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method`2 method, String host, CallOptions options, TRequest request)
   at SolarWinds.Feature.Service.FeatureCatalog.FeatureCatalogClient.GetFeatures(GetFeaturesRequest request, CallOptions options)
   at SolarWinds.Feature.Service.FeatureCatalog.FeatureCatalogClient.GetFeatures(GetFeaturesRequest request, Metadata headers, Nullable`1 deadline, CancellationToken cancellationToken)
   at SolarWinds.Orion.Feature.Client.Service.GrpcFeatureProviderAdapter.GetFeatures(OrionServerLicenseContext featureSet)

Perform the following steps to resolve the issue:

1. Stop All SolarWinds Service Manager Services
2. Locate the License Files

• Navigate to: C:\ProgramData\SolarWinds\
• Find the files named: lease.dat and license.dat

3. Move the Files to a Backup Location

• Copy or move these files to a different folder, e.g. Downloads, Backup, or another safe location.

4. Restart All SolarWinds Services

• Using SolarWinds Service Manager, start all previously stopped services.
• Wait about 1-3 minutes to give the services a chance to start up

5. Access the Web Console

• Open up the Web console to confirm functionality.

6. Reapply Licenses

• If necessary, reapply the proper license to the system.

If the steps above don't work:

1. Using the command prompt, navigate to the SolarWinds installation path and run the migration.exe /expireall command. 
2. Activate the licenses again.