You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have received the following error(below) during 8.11.0 setup. The JIRA configurator tool did not successfully connect us to the MS SQL Server 2016. The schema has been created and domain service account setup for the authentication. The MS SQL DB has been setup for SSL where the dbconfig.xml file has been specified with connection string encrypt=true;trustServerCertificate=true.
From our DBA, the problem is due to how we configure the login. We followed the connection string settings for the dbconfig.xml. The firewall between the JIRA server to the db server has been cleared and verified with telnet.
MS SQL Server Error = attempt to login using sql authentication failed
JIRA Error = Database: JIRA couldn't connect to your database.
Whenever I have problem connecting to a database from an Atlassian application like Jira, I use DBeaver to figure out the connectivity problem.
DBeaver is written in Java and uses a similar connection string methodology as Jira/Confluence/etc. If it works there, it will work on Jira. DBeaver is a desktop GUI and is more interactive than Jira so it is easier to debug these problem. It also has a wizard to guide you through your first connection that then you can apply the result be to Jira:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.