Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

problem upgrading from 8.19.1 to 8.22.4

I am trying to upgrade the Jira 8.19.1 to 8.22.4

I have followed your upgrade guideline, but while running the exe I got an error message below

run those steps

  1. administration > Application > Plan your upgrade no1 All pre-upgrade checks have passed
  2. administration > System > Instance Health all green ticks
  3. administration > Manage apps > Jira update check > all green
  4. administration > system > import and export > backup system 
  5. copy the following file to c:\temp
    1. dbconfig.xml
    2. bin\setenv32.bat
    3. bin\
    4. conf\server.xml
    5. bin\setenv.bat
    6. bin\
    7. conf\certfiicate files
  6. run cmd shutdown.bat on c:\program file\atlassian\jira\bin
  7. run the 8.22.4 Jira software after the backup is done the error message pop up. I saw another CONFSERVER-59387 just to click ignore and continue to set up and should not be any error. 
  8. after installation is complete, I click start Jira software 8.22.4 now, and next start access to the website but not show up.
  9. the Jira Service is running

error message.JPG

1 answer

0 votes
Daniel Ebers Community Leader Aug 17, 2022

Hi @Michael

I found this error in a bug which seems being processed ( but that should not prevent an upgrade.

The "real" reason why it fails should be visible from logs. In case you are still stuck probably consulting an Atlassian Partner ( could make sense, they are experienced in doing (even complex) upgrades.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events