I am having the same issue with version 8.1.1 connecting to a SQL server 2000 database. One thing I noticed is there is not a java.security file in the security folder, just a java file. It contained the referenced configuration ( 3DES_EDE_CBC from the jdk.tls.disabledAlgorithms ) so I am guessing…

I had to use jTDS. [image] java.sql.SQLException after migration 7.9 to 8.1 and with SQL Server 2005 Database Connection Ignition The newer versions of the jdbc driver dropped support for the older versions. I ended up using jTDS for those. https://sourceforg…

I had a similar issue with MSSQL v10, Server 2008 R2 going to Ignition v8.1.6 from v7.9.14. Updated the driver to MSSQL JDBC v7.2.2 for jre11 and kept getting the following error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]" The SQL server (whic…

Just upgraded from V8.1.3 to V8.1.7 and we lost one of our database connections: Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accept…

Once the V8.1.7 → V8.1.3 installation was complete the connection became valid again…

8.1.7 deprecates TLS 1.0 and 1.1 due to an upgrade in our bundled Java version, as mentioned in the changelog and the user manual .

See also this topic for a work-around; [image] SQL Server Connection Faulted Ignition After replacing a development installation of Ignition 8.1 with 7.9.17, I am suddenly unable to communicate with my local SQL server. The connection was fine before the reinstall but now…

Rather than downgrading Ignition’s TLS preferences you should prefer upgrading or patching your SQL Server instances: Zulu64 JRE and Database Connection Faults - #2 by Kevin.Herron

No patches for anything older than SQL Server 2008.

Hi guys, this morning I upgraded both master and backup gateway from V8.1.3 to V8.1.7 then on the master, removed TLSv1 and TLSv1.1 from line 729 of the java.security file and restarted the gateway. Master now has a valid connection to the previously connection faulted database. Unfortunately, when …

Any chance of a typo when editing the backup’s java.security file? Maybe copy the working one from the master to the backup?

Unable to connect to SQL Server 2000

Ignition

pturmel June 15, 2021, 7:17pm 10