SQL exception thrown by the Active Objects library when using incompatible JDBC driver

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Symptoms

The error occurs generally doing a database operations, for example upon modifying the sprint date, JIRA triggers the operation to database which throw the following error in atlassian-jira.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 2012-10-09 11:07:26,950 http-443-23 ERROR [500ErrorPage.jsp] Exception caught in 500 page There was a SQL exception thrown by the Active Objects library: Database: - name:Microsoft SQL Server - version:10.50.1600 - minor version:50 - major version:10 Driver: - name:Microsoft JDBC Driver 4.0 for SQL Server - version:4.0.2206.100 com.microsoft.sqlserver.jdbc.SQLServerException: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ','.   Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ','. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)

Diagnosis

Check if you are using the correct driver for Database, which is located under <JIRA install>/WEB-INF/lib and must be jTDS.

Cause

JIRA does not fully work with the Microsoft JDBC driver.

Solution

Resolution

  1. Shutdown JIRA

  2. Remove Microsoft JDBC driver from your <JIRA install>/WEB-INF/lib

  3. Follow the documentation instructions on how to add a JTDS driver

You can see the supported database drivers here: Supported Platforms

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.