This question is in reference to Atlassian Documentation: When connecting to a named instance JIRA throws Connection refused

Ask your question here...

3 answers

0 votes

Actually, yes it does. 

So the question becomes "what are you doing differently?"

I try to explain. I have SQL Server 2012 installed as a default instance and SQL Server 2014 installed as a named instance. I have the latest JIRA + Service Desk version running on a Tomcat. If I connect JIRA to SQL Server 2012 then works well. If I try to connect it with the 2014 one, doing exactly what this page says then it gives a connection refused error. Even I have cared of configuring SQL Server 2014 to run on an static TCP port instead of on a dynamic as it was by default. For that purpose I used the configuration tool that came out of the box with my SQL Server 2014.

What am I doing differently?

That's where I'm stuck - I've got a SQL Server running as a named instance based on essentially pasting in the dbconfig given on that page.  So I don't know.

It didn't work for me because SQL Server 2014 TCP/IP connection was disabled on the SQL Server Configuration Manager...

Ah, so the SQL server was misconfigured.  Well spotted!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 6 hours ago in Jira Ops

Jira Ops Early Access Program Update #5: Three new ways to get a live Jira Ops demo!

Welcome to your weekly Jira Ops Early Access program update, where we’re sharing news and updates on Jira Ops progress as we work toward our 1.0 release. If you ever want to drop us feedback or ideas...

18 views 0 1
Read article

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