I have purchased a JIRA starter pack for 10 users. I have installed it in a test machine, created few projects, issues, usres, etc. and tested it. After testing it for few months, I have installed it in our server yesterday.
As I have created all users and required projects in the JIRA in test machine, I have taken a backup from test machine and uploaded it into the JIRA in the server. After this upload is complete, I can't access JIRA anymore.
This is the error message:
JIRA Access Constraints
You cannot access JIRA at present.
The current license is too old to install this version of JIRA (5.2.4)
I have renewed the JIRA licence till April 2013 and I am not sure why am I getting this. Is it because I haven't uninstalled JIRA from the test machine ?
Please find the screen shot attached which refers to my licence details.
A quick response is highly appreciated.
I am having this problem too, just that i am unable to put in the new license because my admin user is not allowed. with following messag:
JIRA cannot proceed with the upgrade as you are not logged in as a JIRA administrator, or this version of JIRA cannot recognize administrators from the version that you have upgraded from. To proceed, log in as a JIRA administrator. If you cannot log in, override this requirement by setting the system property '-Dnon.admin.upgrade=true', then restarting JIRA.
I even tried to put in the -Dnon.admin.upgrade=true and restartet the service but it is not working.
hi , I got below issue after importing a live data dump to new environment rror occurred during export before upgrade: There was a problem backing up data for the null plugin. If necessary, auto-export can be disabled; see http://www.atlassian.com/software/jira/docs/latest/upgrade/autoexport.html com.atlassian.core.AtlassianCoreException: There was a problem backing up data for the null plugin. at com.atlassian.jira.bean.export.AutoExportImpl.exportData(AutoExportImpl.java:111) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:445) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:404) at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:107) at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:55) at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:45) at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:140) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:345) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:215) at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:124) at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:33) at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:86)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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