Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Desktop tools like Trap Viewer, Syslog Viewer, Account Limitation Builder do not work if TLS 1.0 is disabled

Desktop tools like Trap Viewer, Syslog Viewer, Account Limitation Builder do not work if TLS 1.0 is disabled

Updated September 5, 2017


When you open Orion desktop tools like Trap Viewer, Syslog Viewer, Report Writer, Account Limitation Builder, an SQL connection error like the following is displayed.




Products running on SolarWinds Orion Platform version 2016.2 and later, such as:

  • NPM 12.0.1 and later
  • SAM 6.3 and later


The TLS 1.0 protocol is disabled on the SQL Server, Orion server, or both. TLS 1.0 must be enabled on the SQL Server machine and Orion server to use SolarWinds Orion desktop tools by default.


View TLS compatibility with Orion Core Products to verify if your SolarWinds Orion products work with TLS 1.0 disabled.

Solution 1: Enable the TLS 1.0 protocol on your SQL server and all SolarWinds Orion servers

SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should 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 operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

  1. Log in to the computer as an administrator.
  2. Back up your registry. 
  3. Open the registry editor.
  4. Find or create the following keys:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server
  5. Within each key find or create the following REG_DWORD values:
    • DisabledByDefault, set value to 0 decimal
    • Enabled, set value to 1 decimal
  6. Reboot the computer.
  7. Apply this change to all servers in your SolarWinds environment where TLS 1.0 disabled.

TLS 1.0 is now enabled.

Solution 2: Install the latest Microsoft updates for SQL Server and  SQL Native Client and make configuration changes

Microsoft released updates that enable TLS 1.2 support for SQL Server products. You should install those updates on you SQL Server before attempting following steps.


  1. Install KB3135244 on your SQL Server.
  2. Log in to the computer hosting the Orion sever as an administrator.
  3. Download and install Microsoft® SQL Server® 2012 Native ClientQFE.
  4. Download and install ADO.NET. This is the SqlClient update mentioned in KB3135244 that applies to your installed versions of Windows and .NET.
  5. Open the Orion Service Manager and stop all services.
  6. In the Orion program folder (located by default in C:\Program Files (x86)\SolarWinds\Orion), create a backup of SWNetPerfMon.DB.
  7. Open file in Notepad.
  8. In the beginning of the file, find string that starts with "ConnectionString=provider=SQLOLEDB.1;".
  9. Replace "SQLOLEDB.1" with "SQLNCLI11".
  10. Start all Orion services.

The SolarWinds Orion desktop tools work as expected.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified