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

New Driver for database: Upgrade won't connect

Hi,  Upgraded Windows server based Jira version 7.3.4 to 7.60  in order to be on minimum version that allows using the migration assistant to cloud. 

Database is MSSQL 2014 sitting on same server as the Jira application.  

It shipped  a new database version and insisted I ran the config .exe and press Save in order to make the necessary changes which it did.   

However, I cannot connect as Jira startup argues the database is not online or reachable (see attached) and I simply don't know why.  I have tried rejigging the dbconfig to specify instance etc as per original line but has made no difference.   As I am on version with expired support I cannot get upgrade help frrom Atlassian.

Original Line in dbconfig:   (Refer Fig 1 below)


dbconfig line after running config and pressing SAVE:  (Refer Fig 2 below)



The database is online and working, I have logged into it using MSSQL Mngnt Studio and performed queries etc.  

Many thanks in advance.


Fig1. Jira db Error before config change.png


Fig 2

Jira db Error after config change.PNG



1 answer

I stopped / started service before / after change but to no avail.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events