# TLS 1.0 error getting the following error when trying to connect to a SQL Server

**URL:** <https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177>\
**Category:** Ignition\
**Created:** [June 20, 2024, 6:16pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177 "2024-06-20T18:16:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rob\_Nieuwenhuizen](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@Rob\_Nieuwenhuizen](https://forum.inductiveautomation.com/u/Rob_Nieuwenhuizen)\
**Post date:** [June 20, 2024, 6:16pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177/1 "2024-06-20T18:16:32Z")

</div>

getting the following error when trying to connect to a sequel Server Does this mean its using TLS 1.2 or 1.3? for security?

Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:939ad548-634f-441f-937a-31bdb83192c8)

---

<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:** [June 20, 2024, 6:18pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177/2 "2024-06-20T18:18:34Z")

</div>

This means your SQL Server version is ancient and does not support TLS 1.2 or 1.3, meanwhile support for TLS 1.0 and 1.1 has been disabled by default for a few years now.

Similar to what's going on in this thread: [Unable to connect to SQL Server 2000 - #9 by PGriffith](https://forum.inductiveautomation.com/t/unable-to-connect-to-sql-server-2000/42247/9)

---

<div class="post-metadata">

**Author:** ![Rob\_Nieuwenhuizen](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@Rob\_Nieuwenhuizen](https://forum.inductiveautomation.com/u/Rob_Nieuwenhuizen)\
**Post date:** [June 20, 2024, 6:23pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177/3 "2024-06-20T18:23:17Z")

</div>

Ok Thanks For the quick reply.

---

<div class="post-metadata">

**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:** [June 20, 2024, 9:48pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177/4 "2024-06-20T21:48:54Z")

</div>

See if my notes on a solution for SQL Express 2005 are relevant.

> [@SQL Express 2005 database connection ideas?](https://forum.inductiveautomation.com/t/sql-express-2005-database-connection-ideas/78728/18):
>
> Thank you so much for the extra trouble with the screenshots. I hadn't found any reference to jTDS in my previous searches and, if I had, I'm not sure that I could have worked out the configuration. It's also the first time I've set up a driver and so your HTML prompts are useful too. For anyone wanting the text to cut and paste in: Property Value Classname net.sourceforge.jtds.jdbc.Driver URL format jdbc:jtds:sqlserver://hostname Connection property instructions Use \<i\>databaseName…

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [June 21, 2024, 8:39pm UTC](https://forum.inductiveautomation.com/t/tls-1-0-error-getting-the-following-error-when-trying-to-connect-to-a-sql-server/92177/5 "2024-06-21T20:39:08Z")

</div>

You can either upgrade the TLS, or edit an specific file in the gateway to allow TLS 1.
