# SQL Database became faulty after upgradation from V8.1.13 to V8.1.19

**URL:** <https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 22, 2022, 3:41pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277 "2022-08-22T15:41:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aman\_Pawar](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@Aman\_Pawar](https://forum.inductiveautomation.com/u/Aman_Pawar)\
**Post date:** [August 22, 2022, 3:41pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/1 "2022-08-22T15:41:48Z")

</div>

I've upgraded Ignition from V8.1.13 to V8.1.19. There are three SQL database connections. After upgradation all three connections became faulty. Kindly suggest solution.  
The errors are as given below:

# ================================================================= 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:92a6b6dd-f4ea-4f3f-bb3d-3de7f8e3b85f)

# 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:f11d8c2c-1402-41b2-999c-474168ca48ea)

# 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:d6cd5476-941e-4459-b872-6cd54438433b)

---

<div class="post-metadata">

**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:** [August 22, 2022, 3:43pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/2 "2022-08-22T15:43:49Z")

</div>

This response and its linked responses should help explain: [Connection to MSSQL(2014) lost when updated to 8.1 (from 7.9) - #4 by Kevin.Herron](https://forum.inductiveautomation.com/t/connection-to-mssql-2014-lost-when-updated-to-8-1-from-7-9/57332/4)

---

<div class="post-metadata">

**Author:** ![Aman\_Pawar](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@Aman\_Pawar](https://forum.inductiveautomation.com/u/Aman_Pawar)\
**Post date:** [August 22, 2022, 3:54pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/3 "2022-08-22T15:54:28Z")

</div>

So do I need to upgrade TLS 1.2 or TLS 1.3?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 22, 2022, 3:57pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/4 "2022-08-22T15:57:59Z")

</div>

You don’t “upgrade TLS”; you upgrade your SQL server install so that it understand modern protocols.

TLS 1.2 was released in 2008.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [August 22, 2022, 4:14pm UTC](https://forum.inductiveautomation.com/t/sql-database-became-faulty-after-upgradation-from-v8-1-13-to-v8-1-19/63277/5 "2022-08-22T16:14:22Z")

</div>

I would suggest taking a look at the following guide. The fix here may be as easy as upgrading the driver. If that doesn’t work though, I would suggest looking at the other options. Since you were on 8.1.13 which has TLSv1 and TLSv1.1 disabled by default, it’s possible someone had previously re-enabled those in the java security file which is why you were able to connect before upgrading to 8.1.19. I would highly suggest upgrading your SQL Server to support later versions of TLS and upgrading your JDBC driver instead of just re-enabling the older versions of TLS.

> **[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)**
>
> Summary
> A recent update to Java 8 (8u291), which also applies to Java 11.0.11 and above, has disabled TLS 1.0 and 1.1. This has resulted in cases of Ignition's connection to Microsoft SQL Server (M...