Generally, this is related to a collation issue, so you could use Daniel's advice in the thread below just to rule that out. Is that right? There haven't been any config changes made in the past, perhaps that didn't apply correctly until this most recent reboot? So you confirm that you've been running on Confluence 7.2.1 for a while now, without any issues, until shutting down Confluence since last weekend. 20:26:59,062 WARN doRollback Performing rollback.Īny assistance pointing me in the right direction to get this back up and running is greatly appreciated! Error: Hibernate operation: could not execute statement bad SQL grammar nested exception is .jdbc4.MySQLSynta圎rrorException: Table 'confluence.scheduler_run_details' doesn't exist 20:26:59,062 WARN doCommit Commit failed. 20:26:59,062 ERROR mapManagedFlushFailure HHH000346: Error during managed flush 20:26:59,061 ERROR logExceptions Table 'confluence.scheduler_run_details' doesn't exist "Using Java: D:\jre1.8.0_231\bin\java.exe"Įrror: Unable to access jarfile C:\Program My Jira Core installation is functioning fine.Īlso, not sure this is applicable, but when starting confluence from the command prompt I see this: No other changes have been made to the server or to Confluence. I had to shutdown the server hosting Confluence over the weekend due to a scheduled power outage, I received the above errors when trying to start Confluence back up on Monday morning. "could not extract ResultSet SQL nested exception is : could not extract ResultSet" Fatal error during startup sequence: :mananagedjobs (Start and stop the Managed Scheduled Jobs)" When starting up Confluence 7.2.1 on Windows Server 2019 using MySQL 5.7, the web page displays "Confluence had problems starting up" followed by:
0 Comments
Leave a Reply. |