# \[FEEDBACK/BUG?\] Database Connections faulted after upgrade to Ignition 8.0 **URL:** \ **Category:** Ignition Early Access\ **Created:** [November 11, 2018, 10:40pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751 "2018-11-11T22:40:53Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![bennuss11](https://avatars.discourse-cdn.com/v4/letter/b/e9bcb4/32.png) [@bennuss11](https://forum.inductiveautomation.com/u/bennuss11)\ **Post date:** [November 11, 2018, 10:40pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/1 "2018-11-11T22:40:53Z")
Unexpected Behavior : Database connections faulted after upgrading to Ignition 8. Connection to Local database is fine, network databases faulted. Database Status message: “Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: “Unexpected rethrowing”.)” Expected Behavior: Working database connections. Steps: - Checked with other gateway backups and with new connections. Same issue. - Downgraded Ignition versions to verify connections worked in 7.9.9. They do. Info: Version: 8.0.0-beta0 (b2018111102) Installed Java Versions: Oracle Java 8 Update 151 Database Connection Driver: Microsoft SQLServer JDBC Driver (4.0) Any ideas on what is going on? ---
**Author:** ![anjoroge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/anjoroge/32/6698_2.png) [@anjoroge](https://forum.inductiveautomation.com/u/anjoroge)\ **Post date:** [November 12, 2018, 4:30pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/2 "2018-11-12T16:30:55Z")
Hi bennuss11 It seems like ignition is no longer connecting to you database. It may be because, there is problem with your network not seeing the database. You could try creating a new connection to the database and see If you are able to connect. Usually when you upgrade from 7.9.9 to 8.0 the connection should be retained. You can also try substituting localhost on you connection with the ipaddress of your machine. In the edit connection settings e.g.jdbc:mysql://ipaddress:3306/test. to see if this helps ---
**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\ **Post date:** [November 12, 2018, 4:44pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/3 "2018-11-12T16:44:37Z")
We have also seen issues with older JDBC drivers not working properly with Java 11 that the Ignition gateway is now packaged with. Please try [updating the driver in Ignition](https://docs.inductiveautomation.com/display/DOC79/JDBC+Drivers+and+Translators#JDBCDriversandTranslators-UpgradingaJDBCDriver) to the `jre10` version of the [7.0 driver available from Microsoft](https://www.microsoft.com/en-us/download/details.aspx?id=57175). This has corrected all issues we have run into so far. ---
**Author:** ![bennuss11](https://avatars.discourse-cdn.com/v4/letter/b/e9bcb4/32.png) [@bennuss11](https://forum.inductiveautomation.com/u/bennuss11)\ **Post date:** [November 12, 2018, 11:42pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/4 "2018-11-12T23:42:58Z")
Well, I have tried a few of your suggestions, and I have learned a few things. In checking the SQL versions of the databases I am trying to connect to, the versions I cannot connect to are SQL Server 2000. (Why we are still using SQL 2000 is a whole different question). So far the others I have tried are all version 2012+, which all work fine. @ggross, since the 7.0 driver does not support SQL version earlier than SQL Server 2008, i do not believe it will not solve my issue. Any ideas on how to connect to SQL versions older than 2008? ---
**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:** [November 13, 2018, 12:02am UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/5 "2018-11-13T00:02:50Z")
Might be approaching an unsupportable configuration according the support matrix: [https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-2017](https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-2017) ---
**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\ **Post date:** [December 17, 2018, 4:26pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/6 "2018-12-17T16:26:05Z")
I just restored a backup from one of my 7.9 gateways to 8. I was using MSSQL JDBC 6.2 and that was copied as part of the backup, but of course that was not compatible. Can their be a warning/upgrade message or alert to notify during restore (prob best on the commissioning check) that the installed JDBC driver is known not to work? ---
**Author:** ![andrea.minu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.minu/32/3326_2.png) [@andrea.minu](https://forum.inductiveautomation.com/u/andrea.minu)\ **Post date:** [August 2, 2019, 6:36am UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/7 "2019-08-02T06:36:14Z")
We resolved the same problem with SQL 2005 following this help > Maybe it can help you ---
**Author:** ![automatisme.iton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/automatisme.iton/32/5254_2.png) [@automatisme.iton](https://forum.inductiveautomation.com/u/automatisme.iton)\ **Post date:** [August 22, 2019, 5:44pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/8 "2019-08-22T17:44:30Z")
Hello Andrea can you tel us what change you have make exactly, and the version of JDBC you use Whe have the same issue between SQL server 2005 and ignition 8.0 ---
**Author:** ![andrea.minu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.minu/32/3326_2.png) [@andrea.minu](https://forum.inductiveautomation.com/u/andrea.minu)\ **Post date:** [August 26, 2019, 6:51am UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/9 "2019-08-26T06:51:04Z")
HI As described in the link, I just modified the **java.security** file in the **JRE** Install folder and remove the value: **3DES\_EDE\_CBC** from the **jdk.tls.disabledAlgorithms** in the file: Program Files\Java"JRE Version"\lib\security. I have used the version of the Jdbc driver included in Ignition V8 Andrea ---
**Author:** ![larryjones](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/larryjones/32/4102_2.png) [@larryjones](https://forum.inductiveautomation.com/u/larryjones)\ **Post date:** [October 24, 2019, 8:36pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/10 "2019-10-24T20:36:52Z")
With Ignition 8, that “java.security” file is located at “C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\conf\security” on a Windows computer. ---
**Author:** ![yzhang](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@yzhang](https://forum.inductiveautomation.com/u/yzhang)\ **Post date:** [December 10, 2019, 8:36pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/11 "2019-12-10T20:36:16Z")
> [@larryjones](#): > > C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\conf\security Thanks Andrea, it is working for me. what I've done is modify the java.security file in the C:\Program Files\Inductive Automation\Ignition folder and remove the value: 3DES\_EDE\_CBC from the jdk.tls.disabledAlgorithms in the file Then restart the Ignition gateway ---
**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:** [January 14, 2021, 4:16pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/12 "2021-01-14T16:16:32Z")
Split this topic on January 14, 2021, 4:16pm UTC 2 posts were split to a new topic: [Unable to connect to SQL Server 2000](https://forum.inductiveautomation.com/t/unable-to-connect-to-sql-server-2000/42247) ---
**Author:** ![andrea.minu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.minu/32/3326_2.png) [@andrea.minu](https://forum.inductiveautomation.com/u/andrea.minu)\ **Post date:** [October 20, 2021, 3:03pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/13 "2021-10-20T15:03:13Z")
summarizing after some test With Ignition 8.x you should delete the **3DES\_EDE\_CBC** and the **TLSv1** values from java.security file. Instead if you need use the integrated security of Windows for connect to the database SQL server you should also download the mssql-jdbc\_auth-x.x.x.x64.dll ( from microsoft web site as described in the help manual) and renamed it to sqljdbc\_auth.dll and copy this dll in C:\Program Files\Inductive Automation\Ignition\lib\ ---
**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\ **Post date:** [June 7, 2022, 10:37am UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/14 "2022-06-07T10:37:34Z")
Hi, I updated the MSSQL driver (jre11) as explained in the IA docs ([JDBC Drivers and Translators - Ignition User Manual 8.0 - Ignition Documentation](https://docs.inductiveautomation.com/pages/viewpage.action?pageId=26020735)) I also removed the 3DES\_EDE\_CBC from the jdk.tls.disabledAlgorithms in the file and restarted Ignition. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/2/f2c59ae9d810218f5a912ddf5989f1103073e6c0.png) But after upgrading I’m getting the following error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/85ebfa17be774e33f33147bda0e90f961b138087.png) Could somebody help me find the solution to this problem? I’m using Ignition 8.0.4 and MSSQL 2019. They are installed on separate machines and are installed on Linux. It seems to only be the case when restoring a gateway backup. If I copy all the resources to a fresh gateway (same version) and create a new database connection then the problem doesn’t seem to appear. ---
**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:** [June 7, 2022, 11:58am UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/15 "2022-06-07T11:58:38Z")
The JDBC driver is stored in the gateway backup. So restoring the gateway backup replaces your newer JDBC driver with an older one. Re-upgrade the JDBC driver **after** restoring the backup. ---
**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\ **Post date:** [June 7, 2022, 12:13pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/16 "2022-06-07T12:13:45Z")
Hi Phil, I did re-upgrade the JDBC driver after restoring the backup. But still no luck. ---
**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 7, 2022, 12:23pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/17 "2022-06-07T12:23:45Z")
The error you’re seeing means the server certificate is not trusted by Ignition. You’ll need to add it to the “supplemental certificates” folder in the Ignition Gateway so it gets imported to the trust store. [Adding Security Certificates into KeyStores - Ignition User Manual 8.1 - Ignition Documentation (inductiveautomation.com)](https://docs.inductiveautomation.com/display/DOC81/Adding+Security+Certificates+into+KeyStores) ---
**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\ **Post date:** [June 7, 2022, 12:56pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/18 "2022-06-07T12:56:29Z")
Hi Kevin, Do you have a little more background on this? How do I get this certificate for example? Or should I contact support on this? ---
**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 7, 2022, 12:58pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/19 "2022-06-07T12:58:49Z")
I don’t know how to get it exactly… it’s going to be something you get out of a configuration tool or something for SQL Server. Presumably the server has a self-signed certificate right now, which is why Ignition doesn’t trust it by default. Support may be able to help or they may end up just being your partner in Googling. edit: I think you can also bypass certificate validation by adding `trustServerCertificate=true` to the JDBC connection parameters. ---
**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\ **Post date:** [June 7, 2022, 1:06pm UTC](https://forum.inductiveautomation.com/t/feedback-bug-database-connections-faulted-after-upgrade-to-ignition-8-0/20751/20 "2022-06-07T13:06:58Z")
> [@Kevin.Herron](#): > > trustServerCertificate=true Adding this to the JDBC connection parameters worked for me.