Java Processes fail to start | The driver could not establish a secure connection to SQL Server...
search cancel

Java Processes fail to start | The driver could not establish a secure connection to SQL Server...

book

Article ID: 242092

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

Java Automation Engine Processes (JCP, JWP, REST) fail to start. The database in use is Microsoft SQL.

The following error is present in the log files:

20221011/084118.059 - 1      U00003590 UCUDB - DB error: '08S01', '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". ClientConnectionId:d31c2349-49aa-42d5-b867-2774c6812cbe', '0', 'com.microsoft.sqlserver.jdbc.SQLServerException'
20221011/084118.074 - 1      U00032031 Error when connecting to Database
20221011/084118.309 - 40     U00045025 OSGI ['com.automic.indexsearch']: 'FrameworkEvent ERROR'
20221011/084118.309 - 40               Unhandled Exception in thread Framework Event Dispatcher: Equinox Container: 8e9120f0-5d56-4cae-9bb2-90e1496fbe77
20221011/084118.309 - 40     U00045014 Exception 'java.lang.IllegalStateException: "The service has been unregistered"' at 'org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getReferenceImpl():285'.
20221011/084118.309 - 40     U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.
20221011/084118.309 - 40     U00003450 The TRACE file was opened with the switches '0000000000000000'.

Environment

Release : 21.X

Component : AUTOMATION ENGINE

Database: Microsoft SQL

Cause

This is caused by the JDBC driver and MS SQL requiring TLS/SSL to communicate and a trusted connection must be made.  This was not needed with previous versions of the JDBC driver and MSSQL

Resolution

The error is coming from a driver, not Automic, the resolution can be found below:

Edit the JDBC connection string so it has the following at the end of the string.

encrypt=true;trustServerCertificate=true

Example:

sqlDriverConnect=jdbc:sqlserver://localhost:1433;databaseName=Automic;integratedSecurity=false;user=Automic;password=???;encrypt=true;trustServerCertificate=true

If this error still occurs after updating the string, please reach out to a DBA to see what else might be needed.