When a draft is published the logs show invalid column exceptions for contentId

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 9.2.15, 9.2.17, 9.2.20
    • Component/s: Editor - Synchrony
    • None
    • 2
    • Severity 3 - Minor

      Issue Summary

      When a draft is published the logs show invalid column exceptions for contentId

      Steps to Reproduce

      1. Install Confluence 9.2.17 or higher with Microsoft SQL server 2019
      2. Create a new Confluence page
      3. Add a file to the page (xlsx or pdf)
      4. Exit draft without publishing
      5. Return to the draft via User Profile > Drafts, and publish the page

      Expected Results

      Page is deleted/edited without issues and no errors in logs

      Actual Results

      Page is deleted/editted without issues but below errors in logs

       -- url: /confluence/setup/finishsetup.action | userName: anonymous | action: finishsetup | referer: https://linux-126474.prod.atl-cd.net/confluence/setup/setupadministrator-start.action | traceId: a18f64a695a067ce
      2026-05-29 09:27:14,140 WARN [reconciliation-executor:thread-4] [engine.jdbc.spi.SqlExceptionHelper] logExceptions SQL Error: 207, SQLState: S0001
       -- url: /confluence/setup/finishsetup.action | userName: anonymous | action: finishsetup | referer: https://linux-126474.prod.atl-cd.net/confluence/setup/setupadministrator-start.action | traceId: a18f64a695a067ce
      2026-05-29 09:27:14,140 ERROR [reconciliation-executor:thread-4] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Invalid column name 'contentId'.
       -- url: /confluence/setup/finishsetup.action | userName: anonymous | action: finishsetup | referer: https://linux-126474.prod.atl-cd.net/confluence/setup/setupadministrator-start.action | traceId: a18f64a695a067ce
      2026-05-29 09:27:14,141 ERROR [reconciliation-executor:thread-4] [internal.content.bodycontentquerier.BodyContentQuerier] executeQuery Error executing query: could not extract ResultSet
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Shivangi Nayak
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: