topic Re: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connect in Data Engineering

com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.

Kazer — Mon, 30 Jan 2023 09:47:33 GMT

Hi. I am trying to read from our Microsoft SQL Server from Azure Databricks via spark.read.jdbc() as described here: Query databases using JDBC - Azure Databricks | Microsoft Learn. The SQL Server is on an Azure VM in a virtual network peered with the virtual network of the azure databricks workspace.

The reading/writing used to work without problems. Last week, I started to get the error message when manually triggering the function in a notebook:

com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target".

The weird thing is: In my automated databricks workflow I also use read/write operations. The first read and write operation work as usual, but the second read operation is stuck without throwing an error. If I don't manually cancel the run, the function will just be stuck for hours.

Would be glad if sombody could give me a hint at what the problem could be?

Re: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.

Kazer — Wed, 01 Feb 2023 07:43:31 GMT

Solved. The problem was that some of the tables I tried to access were blocked by a transaction in a stuck stored procedure. So this was an SQL Server side problem specific for the tables I tried to access and had nothing to do with Azure/Databricks.

Re: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connect

databricks26 — Tue, 02 Jan 2024 16:53:22 GMT

Hi @Kazer ,
Even if I use a new table name, I get the same error. Do you have any suggestions?

Thanks,