SSL Security error using OLEDB Connection
Friday, January 26, 2018
This error may be caused by the Transport Layer Security (TLS) version 1.2 being the only enabled version on the SmartConnect Server. TLS 1.2 support for Microsoft SQL Server
If you are using TLS 1.2 on your server that runs SmartConnect with TLS 1.0 and 1.1 turned off, the OLEDB Connection Data Source will no longer work.
You will receive the error “[DBNETLIB][ConnectionOpen (SecDoClientHandshake()).]SSL Security Error.”
In SmartConnect, this means that any existing maps with an OLEDB Connection setup as the Source will not work once TLS 1.0 and 1.1 are turned off. You will also no longer be able to setup new maps using the OLEDB Connection either.
There are a couple of options if you using the OLEDB Connection with only TLS 1.2 enabled.
1. You can switch to using an ODBC connection for your source instead when selecting from your Data Source Drop down.
2. You can enable TLS 1.0 and 1.1 on the SmartConnect Server.
It appears that the OLE DB provider may not be upgraded to support TLS 1.2 in the future, so it would be good practice to upgrade any existing maps to ODBC as that will continue to be upgraded with TLS.
If you are using TLS 1.2 on your server that runs SmartConnect with TLS 1.0 and 1.1 turned off, the OLEDB Connection Data Source will no longer work.
You will receive the error “[DBNETLIB][ConnectionOpen (SecDoClientHandshake()).]SSL Security Error.”
In SmartConnect, this means that any existing maps with an OLEDB Connection setup as the Source will not work once TLS 1.0 and 1.1 are turned off. You will also no longer be able to setup new maps using the OLEDB Connection either.
There are a couple of options if you using the OLEDB Connection with only TLS 1.2 enabled.
1. You can switch to using an ODBC connection for your source instead when selecting from your Data Source Drop down.
2. You can enable TLS 1.0 and 1.1 on the SmartConnect Server.
It appears that the OLE DB provider may not be upgraded to support TLS 1.2 in the future, so it would be good practice to upgrade any existing maps to ODBC as that will continue to be upgraded with TLS.
