ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 224586

calendar_today

Updated On:

Products

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

Issue/Introduction

We are trying to setup SQL monitoring for a server running in Azure. DB 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 connection test.
 
 
The probe is started, and this issue only happens for a specific server, as other SQL servers can be tested. 
 
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 

Cause

- TLS was not set to 'Enabled' for the connection.

Environment

Release : 20.3

Component : UIM - SQLSERVER (any version) 

- TLS 1.2 support for sqlserver is supported as of v5.30 or higher.

Resolution

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

In the probe connection detail, enable the use TLS checkbox and try again. 

sqlserver IM Configuration (broadcom.com)

 

Attachments