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

#1

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?

0 Likes
#2

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

0 Likes
#3

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.

0 Likes
#4

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?

0 Likes
#5

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

1 Like
#6

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?

0 Likes
#7

We resolved the same problem with SQL 2005 following this help


Maybe it can help you

0 Likes
#8

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

0 Likes
#9

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

1 Like
#10

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.

1 Like
#11

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

0 Likes