Tools

Online license activation fails when using the desktop License Manager

This article addresses an issue with license activation for products using the desktop License Manager application. The online license activation fails with the "Your license activation failed" error.

First published date

9/12/2022 5:58 PM

Last published date

3/10/2025 6:22 PM

Overview

When activating a valid license online, it fails with the following error message on DMRC:

ERROR 

Your license activation failed

The license you provided cannot be activated.

The underlying connection was closed: An unexpected error occurred on a send.

The request was aborted. Could not create SSL/TSL secure channel

     

    image.png


    SolarWinds License Manager also reports an error status:

    ERROR

    The synchronization is complete. Results are on the Synchronize Licenses dialog.


    License_Manager_Error.png

    This applies to the following products:

    • Dameware
    • Engineer's Toolset Desktop
    • Network Topology Mapper
    • Patch Manager
    • ipMonitor
    • Database Mapper
    • Task Factory
    • Orion platform products 2016.1 or older

    This does not apply to Serv-U.

     

    Product section

    Dameware Remote Support & Mini Remote Control

    Cause

    An update patch was applied to the license server that caused a mismatch of the security protocol in use by the client server and the license server.

    Resolution

    Solution 1: Install the latest version of the SolarWinds License Manager version 6.x.x.

    Or

    Solution 2: Manually do the procedure below to enable SchUseStrongCrypto and SystemDefaultTlsVersions for .NET in the Windows Registry.

    Warning:

    SolarWinds strongly recommends that you back up your registry before editing it. Only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to  reinstall your OS to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

     

    1. Open Registry Editor.

    2. Create or update the four registry settings below:

      1. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001

      2. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001

      3. [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions" = dword:00000001
        "SchUseStrongCrypto" = dword:00000001

      4. [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions" = dword:00000001
        "SchUseStrongCrypto" = dword:00000001

    3. Restart the computer.

    Note:

     The SchUseStrongCrypto setting allows .NET to use TLS 1.1 and TLS 1.2. The SystemDefaultTlsVersions setting allows .NET to use the OS configuration.

     

    If the registry process does not fix the issue, please contact SolarWinds Support for assistance.