When using MSSQL 2019, we are unable to create a support zip on Crowd 4.3.0
Crowd 4.3.0 supports the MSSQL 2019 database, based on the supported platforms:
Expected results
Crowd successfully creates a support zip.
Observed behavior
An error is returned on Crowd UI per the screenshot below:
Inside the logs, we can see the following:
2021-07-06 17:20:03,348 http-nio-8095-exec-13 ERROR [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: bundle [com.atlassian.troubleshooting.plugin-crowd] com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.troubleshooting.plugin-crowd] at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95) at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86) at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: com.atlassian.activeobjects.internal.DatabaseProviderNotFoundException: Could not find database provider for data source which uses JDBC driver <jTDS Type 4 JDBC Driver for MS SQL Server and Sybase>
Workaround
Short term
If you must immediately retrieve the Crowd logs for troubleshooting purposes, they will be located on the Crowd_data/logs folder and can be zipped up or tar+gz'd to send to support in liu of a full support zip.
Long term
The jTDS MSSQL JDBC driver that is referenced in the logged error message is deprecated, however if you migrate from the jTDS driver to the official Microsoft JDBC driver you will not have this issue and will be able to successfully generate support zips.
- is caused by
-
ATST-1092 Loading...
- is cloned by
-
KRAK-4563 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...