After update to 9.13.0 license is not valid anymore

[Oliver Schneeweiß]

Hello,

I’ve just update my on-premise-installation of Jira to version 9.13.0.

After this, i cannot start the jira-services because my license code (jira starter) is not valid for a data center-installation. 

But I don’t have a data center-installation. I have a starter-edition.

Also if i try to install again my license, it repeats the error-message.

What can i do, to get my installation back to work.

[Brant Schroeder · Accepted solution]

@Oliver Schneeweiß Do you have the ability to roll the update back?  Server is only supported to version 9.12.  9.13 is data center only.

The final server Long Term Support (LTS) releases are Jira Software 9.12, Jira Service Management 5.12, and Confluence 8.5. These LTS versions will be eligible for security updates and bug fixes until server end of support.

[Oliver Schneeweiß]

Thanks for your response.

How could i make a roll-back?

And: there wasn‘t any hint or message, that this update would be a problem! I’ve got several e-mails from atlassian, that we all shall update our jira-installations because of vulnerability. So I’ve done. And now, my installation isn’t working anymore…

[Oliver Schneeweiß]

I have another question:

In my case, there is an option to activate an evaluation license.

But after activation and restart of my server, the old (not working) license is still active.

Does anybody know, how i can enable this evaluation license?

[Brant Schroeder]

@Oliver Schneeweiß Have you submitted a support issue yet to Atlassain? https://support.atlassian.com/contact/  I would suggest doing that as this is just a community forum.  To rollback you would have had to have made a backup at the time of the upgrade or taken a snapshot of your VM.  Did you do either?

[Oliver Schneeweiß]

Hello Brant,

i could solve the problem. I’ve made a rollback to my previous version 9.12.1 and now my jira-installation is working well again.

Thanks for your support!

[Brant Schroeder]

Glad to hear you were able to get it up and running again.