You could add 'encrypt=false' to the connection Options dialog which has the same effect but is neater, or construct a full JDBC string and use a Generic Database connection instead. ClientConnectionId:8563cdf7-79c9-4979-891a-07ee415b1ffeThe problem is related to a breaking change introduced with version 10.2: Error: PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested target. The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.

Subject: Problems upgrading MSSQL's JDBC to 11.2 and how to set properly encrypt=false in the JDBC URL hacky and the JNDI approach will require a lot of work in order to migrate all the connections. JNDI_JDBC_TEST/url=jdbc:sqlserver://SERVER:1443 databaseName=DATABASE integratedSecurity=false encrypt=false īoth options work OK but the hacky one is just. But it is a cowboy job :PĪnother option is to use JNDI connections. This hack will create a proper JDBC URL connection:Īnd therefore the connection will succeed. Well there is a hack, by adding encrypt=false to the database name. The problem is related to a breaking change introduced with version 10.2:īREAKING CHANGE TLS encryption is enabled by default.įrom Pentaho GUI is not not possible to disable the TLS encryption. I am upgrading MSSQL's JDBC to the latest version (currently 11.2) but after copying the file into the lib folder I am getting the following error:

Microsoft sql server jdbc driver 3.0