# SQL Server Connection Error **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 26, 2025, 5:28am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-error/104213 "2025-03-26T05:28:16Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![davidy](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@davidy](https://forum.inductiveautomation.com/u/davidy)\ **Post date:** [March 26, 2025, 5:28am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-error/104213/1 "2025-03-26T05:28:16Z")
I am trying to get a new Ignition 8.1.47 on Ubuntu to connect to MS SQL Server (Tried 2022 and 2019). The error I get is: > Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)".) I have updated the JDBC drivers to the latest 12.10. I have added trustServerCertificate=true;encrypt=true as extra connection properties. I have tried adding: wrapper.java.additional.11=-Djdk.tls.client.protocols=TLSv1.2 in ignition.conf I tried pointing it to SQL Server 2012 currently being used by an Ignition 7.9 project. The error message has not changed in any configuration. Is there anything else I can try? Or a known configuration of Ignition/JDBC/MS SQL Server that works? ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [March 26, 2025, 8:27am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-error/104213/2 "2025-03-26T08:27:07Z")
See if [What permissions/role needed for ignition to insert data to MSSQL table? - #4 by Transistor](https://forum.inductiveautomation.com/t/what-permissions-role-needed-for-ignition-to-insert-data-to-mssql-table/73760/4) helps. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [March 26, 2025, 10:49am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-error/104213/3 "2025-03-26T10:49:37Z")
> [@Connection to MSSQL(2014) lost when updated to 8.1 (from 7.9)](https://forum.inductiveautomation.com/t/connection-to-mssql-2014-lost-when-updated-to-8-1-from-7-9/57332/4): > > This thread (and its linked threads) should cover your SQL Server problem: [SQL Server Connection Faulted](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393) Basically, your old version of SQL Server does not support TLS 1.2, and by default newer Java versions have deprecated and do not support TLS 1.0 or 1.1. So you either need to upgrade SQL Server or hack up your Java install to enable the insecure protocols. User sources are managed in the gateway. All I know is you have a user source trying to a connect to an AD server at hostname “scada-dc… also [https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue](https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue) edit: oops, only saw MSSQL 2012, this shouldn't be relevant with the newer versions... ---
**Author:** ![Lynn\_Martineau](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@Lynn\_Martineau](https://forum.inductiveautomation.com/u/Lynn_Martineau)\ **Post date:** [March 26, 2025, 8:52pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-error/104213/4 "2025-03-26T20:52:32Z")
Check the Database Drivers page on the gateway. Whenever I've seen > [@davidy](#): > > Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)".) there was an error indicating the SQL Server driver on your Ignition server needs to be updated. Click the Edit button next to the driver that has an error and update the .JAR file from there.