sqlserver connection test fails with "Probe has to be started for connection test"
search cancel

sqlserver connection test fails with "Probe has to be started for connection test"


Article ID: 224586


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


  • We are trying to setup SQL monitoring for a server running in Azure.
  • Database ports are opened and it is able to connect to the DB using SQL Client.
  • Also telnet is successful.
However, we are getting 'Probe has to be started for connection test' error during the sqlserver probe connection test.
Actually the probe is started, and this issue only happens for a specific server, as other SQL servers' connection tests are successful.
In the probe logs we see:
sqlserver: (NimCryptographerCfgKeyReadEncryptedValue) failed to decrypt value. RC=3
sqlserver: Profile: test connection profile/test connection checkpoint/Connect - COM Error: Code=0x80004005 Source=Microsoft OLE DB Provider for ODBC Drivers Description=[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error 


  • Release: 20.3
  • Component: UIM - SQLSERVER (any version) 
  • sqlserver probe - TLS 1.2 support for sqlserver is supported as of v5.30 or higher.


  • In this case, TLS was not set to 'Enabled' for the connection.
  • In other cases where this error occurs, its normally due to user access/permissions


Most likely, the server hosting the SQL Server that is contacted requires TLS 1.2 for the connection. 

In the probe connection details, Edit Connection, select the 'TLS Enabled' checkbox and try again. 

sqlserver IM Configuration (broadcom.com)


Additional Information

For Microsoft (MS) SQL Server authentication, please check if the user has been granted the correct permissions and also the dbo role.

Please refer to:

SQL Server Monitoring Release Notes

'Access Prerequisities'