You can translate the question and the replies:

SSL error in SQL server

Hi Team, Denodo 6.0 Database Adapter : MS SQL server 2012 (MS Driver) Driver Class Path : sqljdbc4.jar Driver Class : com.microsoft.sqlserver.jdbc.SQLServerDriver Error: Unable to establish connection: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did not return a response. The connection has been closed. ClientConnectionId:23c40430-e7ac-4271-8415-7afe874cd6ad". Please suggest. Thanks.
SSL
user
25-11-2019 04:35:23 -0500

13 Answers

Hi, From your driver classpath I can see that you are using a fairly old version of the MS Driver. I am unable to reproduce this issue as version 4.0 is no longer supported by MS SQL Server. What I would do is first update the driver to the latest version and see if this solves the issue. I would take a look at this Microsoft article that explains more about this issue: [Intermittent JDBC Connectivity issue](https://blogs.msdn.microsoft.com/dataaccesstechnologies/2016/11/30/intermittent-jdbc-connectivity-issue-the-driver-could-not-establish-a-secure-connection-to-sql-server-by-using-secure-sockets-layer-ssl-encryption-error-sql-server-returned-an-incomplete-respons/) Hope this helps!
Denodo Team
25-11-2019 19:03:11 -0500
Hi Team, Please confirm if I can do this: Denodo 6.0 jre folder : current jvm is 1.7 update it to jvm 1.8 ? By copying jvm 1.8 folder, named as jre. (replacing jvm 1.7 with jvm 1.8) Thanks.
user
27-11-2019 03:44:14 -0500
Please suggest.
user
29-11-2019 01:26:21 -0500
Hi Team, Please confirm if I can do this: Denodo 6.0 jre folder : current jvm is 1.7 update it to jvm 1.8 ? By copying jvm 1.8 folder, named as jre. (replacing jvm 1.7 with jvm 1.8) Thanks.
user
02-12-2019 01:18:39 -0500
Please suggest.
user
03-12-2019 22:12:38 -0500
Awaiting response: Hi Team, Please confirm if I can do this: Denodo 6.0 jre folder : current is 1.7 update it to 1.8 ? By copying 1.8 folder, named as jre. (replacing 1.7 with 1.8) Thanks.
user
05-12-2019 03:50:21 -0500
please update.
user
12-12-2019 00:35:20 -0500
Hi, I personally wouldn’t take that approach as it can lead to unexpected errors. What I would do to use a custom JRE is to change it from the Control Center. Under the Configure tab I would edit the Java Virtual Machine and add a new one. I would read the documentation on [Denodo Platform Configuration](https://community.denodo.com/docs/html/browse/7.0/platform/installation/denodo_platform_control_center/virtual_machine_and_web_container_configuration/virtual_machine_and_web_container_configuration) to learn more about this. Hope this helps!
Denodo Team
18-12-2019 11:18:27 -0500
Thanks Team, I will use custom JVM from control center. However, can you tell me if any of the configuration properties file has details for JVM. Thanks.
user
24-12-2019 05:27:20 -0500
Hi Team, I updated JVM options to use jre1.8. But we have the problem as: the sqljdbc drivers version 4,6 and 7 are not able to conenct to few data base tables (sql server). But the "jtds" driver has no such problem. Adapter : MS SQL Server 2012 (JTDS) denodo-jtds-1.2.1 net.sourceforge.jtds.jdbc.Driver Adapter : MS SQL Server 2012 (MS Driver) sqljdbc4.jar or mssql-jdbc-6.4.0.jre8.jar com.microsoft.sqlserver.jdbc.SQLServerDriver error for sqljdbc: unable to find columns,unable to connect to database. as we have only to use sqljdbc jar, how to procced here. Note: the user has all access. Thanks.
user
27-12-2019 02:41:04 -0500
please update.
user
30-12-2019 03:29:04 -0500
please update for : 27 Dec 2019 13:11
user
31-12-2019 06:50:24 -0500
Hi, First of all I would be careful using the sqljdbc4 connector as [Microsoft does not support (4.1 and down) officially for Java 8](https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-ver15). Regarding the mssql-jdbc-6.4.0 connector I have not had any problem using it with a custom JVM on Java 8. I would take a look at the [Diagnosing problems with the JDBC driver](https://docs.microsoft.com/en-us/sql/connect/jdbc/diagnosing-problems-with-the-jdbc-driver?view=sql-server-ver15) page on the Microsoft Documentation to further trace this issue. Another path I would follow is to try connecting using the exact same driver through a different client and see if I get any issue. This should help me know if the problem is the driver or Denodo. Hope this helps!
Denodo Team
07-01-2020 13:42:13 -0500
You must sign in to add an answer. If you do not have an account, you can register here