I got this error too, upgrading for JIRA 6.0.7 to JIRA 7.2.0, (and it was not easy to track down the problem).
I looked at the JIRA “Health Check” (log in as system administrator, go to “Administration | System | Support Tools | Instance Health”. There was an issue here to do with database configuration… but that wasn’t the cause of the error.
Looked at the log file (/var/atlassian/application-data/jira/log/atlassian-jira.log) and happened across the error “This version of JIRA Agile requires a minimum build number of #45 in order to proceed”, which is described with solution here: https://confluence.atlassian.com/jirakb/this-version-of-jira-agile-requires-a-minimum-build-number-of-45-in-order-to-proceed-812222943.html This fixed my problem.
Getting this after a faulty installation. Any solutions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this can happen if an upgrade is interrupted, or started from a dodgy data set (I've just done that myself), or if something genuinely goes wrong with it.
You'll need to read the log file for the full details, and explain what you have done to provoke this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.