# SQL Server Connection Faulted **URL:** \ **Category:** Ignition\ **Tags:** database, ignition79\ **Created:** [May 5, 2021, 6:46pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393 "2021-05-05T18:46:27Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://forum.inductiveautomation.com/u/jay)\ **Post date:** [August 7, 2021, 2:55am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/21 "2021-08-07T02:55:07Z")
Phil capitalized the ‘S’ in server, op did not. “SQL Server”: the Sybase RDMS Microsoft purchased. Specify it as Microsoft SQL Server. Ethernet/IP is understandable enough. EtherNet/IP (capital ‘N’ there) is/was a marketing ploy by Allen-Bradley. Keenex vs tissue. I read the post on this forum regularly, thanks all. When I read that question I had no idea which RDMS was involved. I feel a bit dim-witted sometimes. Every reply assumed that it was MS SQL Server. Correctly, I think, but not obvious to me at all. ---
**Author:** ![roshen.borkar](https://avatars.discourse-cdn.com/v4/letter/r/46a35a/32.png) [@roshen.borkar](https://forum.inductiveautomation.com/u/roshen.borkar)\ **Post date:** [August 9, 2021, 4:06pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/22 "2021-08-09T16:06:47Z")
I had the same issue a few days back. I updated my JDBC driver [From 6.0 to 7.2 I believe (sqljdbc4.jar to mssql-jdbc-7.2.1.jre11.jar)] and that fixed it. I refereed the manual to perform this driver update. ([JDBC Drivers and Translators - Ignition User Manual 8.0 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC80/JDBC+Drivers+and+Translators)) ---
**Author:** ![shabir.ahmed](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shabir.ahmed](https://forum.inductiveautomation.com/u/shabir.ahmed)\ **Post date:** [August 19, 2021, 12:51pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/23 "2021-08-19T12:51:49Z")
Thanks alot, It worked for me in V8.1.7 ---
**Author:** ![Kraenbring](https://avatars.discourse-cdn.com/v4/letter/k/f4b2a3/32.png) [@Kraenbring](https://forum.inductiveautomation.com/u/Kraenbring)\ **Post date:** [August 23, 2021, 8:22pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/24 "2021-08-23T20:22:21Z")
This also worked perfectly for me on version 7.8 I just took those two items out of the disabled algorithm string. Had to search elsewhere for the java.security file, but it was easy enough. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/4/84c550e4fd89023140b8176ef17d18580a781379.png) ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [September 7, 2021, 11:33am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/25 "2021-09-07T11:33:01Z")
Just ran into this at our shop when going from 8.1.4 to 8.1.9. While editing the security.conf file did work, will this get overwritten to default installing the next upgrade? ---
**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:** [September 7, 2021, 1:31pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/26 "2021-09-07T13:31:41Z")
Likely. It is distributed with the JRE. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [September 7, 2021, 2:42pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/27 "2021-09-07T14:42:07Z")
That’s what I figured. Looks like I’ll have to squeeze in a service pack update for our 2014 installation. ---
**Author:** ![pgmo](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@pgmo](https://forum.inductiveautomation.com/u/pgmo)\ **Post date:** [September 9, 2021, 9:37am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/28 "2021-09-09T09:37:35Z")
> [@dlorenzo](#): > > I just went through this issue on 8.1.7. If you haven’t fixed it yet, I modified the file C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\conf\security\java.security > > Deleted TLSv1 and TLSv1.1 > > Restarted ignition service and database connections worked just fine. This worked for me too (upgrading from 8.1.2 to 8.1.10 caused all database connections to go faulted) ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [September 14, 2021, 5:59pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/29 "2021-09-14T17:59:06Z")
Just upgraded from V8.1.7 to V8.1.10 and had the same issue and resolved the same way. Is it correct that we will have to do this every time we upgrade from now on unless our IT department upgrade or patch their affected databases SQL Server instances as described here?: [Zulu64 JRE and Database Connection Faults - #2 by Kevin.Herron](https://forum.inductiveautomation.com/t/zulu64-jre-and-database-connection-faults/47152/2) ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [September 14, 2021, 6:00pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/30 "2021-09-14T18:00:51Z")
To quote above: > [@pturmel](#): > > Likely. It is distributed with the JRE. ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [September 14, 2021, 6:08pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/31 "2021-09-14T18:08:31Z")
Yea, was just checking to see if there was perhaps another solution that perhaps IA were working on (eg. while upgrading, checking that file to see if those 2 items had been removed and if so, automatically removing them for the new file. Probably not the best approach to this though I am guessing for reasons that are beyond my understanding. I will see if I can get our IT dep do get this done - hopefully it is not something that they will be too nervous about doing since this is a fairly old but widely used db. ---
**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:** [September 14, 2021, 7:05pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/32 "2021-09-14T19:05:22Z")
Some might see the annoyance dealing with insecure SQL Servers on each upgrade to be a _ **feature** _. ---
**Author:** ![dturner](https://avatars.discourse-cdn.com/v4/letter/d/90ced4/32.png) [@dturner](https://forum.inductiveautomation.com/u/dturner)\ **Post date:** [October 28, 2021, 2:58am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/33 "2021-10-28T02:58:20Z")
This solution worked for me too. I am on version 7.9.5 ---
**Author:** ![tanda](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tanda/32/19154_2.png) [@tanda](https://forum.inductiveautomation.com/u/tanda)\ **Post date:** [November 19, 2021, 1:26am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/34 "2021-11-19T01:26:43Z")
Thank you! Also, thanks to @pturmel for the lead up to this answer. I had to connect to an older server that only accepted TLSv1.0 and this was just what I needed to do. This forum and the folks at Inductive Automation rock! ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [December 2, 2021, 4:12pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/35 "2021-12-02T16:12:26Z")
Just upgraded from V8.1.10 to 8.1.12 and everything worked without editing the config file. Could not find anything in the release notes in regards to this… ---
**Author:** ![Luke\_Moua](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@Luke\_Moua](https://forum.inductiveautomation.com/u/Luke_Moua)\ **Post date:** [December 27, 2021, 10:16pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/36 "2021-12-27T22:16:11Z")
Thank you, this worked for me as well. Running SQL Server 2008 10.50.6000.34 Ignition Version: 8.1.9 ---
**Author:** ![david.rigby](https://avatars.discourse-cdn.com/v4/letter/d/5f9b8f/32.png) [@david.rigby](https://forum.inductiveautomation.com/u/david.rigby)\ **Post date:** [March 14, 2022, 12:13am UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/37 "2022-03-14T00:13:56Z")
Crazy stuff. I have recently upgraded 3 systems 8.1.1 to 8.1.14, 8.1.7 to 8.1.14 and 8.1.13 to 8.1.14 All using SQL server 2019 with the default instance and had no issue. I just created a new test VM and installed 8.1.14 direct (again SQL 2019 default instance) and got the issue described above. Thanks to all who contributed as this would have been a real head scratcher. regards Dave ---
**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\ **Post date:** [March 22, 2022, 4:34pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/38 "2022-03-22T16:34:17Z")
To those stumbling upon this thread, Support has released a knowledge base article that covers the workaround for this issue: [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:** ![Tiassa\_Toukou](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Tiassa\_Toukou](https://forum.inductiveautomation.com/u/Tiassa_Toukou)\ **Post date:** [October 27, 2022, 5:30pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/39 "2022-10-27T17:30:29Z")
One Solution that solved my issue to was to add ";encrypt=false" to the end of my connect URL example : " jdbc:sqlserver://Hostname\InstanceName;encrypt=false" ---
**Author:** ![Diego\_Aaron\_Gonzalez](https://avatars.discourse-cdn.com/v4/letter/d/9de053/32.png) [@Diego\_Aaron\_Gonzalez](https://forum.inductiveautomation.com/u/Diego_Aaron_Gonzalez)\ **Post date:** [November 21, 2022, 6:47pm UTC](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393/41 "2022-11-21T18:47:32Z")
thanks! [Previous page](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393.md?page=1) [Next page](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393.md?page=3)