Litespeed cannot connect to SQL Server when encryption is enforced and TLS 1.0 is disabled.
After disabling TLS 1.0 and using TLS 1.2, Litespeed fails to backup saying it can't log in.
Also the error below appears when trying to configure the instance engine:
'XXXX\DATAVAULT: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.'
You may also see this error when trying to backup:
'Msg 62300, Sev 16, State 1: Backup of database "DB_NAME" failed. Database [DB_NAME] not found [SQLSTATE 42000]'
SOLUTION 1:
You must configure, via the litespeedsettings.ini file (Usually in C:\Documents and Settings\All Users\Application Data\Dell\LiteSpeed\SQL Server), the use of a different provider for TLS1.2 as the default provider does not work with that protocol.
When TLS 1.0 is disabled, to workaround the issue, please add the update below to your Litespeedsettings.ini file and try the test again.
[general]
Provider=provider used
[instance name]
Provider=Provider used
***Please note that only one [instance name] section should be present in the Litespeedsettings.ini file. If there is an existing [instance name] in the .ini file, please add the provider line underneath that section.***
EXAMPLE 1:
[general]
Provider=SQLNCLI10
[myServerName]
Provider=SQLNCLI10
EXAMPLE 2:
[general]
Provider=SQLNCLI11
[myServerName]
Provider=SQLNCLI11
EXAMPLE 3:
[general]
Provider=SQLNCLI11.1
[myServerName]
Provider=SQLNCLI11.1
Normally the [instance name] is not needed, but it's included here to assist troubleshooting.
If you do not know what provider is used, you can create a “test.udl” file.
To do this, connect to the server using that “test.udl” file. If the test works, open the test.udl file in notepad and make a note of the provider seen.
Alternatively, you may run the following command against the instance:
********************************
EXEC sp_MSset_oledb_prop
********************************
EXAMPLE:
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=LiteSpeedLocal;Data Source=ALVCLBW13\CSRWORK
(sqloledb.1 is the default. You may see sqloledb10 or sqloldbd11 which translates into SQLNCLl10 or SQLNCLl11 for the Litespeedsettings.ini file)
For more information on creating a .UDL file, please check the following Microsoft article here
SOLUTION 2:
Do not enable TLS 1.2 and continue with TLS 1.0 enables.
STATUS
Issue fixed in version 8.6.1. The latest version of LiteSpeed on SQL Server can be downloaded here
