java.sql.SQLException: Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication

Ignition
21

What is the exact error (full stack trace) you get? Does that DLL match the JDBC driver version you have installed?

22

Hi Kevin,

Error on Status -> CONNECTIONS -> Databases -> Details:

Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication. ClientConnectionId:0cdd34c6-5fc2-4c53-a879-c126acb8fd26)

I'm not exactly sure how to get the full stack trace - Diagnostics -> Logs?

In my C:\Program Files\Inductive Automation\Ignition\user-lib\jdbc folder, I have

mssql-jdbc-7.2.1.jre11.jar

and a

mssql-jdbc-9.2.1.jre11.jar

So I guess I should have downloaded a different driver? Like the 9.2.1 driver? Trying now.

23

Wait no, my Ignition gateway version is 8.1.28 which the documentation says runs java 11 which the 12.4 driver should be good with as far as I can tell.

24

There must be only one jar for a particular DB brand. (Ending up with two usually means a failed JDBC install at some point.) Delete one and restart your gateway. Then install the jar that matches the DLL you want. Check back that you didn't strand another old jar.

25

Thanks Phil, ok, so I deleted the older mssql-jdbc-7.2.1.jre11.jar and restarted the gateway.

I then decided that I would update our Ignition systems from 8.1.28 to current 8.1.33 as the documentation indicates that java version recently changed from 11 to 17 and I thought I may as well while I am here.

My gateway now says it is running java version 17.0.8+7-LTS, I have the mssql-jdbc_auth-12.4.2.x64.dll file in the lib folder. I also have mssql-jdbc-9.2.1.jre11.jar in the jdbc folder with no other jar files for the db brand - shouldn't there now be a jre17.jar in there now?

Still getting the same error...

26

I'm wondering if maybe I should try upgrading the JDBC driver from mssql-jdbc-9.2.1.jre11.jar to mssql-jdbc-12.4.2.jre11.jar as described here:

JDBC Drivers and Translators - Ignition User Manual 8.1 - Ignition Documentation

27

Consider taking a look at the SQL Server JDBC Driver support matrix: https://learn.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver16

I don't think it is a bad idea to go to the latest supported JDBC driver if possible. You should also be able to use the .jre17 variants with 8.1.33+.

EDIT: after taking a peek at the latest (at time of writing) 12.4 version, it looks like they've not done a build that is leveraging JDK17 features, so the .jre11 variant is still the latest choice. :+1:

1 Like
28

One thing I'll mention is that we leave your JDBC drivers in place on upgrade. Also, the native DLL for auth needs to match the JDBC driver version. So you're on the right path with your proposal to match up the JDBC JAR to mssql-jdbc-12.4.2.jre11.jar.

1 Like
29

If I try to upgrade JDBC driver and things go south how would I restore to previous? Would a gateway restore from backup get me back?

30

Thanks!

31

Pssst! If you reply via email, delete the signatures, images, legal notices, and quoted material that you would normally get, to comply with this forum's neatness rules. You should edit the above comment accordingly.

(If you can't get your emails to conform for any reason, don't use email replies at all.)

2 Likes