VAIM 12.9 installation cannot authenticate to remote SQL Server running on Windows 2016 Server
search cancel

VAIM 12.9 installation cannot authenticate to remote SQL Server running on Windows 2016 Server

book

Article ID: 133500

calendar_today

Updated On:

Products

CA Virtual Assurance for IM

Issue/Introduction

  • I am unable to install VAIM 12.9, since the installation cannot authenticate to remote SQL Server running on Windows 2016 Server:

  • You can test the connection from the VAIM Server to the remote SQL DB using the OSQL command which is packaged as part of SQL Client Tools (which is a required pre-requisite).  You will not be able to authenticate within the VAIM installer unless one of the below commands completes successfully (depending on the authentication type configured within SQL Server)

Windows authentication:

osql -S <SQL-SERVERNAME>\<INSTANCE>,1433 -E -Q "SELECT * FROM sysdatabases”

sa:

osql -S <SQL-SERVERNAME>\<INSTANCE>,1433 -U <user-name> -P <password> -Q "SELECT * FROM sysdatabases"













Environment

VAIM 12.9

SQL Server running on Windows 2016 Server

Cause

  • By default TLS 1.0 is disabled for Schannel connections on Windows 2016 Server.
  • The VAIM installer is trying to connect to SQL Server using TLS 1.0 and this setting is not user configurable.


Resolution

  1. Enable TLS 1.0 for both Client and Server on the Remote SQL Server:
  • To enable the TLS 1.0 protocol, create an Enabled entry in  both the Client and Server subkeys. 
  • These entries do not exist in the registry by default. 
  • After you have created the each entry change the DWORD value to 1.


HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS1.0\Client



HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\ TLS1.0\Server


2. Reboot Server to make the changes.


Additional Information

Transport Layer Security (TLS) registry settings

https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings

Attachments