JIRA Access Constraints error. I've been testing the upgrade of our Jira instance from 4.4.4 to 5.2.2 in our dev environment and after rolling back to 4.4.4 from a failed 5.2.2 upgrade attempt, I get the following error.
Failed to start JIRA due to a build number inconsistency. The data present in your database is newer than the version of JIRA you are trying to startup. Database version is: 813 JIRA app version is: 664 Please use the correct version of JIRA. You are running: 4.4.4#664-r167664
I reverted back to a VM snapshot before the up/g of the server and a db back-up before the up/g. Can you advise what could be causing this issue? thanks
The fail startup because JIRA 4.4.4 tried to connect to database that has been upgraded to 5.2.2. What I am suspecting in this case is that, even though the upgrade failed, the database was partially upgraded to 5.2.2.
Rolling back only can be done like https://confluence.atlassian.com/display/JIRA052/Rolling+Back+a+JIRA+Upgrade
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot