Task Report Macro Generates PostgreSQL Error

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

Problem

Task report macro generates an error when trying to be used.

1 Error rendering macro 'tasks-report-macro' : There was a SQL exception thrown by the Active Objects library: Database: - name:PostgreSQL - version:8.3.23 - minor version:3 - major version:8 Driver: - name:PostgreSQL Native Driver - version:PostgreSQL 9.2 JDBC4 (build 1002) org.postgresql.util.PSQLException: ERROR: syntax error at or near

The following appears in the atlassian-confluence.log for the Task Report Macro causing the issue:

1 2 3 4 5 6 7 8 9 10 11 12 13 ERROR [http-bio-2005-exec-886] [xhtml.view.macro.ViewMacroMarshaller] marshalInternal Error rendering macro: tasks-report-macro -- url: /rest/tinymce/1/macro/preview | userName: xxx.xxxxx | referer: http://xxxxxx:xxxx/pages/editpage.action?pageId=10879059 com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library: Database: - name:PostgreSQL - version:8.3.23 - minor version:3 - major version:8 Driver: - name:PostgreSQL Native Driver - version:PostgreSQL 9.2 JDBC4 (build 1002) org.postgresql.util.PSQLException: ERROR: syntax error at or near "T_DUE_DATE"

Cause

This error is seen when an unsupported version of PostgreSQL is installed.

Resolution

  • Please reference the following document to determine what versions PostgreSQL are compatible with the version of Confluence: Supported Platforms

  • Moving to a supported version of PostgreSQL will correct the issue.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.