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 Soc…

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

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 c…

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 to the jre10 version of the 7.0 driver available from Microsoft . This has corrected all issues we have run into so far.

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 trie…

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…

We resolved the same problem with SQL 2005 following this help [JVz] Springboot 2.0 unable to access SQL Server Database java, sql-server, spring-boot, hikaricp asked by JVz on 01:14AM - 20 Jul 18 UTC Maybe it can help you

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

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 Andre…

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.

[image] 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 j…

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 mic…

Inductive Automation Forum

[FEEDBACK/BUG?] Database Connections faulted after upgrade to Ignition 8.0

Ignition Early Access