# Issue after Ignition Server Restart **URL:** \ **Category:** Ignition\ **Tags:** ignition81, database\ **Created:** [February 28, 2025, 2:40pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049 "2025-02-28T14:40:17Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 2:40pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/1 "2025-02-28T14:40:17Z")
Good Morning, Our ignition server restarted over the weekend are are running at Windows 10 box and our version of Igntion is 8.1 nad Java Version 17.0.8+7-LTS We had a few older connects to some windows xp SQL server 2008 R2 pcs that worked just fine before the restart but now they are faulted with the below error. * * * 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: "SQL Server did not return a response. The connection has been closed. ClientConnectionId:de86f50a-de5b-488c-9eb8-59270813b386".) 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: "SQL Server did not return a response. The connection has been closed. ClientConnectionId:de86f50a-de5b-488c-9eb8-59270813b386". at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2670) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1837) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2257) at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1921) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1762) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1077) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:623) 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.SSLException: SQL Server did not return a response. The connection has been closed. ClientConnectionId:de86f50a-de5b-488c-9eb8-59270813b386 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.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:1767) ... 21 more Caused by: java.io.IOException: SQL Server did not return a response. The connection has been closed. ClientConnectionId:de86f50a-de5b-488c-9eb8-59270813b386 at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:780) at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:836) at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:827) at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:1009) at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:997) at java.base/sun.security.ssl.SSLSocketInputRecord.read(Unknown Source) at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source) at java.base/sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source) ... 27 more ## 8.1.35 (b2023120517) Azul Systems, Inc. 17.0.8 Note I have went and took out tls1.0 and tls 1.1 disabled from the java.security path in the igntion folder and no dice anyone got anything else I could try. ---
**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:** [February 28, 2025, 2:53pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/2 "2025-02-28T14:53:15Z")
This looks like a network/firewall issue. Maybe new rules that didn't affect your existing connections. ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 2:53pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/3 "2025-02-28T14:53:29Z")
I am running JDBC 6.4.0.jre8.jar for the mssql jdbc driver ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 2:54pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/4 "2025-02-28T14:54:15Z")
Windows firewall is disabled on both machines no network changes they are going through a dummy switch directly to each over ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 28, 2025, 3:04pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/5 "2025-02-28T15:04:58Z")
> [@troy1](#): > > Caused by: java.io.IOException: SQL Server did not return a response. This is as blindingly obvious a network/firewall error as there can be. It isn't Ignition. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [February 28, 2025, 3:05pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/6 "2025-02-28T15:05:04Z")
Are you certain SQL server is running and can be connected to with anything else? Try SQL Server Management Tools. ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 3:06pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/7 "2025-02-28T15:06:02Z")
SSMS studio works from the same machine with same credentials ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/8 "2025-02-28T15:07:12Z")
Got it resolved I had to disable 3DES\_EDE\_CBC in the java security file I found this on this form post [java.sql.SQLException after migration 7.9 to 8.1 and with SQL Server 2005 Database Connection - Ignition - Inductive Automation Forum](https://forum.inductiveautomation.com/t/java-sql-sqlexception-after-migration-7-9-to-8-1-and-with-sql-server-2005-database-connection/41526) ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 3:11pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/9 "2025-02-28T15:11:17Z")
Was the java.security file 3DES\_EDE\_CBC being blocked in the ignitnio security not direclty the firewall on the pc like I said we dont acutlaly have a firewall in place thanks though ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [February 28, 2025, 3:12pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/10 "2025-02-28T15:12:47Z")
I would question then if it was actually working prior to the restart of the computer. If this wasn't disabled previously, then how was it working before? ---
**Author:** ![troy1](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@troy1](https://forum.inductiveautomation.com/u/troy1)\ **Post date:** [February 28, 2025, 3:17pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/11 "2025-02-28T15:17:50Z")
Could have been updated or changed I know we were having an Issue with the service and created a new ignition service with a new install so that could be it, but I was not involved with that the PLC guy was I am more database IT guy but thanks for your help! (So that file could have been reset) ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [February 28, 2025, 3:41pm UTC](https://forum.inductiveautomation.com/t/issue-after-ignition-server-restart/103049/12 "2025-02-28T15:41:54Z")
If they re-installed, it most definitely was reset and most likely someone previously applied the same fix.