Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion Platform encounters issues after disabling TLS 1.0 and TLS 1.1

Orion Platform encounters issues after disabling TLS 1.0 and TLS 1.1

Created by Alexandra.Nerpasova, last modified by Jie Y Lee on Oct 02, 2018

Views: 1,430 Votes: 1 Revisions: 9

Updated July 18, 2018


When you disable TLS 1.0 and TLS 1.1 on systems running Orion Platform 2017.3 and below and leave only the TLS 1.2 cipher, applications in Orion stop working properly.


  • Orion Platform 2017.3


Starting in Orion Platform 2018.2, TLS 1.2-only connections are supported for organizations that require that type of delivery for security and compliance reasons. See TLS compatibility with Orion Platform products.


This is a known issue caused by disabling TLS 1.0 and TLS 1.1. It has been fixed in version 2018.2 of the Orion Platform. If you are using an earlier version of the Orion Platform, use the workaround described below.


  1. Go to the page (© Microsoft 2017, available at, obtained on December 14, 2017.)
  2. Download and install updates that are targeted to your specific SQL Server version running in your environment. For example:
    • SQL Server 2008 R2 SP3 10.50.6542.0 SQL Server 2008 R2 SP3 TLS 1.2 Update
    • Hotfix rollup 3099842 for the .NET Framework 4.5.2, 4.5.1, and 4.5 on Windows 8.1 and Windows Server 2012 R2
  3. Update the SQL native client on the primary Orion Server, any Additional Polling Engines, Additional Web Servers, and HA backups.
    1. See SQL Server Native Client (for SQL Server 2008 R2) - SQL Server Native Client (x86 and x64) (© Microsoft 2017, available at, obtained on December 14, 2017.) in the second table on the Microsoft web page.
    2. Download and install the native client update.

      The native client update is a part of the SQL Server 2008 R2 SP3 TLS 1.2 Update package so it is not required to install it when the SQL Server is on the same machine as the Orion Platform. For example, typical evaluation configurations.

  4. Open the SWNetPerfMon.DB file in Notepad.exe on every Orion Server. The default location is C:\Program Files (x86)\SolarWinds\Orion.
  5. At the top of the file, change the string ConnectionString=provider=SQLOLEDB.1 to ConnectionString=provider=SQLNCLI10
  6. Reboot the machine.

    Be sure to repeat the same steps for every Orion server in your environment. For example, Additional Polling Engine, Additional Web Server, HA Backups.

  7. When the process is complete, the Orion Platform should function properly with TLS 1.0 and TLS 1.1 disabled.

Suggested Tags:  


A reason for rework or Feedback from Technical Content Review:



Last modified