Upgrade failed from Confluence 7.2.1 to 7.13

[Marcelo Mensa]

Upgrade looks like it was successful yet getting the following when it tries to start
Upgrade failed. Please consult the system logs for details. You will need to fix these problems, restore your database and confluence home directory to the pre upgrade state. Then retry the upgrade. Upgrade error message: Upgrade task com.atlassian.confluence.upgrade.upgradetask.DenormalisedSpacePermissionsUpgradeTask@3c530ab5 failed during the SCHEMA_UPGRADE phase due to: StatementCallback; bad SQL grammar [DROP TRIGGER IF EXISTS denormalised_space_permission_trigger]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'IF'.

[Charlie Misonne · Accepted solution]

There is a bug report about this issue: CONFSERVER-61145

Are you using Microsoft SQL server?
And is your database version compatible with Conflunece 7.13?  You can check that on https://confluence.atlassian.com/doc/supported-platforms-207488198.html
Only 2016 and 2017 are supported.

If you are not on a supported database version you won't be able to perform a successful upgrade I'm afraid.

[Marcelo Mensa]

Yes, to SQL server.  Sadly on an older version and the next version we have is SQL 2019.  I'll have to see if I can find a 2016 SQL server.

thanks.

[Charlie Misonne]

Ok good luck!

For your information: the feature request vor SQL Server 2019 is still open: https://jira.atlassian.com/browse/CONFSERVER-59751

[Marcelo Mensa]

@Charlie Misonne so after my massive failure back in August left me in mid upgrade I was finally able to revisit this.  To which I resolved and am running on SQL 2019 in an FCI cluster.

First off restored the database as is as I couldn't find any prior backups.  Then had to deal with firewalls because nothing ever comes easy.  I then found where people had mentioned the config.xml to where I can update the connection string.  

That all done the upgrade looked like it completed itself and I was able to log in.  Which initially it all looked off app wise.  I then went ahead and upgrade to 7.15.0.  This fixed the rest of the issues as it upgrades several components. 

[Marcelo Mensa]

@Charlie Misonne oh I did have to fight with the confluence.cfg.xml to get it to use the correct port when calling a named instance.  I tried a couple of things but Confluence connected when I did the following
jdbc:sqlserver://server:portnumber

I tried instance name and it kept defaulting to port 1433.  SQL browser is on.

thank you again.