Troubleshooting
Problem
So while trying to test the connection for adding a data source, adding the JDBC trace in the custom url causes the test connection to fail.
If you remove the JDBC trace from the customer url the test connection works.
If you remove the JDBC trace from the customer url the test connection works.
Cause
The use of the custom url forces the connection to use TLS 1.3 which is unsupported by MS SQL.
Diagnosing The Problem
Collect a tcpdump, you should see that the handshake is failing, from the database server.
Resolving The Problem
In order to force the connection to use a supported TLS method that is supported by MS SQL.
Simply add the below parameter to the custom url:
CryptoProtocolVersion=TLSv1.2
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z0000000CeYAAU","label":"DATA SOURCES"}],"ARM Case Number":"TS019509286","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0.0;12.1.0"}]
Was this topic helpful?
Document Information
Modified date:
15 July 2025
UID
ibm17239756