microsoft ole db provider for sql server working on local machine but not on the server

Question

User-1966075301 posted

We have an application which uses microsoft ole db provider for sql server  to read data from sql server. 

After our DBA team disabled TLS 1.0 and TLS 1.1 

Application on the server stopped working and when I tried connecting to database using Microsoft ole db provider for sql server  I received below error 

[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

But when I am able to connect to the same database and same driver without any issues from my local machine. 

I am not sure why the same connection works on one machine but not on another, any inputs are appreciated

Answer 1

User690216013 posted

https://blog.catchpoint.com/2017/05/12/dissecting-tls-using-wireshark/

Learn how to analyze TLS handshakes using a tool like Wireshark, and then you can easily find out what's wrong on certain machines.

Answer 2

User1065476709 posted

Hi gnaniwars1,

[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

The first step towards resolving the SSL Security error, is to make sure that the version of the target SQL Server instance you want to connect to, is supported by the driver.

For example, Microsoft OLE DB Driver 18.1 for SQL Server supports connecting to SQL Server 2012 or later.

For older versions of SQL Server, you will need to find an earlier version of Microsoft OLE DB Provider for SQL Server as well.

You can find the latest version of the OLE DB driver here.

Best regards,

Sam

Answer 3

User-1966075301 posted

Hi Sam,

Thank you for your inputs.

i have installed the latest drivers present and connecting to sql server 2019 database.

I have installed same drivers present on my machine and installed them on the server and I am unable to determine why it works on machine but not on the server.

Thanks

Gyan

Answer 4

User-1966075301 posted

Thanks for your inputs, I will check with my admin if they are any tools present.

Answer 5

User1065476709 posted

Hi gnaniwars1,

Thanks for your inputs, I will check with my admin if they are any tools present.

You can refer to lextm's suggestion to use Wireshark to dissect TLS.

Best regards,

Sam