Network Management

Access Issue: SolarWinds Platform Web Console Fails Due to Invalid sslProtocolType Enumeration in Licensing Service

SolarWinds services do not connect to the Licensing FeatureProviderService. They encounter an error due to an invalid SslProtocolType enumeration value. This happens because the .NET TLS configuration is not as expected. Turn on strong cryptography for the .NET Framework.

First published date

1/31/2026 12:20 AM

Last published date

1/31/2026 12:20 AM

Overview

When the SolarWinds Platform tries to make a secure Net.TCP connection to the licensing service on port 17777, it hits a snag during the SSL/TLS negotiation. This connection failure stops licensing validation. It might also affect how SolarWinds Platform modules start up or work.

This error is often seen after tightening TLS settings, after Windows updates, or after security policies change. These changes might disable older SSL/TLS protocols.

Product section

Network Performance Monitor

Cause

This problem happens because the .NET Framework isn't configured to use the system's default TLS versions or strong cryptography. Because of this, SolarWinds tries to use an SSL/TLS protocol that's either not supported or has been disabled. This leads to the following error message:

System.ArgumentException: The specified value is not valid in the 'SslProtocolType' enumeration.

Most of the time, this is because:
* TLS 1.0 or 1.1 has been disabled at the operating system level.
* The .NET Framework isn't set up to automatically use TLS 1.2.
* There are missing or incorrect registry settings for strong cryptography.

Resolution

Resolution:
1. Enable strong cryptography for the .NET Framework. To do this, update a specific registry key.
2. Change the value from 0 to 1. This is a DWORD value.

The registry paths are:
HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319

The registry values are:
SchUseStrongCrypto
SystemDefaultTlsVersions

3. Restart the SolarWinds services or reboot the server.

Note: This configuration forces .NET to use secure, system-default TLS versions (such as TLS 1.2), allowing the licensing service connection to succeed.

Additional Notes
- This fix is especially relevant in environments where TLS hardening or security baselines have been applied.
- Ensure TLS 1.2 is enabled at the OS level. See Enable TLS in Orion Platform products.