sqlserver probe connection test and timeout error - log shows Invalid connection string attribute
search cancel

sqlserver probe connection test and timeout error - log shows Invalid connection string attribute


Article ID: 258559


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


I have tried deploying the sqlserver probe on one of the robots while I tried to test it, but it is showing Connection test failed and timeout error.

sqlserver log showed:

sqlserver: Profile: test connection profile/test connection checkpoint/Connect - COM Error: Code=0x80040e4d Source=Microsoft SQL Server Native Client 11.0 Description=Invalid connection string attribute

sqlserver: Connection test to <example.net> failed


  • Release: 20.3
  • sqlserver probe v5.60


For connecting sqlserver to a DB server,

TLS 1.1 is NOT supported.

TLS 1.2 IS supported as of sqlserver probe v5.30 or higher.

"Added support for TLS 1.2. The probe requires the SQL Server Native Client 11.0 driver or ADO.net 4.6 framework. For more information on how to enable TLS 1.2 support and the compatible client and server versions, see:

The following Microsoft SQL Server versions are supported:

  • 2012
  • 2014
  • 2016
  • 2017

Support for TLS v1.2 (Microsoft SQL Server)


If TLS 1.2 is enabled on the Database Server, sqlserver should be able to connect if TLS 1.2 is enabled in the sqlserver probe.


So in other words, the bottom line for connecting to a DB server using sqlserver probe is this:

If TLS of some version/unsupported version is enabled other than TLS 1.2, you have to disable TLS 1.0 and TLS 1.1 and only have TLS 1.2 enabled on the DB server.