# Perspective 8.3 Upgrade Issue: JDBC driver **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [November 7, 2025, 6:30pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045 "2025-11-07T18:30:01Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 6:30pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/1 "2025-11-07T18:30:01Z")
I just upgraded our gateway to 8.3. The only issue I’m having is the screenshot below. Any sugestions? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/2/a2e860c2a7d37f48fddf678f969e81aca83afb0e.png) ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [November 7, 2025, 6:34pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/2 "2025-11-07T18:34:11Z")
Copy the full error stack(click that copy button) and post it here as pre-formatted text. Please see [Wiki - how to post code on this forum](https://forum.inductiveautomation.com/t/wiki-how-to-post-code-on-this-forum/77831). The chopped off text contains important information for troubleshooting. Additionally, you should check to see if the SQL server Driver is actually present in the JDBC driver folder on your gateway. It should come with Ignition on install but maybe something happened. ---
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 6:39pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/3 "2025-11-07T18:39:26Z")
```python java.sql.SQLException: Cannot load JDBC driver class 'com.microsoft.sqlserver.jdbc.SQLServerDriver' at org.apache.commons.dbcp2.DriverFactory.createDriver(DriverFactory.java:53) at org.apache.commons.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:474) at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:541) at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:723) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.getConnectionInternal(DatasourceImpl.java:361) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.runTest(DatasourceImpl.java:313) at com.inductiveautomation.ignition.gateway.datasource.DatasourceManagerImpl$FaultedDatasourceRetryer.lambda$newRetryRunnable$0(DatasourceManagerImpl.java:1109) at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:593) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source) at java.base/java.lang.ClassLoader.loadClass(Unknown Source) at org.eclipse.jetty.ee10.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:443) at java.base/java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.commons.dbcp2.DriverFactory.createDriver(DriverFactory.java:48) at org.apache.commons.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:474) at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:541) at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:723) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.getConnectionInternal(DatasourceImpl.java:361) at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.runTest(DatasourceImpl.java:313) at com.inductiveautomation.ignition.gateway.datasource.DatasourceManagerImpl$FaultedDatasourceRetryer.lambda$newRetryRunnable$0(DatasourceManagerImpl.java:1109) at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:593) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) ``` ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [November 7, 2025, 6:40pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/4 "2025-11-07T18:40:20Z")
Do you have the MSSQL JDBC driver module (they're new to 8.3) installed? You either need that or to manually add an MSSQL driver jar. The installation/upgrade process _should_ have installed the module for you automatically. ---
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 6:56pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/5 "2025-11-07T18:56:01Z")
Yes, the module is installed and showing active. ---
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 6:56pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/6 "2025-11-07T18:56:39Z")
![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/e/0eea1528cff865bf4fc8b2278a39e36bcb795017.png) ---
**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 7, 2025, 6:59pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/7 "2025-11-07T18:59:55Z")
Is this the first gateway start since upgrade? Tried restarting yet? ---
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 7:01pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/8 "2025-11-07T19:01:48Z")
I have not restarted the server, is that what you're asking? I did just update the gateway a few hours ago. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [November 7, 2025, 7:02pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/9 "2025-11-07T19:02:24Z")
In addition to Kevin's question, does any of the underlying DB related config (database drivers, translators, etc) show as 'disabled' in the web UI? Try restarting just the gateway, first. You may also need support to take a look at this point. ---
**Author:** ![Ros\_Alexander1](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@Ros\_Alexander1](https://forum.inductiveautomation.com/u/Ros_Alexander1)\ **Post date:** [November 7, 2025, 7:14pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/10 "2025-11-07T19:14:31Z")
Restarting the gateway was the trick! ---
**Author:** ![Austin\_Li](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@Austin\_Li](https://forum.inductiveautomation.com/u/Austin_Li)\ **Post date:** [December 12, 2025, 7:22pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/11 "2025-12-12T19:22:49Z")
I just went through an upgrade from 8.1 to 8.3, and I had an error with my MSSQL server drivers as well: “Error - either required files are missing or classname is incorrect”. Gateway restarts did not fix the issue for me, as I was missing jar files. I had to follow this article [JDBC Drivers and Translators | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.3/platform/database-connections/connecting-to-databases/jdbc-drivers-and-translators#upgrade-a-jdbc-driver) and download the mssql-jdbc-13.2.1.jre11.jar file from Microsoft [Download - JDBC Driver for SQL Server | Microsoft Learn](https://learn.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-ver15). Then I uploaded the jar file to 8.3 under Connections \> Databases \> Settings. After that, my databases connections were still faulted with the new driver giving me this error: “Cannot create PoolableConnectionFactory ("encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.” Then I looked at this other article [Connecting to Microsoft SQL Server Express | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.3/platform/database-connections/connecting-to-databases/connecting-to-microsoft-sql-server-express). I had to add a parameter to the “Extra Connection Properties” field and separate with a semicolon under each connection like: trustServerCertificate=true; databaseName=yourDB That ended up doing the trick. ---
**Author:** ![andrewbrown](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@andrewbrown](https://forum.inductiveautomation.com/u/andrewbrown)\ **Post date:** [January 31, 2026, 1:26am UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/12 "2026-01-31T01:26:40Z")
Just following up on this. We recently did an update from 8.3.2 → 8.3.3 and have experienced the same issue. JDBC module installed, but still getting a faulted connection state. Restarted the gateway. no luck. Installed the new JDBC from microsoft as the above says. no luck. May have to drop back to 8.3.2? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [February 2, 2026, 5:00pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/13 "2026-02-02T17:00:49Z")
You should contact support, because "a database connection is faulting" could have any number of root causes and is very probably totally unrelated to the original issue in this thread. ---
**Author:** ![jeremy.menzies](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@jeremy.menzies](https://forum.inductiveautomation.com/u/jeremy.menzies)\ **Post date:** [May 6, 2026, 4:11pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/14 "2026-05-06T16:11:07Z")
Same thing happened to me, Upgraded from 8.3.2 to 8.3.6 and stopped connecting to MSSWL. Updated JAR to v13.4 updated all SP in SQL Server tried disabling security ended up downgrading back, back online as soon as went back to 8.3.2 ---
**Author:** ![Timotei\_Vasiu](https://avatars.discourse-cdn.com/v4/letter/t/bbce88/32.png) [@Timotei\_Vasiu](https://forum.inductiveautomation.com/u/Timotei_Vasiu)\ **Post date:** [June 19, 2026, 9:57am UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/15 "2026-06-19T09:57:50Z")
Did you manage to use the latest v13.4 jar file for MSSQL somehow? ---
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [June 19, 2026, 12:13pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/16 "2026-06-19T12:13:49Z")
This is a good one to contact support for because a lot of things can cause it. I've found this guide to be helpful for troubleshooting issues like this as well. [https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue](https://support.inductiveautomation.com/hc/en-us/articles/4417310204813-TLS-v1-0-and-v1-1-Microsoft-SQL-Server-Database-connection-issue) ---
**Author:** ![Timotei\_Vasiu](https://avatars.discourse-cdn.com/v4/letter/t/bbce88/32.png) [@Timotei\_Vasiu](https://forum.inductiveautomation.com/u/Timotei_Vasiu)\ **Post date:** [June 22, 2026, 3:43pm UTC](https://forum.inductiveautomation.com/t/perspective-8-3-upgrade-issue-jdbc-driver/112045/17 "2026-06-22T15:43:04Z")
So I am using Ignition 8.3.4 and just added the mssql-jdbc-13.4.0.jre11.jar in combination with mssql-jdbc\_auth-13.4.0.x64.dll and that works without any issues to connect to MSSQL. I had to add the trustServerCertificate=true and the integratedSecurity=True in extra connection properties. I will update my servers to 8.3.7 soon and hope nothing breaks 😃