# Unable to connect with database connection in Ignition after upgrade 8.1.26 to 8.143 **URL:** \ **Category:** Ignition\ **Tags:** database\ **Created:** [April 27, 2025, 3:59pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613 "2025-04-27T15:59:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![MuraliKrishnan\_Palan](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@MuraliKrishnan\_Palan](https://forum.inductiveautomation.com/u/MuraliKrishnan_Palan)\ **Post date:** [April 27, 2025, 3:59pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/1 "2025-04-27T15:59:26Z")
![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/3/1332afbeac4d04ec87e362b653476ee636c2f12f.jpeg) Getting the below error in Database connection in Ignition after upgrade 8.1.26 to 8.143 java.sql.SQLException: 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)".) at org.apache.commons.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:656) at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:534) at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:734) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.getConnectionInternal(DatasourceImpl.java:300) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.runTest(DatasourceImpl.java:253) at com.inductiveautomation.ignition.gateway.datasource.DatasourceManagerImpl$FaultedDatasourceRetryer.lambda$newRetryRunnable$0(DatasourceManagerImpl.java:1097) at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:593) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: 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)". at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1058) at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841) at org.apache.commons.dbcp2.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:52) at org.apache.commons.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:357) at org.apache.commons.dbcp2.BasicDataSource.validateConnectionFactory(BasicDataSource.java:103) at org.apache.commons.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:652) ... 12 more Caused by: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at java.base/sun.security.ssl.HandshakeContext.(Unknown Source) at java.base/sun.security.ssl.ClientHandshakeContext.(Unknown Source) at java.base/sun.security.ssl.TransportContext.kickstart(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379) ... 20 more 8.1.43 (b2024082010) Azul Systems, Inc. 17.0.11 ---
**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:** [April 27, 2025, 4:09pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/2 "2025-04-27T16:09:48Z")
> [@MuraliKrishnan\_Palan](#): > > javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) This usually means you're connecting to a very old version of SQL Server that doesn't support TLS 1.2 or later... I think this KB article covers it, but if not you can find other posts on the forum about it as well: [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) ---
**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:** [April 27, 2025, 4:21pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/3 "2025-04-27T16:21:46Z")
Please see [Wiki - how to post code on this forum](https://forum.inductiveautomation.com/t/wiki-how-to-post-code-on-this-forum/77831) (and error logs). When you format it as code the forum automatically limits the number of lines displayed (and adds a scrollbar) so that the post doesn't become ridiculously long. You can edit your post to fix it. Thanks. ---
**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:** [April 27, 2025, 4:26pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/4 "2025-04-27T16:26:20Z")
If you've got an ancient version of SQLServer then try the approach listed starting at this post: [SQL Express 2005 database connection ideas? - #15 by JordanCClark](https://forum.inductiveautomation.com/t/sql-express-2005-database-connection-ideas/78728/15) and read down to the end. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [April 27, 2025, 9:51pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/5 "2025-04-27T21:51:26Z")
Or maybe time to upgrade sql server 🙂 ---
**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:** [April 27, 2025, 10:26pm UTC](https://forum.inductiveautomation.com/t/unable-to-connect-with-database-connection-in-ignition-after-upgrade-8-1-26-to-8-143/105613/6 "2025-04-27T22:26:58Z")
In my case it was on a validated medical device manufacturing machine. Revalidation would have been a major pain. Oooh - it was running on XP too!