Installing Jira Service Desk created an error when making a new project

Albert Jumaquio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 11, 2018

This was an issue before I hope you can see it in my history. I did what was asked but I did not see any improvement when I finally upgraded. Is there some way you can do this for me?

 

Technical details

Log's referral number: 85141a6c-891c-4f24-be44-3364b1509431

Cause

Referer URL: http://jira.mod2.com:9001/secure/project/ViewProjects.jspa

java.lang.NullPointerException

2 answers

1 accepted

2 votes
Answer accepted
Keri
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 26, 2018

From the information given in the ticket, it appeared that Service Desk had been installed in the past, but without the correct upgrade path:


2017-04-11 08:10:14,211 JIRA-Bootstrap ERROR [bootstrap.lifecycle.server.ServerPluginLifeCycle] '2.5.8' version of Service Desk cannot be upgraded to '3.4.0-REL-0010'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
com.atlassian.servicedesk.bootstrap.lifecycle.server.UnsatisfiedVersionRequirementException: '2.5.8' version of Service Desk cannot be upgraded to '3.4.0-REL-0010'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
at com.atlassian.servicedesk.bootstrap.lifecycle.server.UpgradeRequirementsChecker.checkVersionRequirementForUpgrade(UpgradeRequirementsChecker.java:25)

The workaround as detailed in the KB article involves temporarily installing another server to perform the upgrade tasks, then importing the data back to the existing server to resolve this issue. 

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 12, 2018

Albert,

I didn't find anything related to your issue in the past on Community. This looks to be your first post. However, I did see that you raised the same issue in the Jira Software support queue.

You've provided more details there and we can obtain full logs from you there so it's better if we keep the investigation there.

Once the issue is resolved please feel free to let us know here what the resolution was.

Thank you for your understanding!
Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events