Can't access JIRA after upgrade from 6.1 to 6.3

It gives me this page after upgrade:

JIRA Access Constraints
You cannot access JIRA at present.
Description Time Level Exception
The current license is too old to install this version of JIRA (6.3.11)

Edit License or proceed under Evaluation Terms

Click the "Edit License or proceed under Evaluation Terms", give me this error:

This user could not be authenticated as a JIRA Administrator

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 can't login either by admin/admin or my original jiraadmin/password. So I followed this link, still can't. https://confluence.atlassian.com/display/JIRA/Setting+Properties+and+Options+on+Startup

 

Can anyone help me? It's a Windows 64 bit.

1 answer

Hi Jirong,

Did you already try to setting the system property as advised by the error message? If you don't know how to do it you can had a look in this KB: https://confluence.atlassian.com/display/JIRA/Setting+Properties+and+Options+on+Startup

Another thing you can try is roll back to your previous version, apply your new license (which can be managed in my.atlassian.com), and re-do the upgrade.

And as always, you also can get help with our support engineers at support.atlassian.com.

-Teilor

I've tried to setting the system property as I said in my first post, didn't work. How can I roll back the upgrade?

I can't even login.

I found the rollback document here: https://confluence.atlassian.com/display/JIRA/Rolling+Back+a+JIRA+Upgrade But I didn't backup anything, due to this is a test site and during the upgrade I thought the backup is done automatically.

Without a backup is not possible to roll out to a previous version :( The change in the system property should've worked. Did you stopped and then started again the JIRA instance? Another thing you could try is create a admin user directly in your database following this instructions https://confluence.atlassian.com/display/JIRA/Retrieving+the+JIRA+Administrator#RetrievingtheJIRAAdministrator-IftherearenoInternalJIRAAdministrators , in this case you will need to stop and start again the instance

It's resolved by restarting the server, not service.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

456 views 7 5
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you