# After upgrading from 8.1.13 to 8.1.32 I have a one DB is down between tens of DBs **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [October 3, 2023, 4:39pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988 "2023-10-03T16:39:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![samer\_samy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/samer_samy/32/52910_2.png) [@samer\_samy](https://forum.inductiveautomation.com/u/samer_samy)\ **Post date:** [October 3, 2023, 4:39pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/1 "2023-10-03T16:39:42Z")
Dears, I can log to a database directly from mssql and i defined this DB in ignition before and it was valid , but now after upgrading from 8.1.13 to 8.1.32 i find this DB failed to connect from ignition gateway although this DB is healthy . ---
**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:** [October 3, 2023, 4:40pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/2 "2023-10-03T16:40:19Z")
What's the error message? ---
**Author:** ![samer\_samy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/samer_samy/32/52910_2.png) [@samer\_samy](https://forum.inductiveautomation.com/u/samer_samy)\ **Post date:** [October 3, 2023, 4:53pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/3 "2023-10-03T16:53:05Z")
```auto 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: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:bad00221-c19c-47c3-a71b-62eede591102) 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:1096) at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:587) 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: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:bad00221-c19c-47c3-a71b-62eede591102 at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2887) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1881) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2452) at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2103) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1950) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1162) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:735) 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: The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12] at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source) at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.ServerHello$ServerHelloConsumer.onServerHello(Unknown Source) at java.base/sun.security.ssl.ServerHello$ServerHelloConsumer.consume(Unknown Source) at java.base/sun.security.ssl.SSLHandshake.consume(Unknown Source) at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source) at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(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:1799) ... 21 more 8.1.32 (b2023091211) Azul Systems, Inc. 11.0.18 ``` ---
**Author:** ![samer\_samy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/samer_samy/32/52910_2.png) [@samer\_samy](https://forum.inductiveautomation.com/u/samer_samy)\ **Post date:** [October 3, 2023, 4:53pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/4 "2023-10-03T16:53:34Z")
Support solved it ```auto Starting with Java 11.0.11, TLS v1.0 and TLS v1.1 protocols are disabled by default. You will need to either enable TLS1.2 on the SQL Server or re-enable TLS1.0 and TLS1.1 on the Ignition Gateway. The suggested method is to enable TLS1.2 on the SQL Server since it's more secure. The process to do this can be found from Microsoft, and is based on the version of SQL Server you're using. I have included the steps for the second option below, assuming you are running Windows. The steps vary a little if you are running Linux. Let me know if you have any questions. Steps to re-enable TLS V1 and TLS V1.1: * https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue 1. Launch the Notepad application as an Administrator 2. Open the java.security file located in `C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\conf\security` 3. Remove TLS V1 and TLS V1.1 from the list of `jdk.tls.disabledAlgorithms` 4. Restart the Gateway Service TLS 1.2 Support for Microsoft SQL Server: [https://support.microsoft.com/en-us/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe](https://support.microsoft.com/en-us/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe) ``` ---
**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:** [October 3, 2023, 4:55pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/5 "2023-10-03T16:55:21Z")
I hope they explained this is a stopgap solution to use until you upgrade your ancient insecure SQL Server instance. ---
**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:** [October 3, 2023, 5:01pm UTC](https://forum.inductiveautomation.com/t/after-upgrading-from-8-1-13-to-8-1-32-i-have-a-one-db-is-down-between-tens-of-dbs/79988/6 "2023-10-03T17:01:13Z")
Here's a better way to solve it if you can't upgrade the DB (and I couldn't): - TLS settings won't be overwritten on your next upgrade. - All your other DB connections will have security left as they should be. > [@SQL Express 2005 database connection ideas?](https://forum.inductiveautomation.com/t/sql-express-2005-database-connection-ideas/78728/15): > > I use jTDS for older versions It just works!