-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.2.6, 9.2.7
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
When a draft is published or deleted on Confluence with Microsoft SQL Server, the logs show invalid column exceptions for contentId and descendantId.
Steps to Reproduce
- Create a new Confluence page
- Add a file to the page (xlsx or pdf)
- Exit draft without publishing
- Return to the draft via User Profile > Drafts, and publish the page
- Delete published page
Expected Results
No error should be seen.
Actual Results
The following errors occur in the logs, but the publishing draft and deleting page operations are successful.
atlassian-confluence.log
2025-08-25 11:21:57,887 ERROR [reconciliation-executor:thread-1] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Invalid column name 'contentId'. -- url: /confluence/plugins/drag-and-drop/upload.action | userName: admin | action: upload | referer: https://linux-108789.prod.atl-cd.net/confluence/pages/
atlassian-confluence.log
2025-08-25 11:23:06,092 ERROR [http-nio-8090-exec-4 url: /confluence/rest/page-hierarchy/incoming/count; user: admin] [v2.api.model.ExceptionConverter] convertServiceException No status code found for exception, converting to internal server error : -- url: /confluence/rest/page-hierarchy/incoming/count | userName: admin | referer: https://linux-108789.prod.atl-cd.net/confluence/spaces/OZHAN/pages/1277953/DRAFT+PAGE | traceId: b0c25f4827f198ba javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154) at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1626) at com.atlassian.confluence.links.persistence.dao.hibernate.HibernateLinkDao.countIncomingLinksForContents(HibernateLinkDao.java:67) at com.atlassian.confluence.links.DefaultLinkManager.countIncomingLinksForContents(DefaultLinkManager.java:85) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) .... ..... at java.base/java.lang.Thread.run(Thread.java:1583) Caused by: org.hibernate.exception.SQLGrammarException: could not extract ResultSet at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:103) .... at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1617) ... 448 more Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'descendentid'. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:270) ...
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available