Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
JDBC connection failed after upgrade stating "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • JDBC connection failed after upgrade stating "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption"
KB0821344

JDBC connection failed after upgrade stating "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption"


16321 Views Last updated : Mar 21, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

After upgrading the Instance and MID Server, loading records from the JDBC Datasource failed with the below error:

MID Server reported error: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: 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:"

There also instances where running SQL 2005 or earlier can run into the following error as these versions of SQL only support TLS version 1.0:

MID Server reported error: SQLState: null
java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:

Cause

1. Find out the Java version used by the MID Server.

  • To check the version, Run this in MID Server > Scripts - Background by selecting the appropriate MID Server from the dropdown
    ms.log(Packages.java.lang.System.getProperties());
  • You can find the "java.version=" in the results.

2. Find out the SQL Server version of the target where the JDBC Datasource queries.

 

Java version 1.8+ uses TLS 1.2 by default

TLS 1.2 is only supported starting from SQL 2008 and higher versions, which can cause the SSL exception.

Reference - https://support.microsoft.com/en-in/help/3135244/tls-1-2-support-for-microsoft-sql-server

Resolution

Please ask the SQL administrators to set up a new view, instance, or node on a separate server running version 2008 or higher to ensure compatibility with the required TLS version.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.