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
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs