How to connect Jira with SQL Server 2008 R2?

JIRA configurator tell that "its okay i see connection", but when I start JIRA Service it tell that there is some error:

JIRA — Internal Server Error

Error reference: aa5fe2b7-e4a0-4c4c-8b14-7ac0bc3767d7

Unable to render full error details at this time. Please consult the error logs for more information.

Okay here is log files for today https://yadi.sk/d/eQdogeBTrRp52 (at first it was H2 data base, then I start connect SQL Server 2008 R2)

3 answers

0 vote

What does the JIRA application log file say the problem is?  Atlassian-jira.log in the <JIRA home>/log directory

What version of JIRA are you using?  You may be using a JIRA version that no longer supports SQL Server 2008 R2.  Was this working at one point, or is this a new setup?   

Here is piece of log file Atlassian-jira.log when JIRA tryung to start https://yadi.sk/d/jixrleh7rSbhB

I think problem in this piece of log (but i dont understand what is that about):

You are using an unsupported mssql collation: Cyrillic_General_CI_AS. This may cause some functionality to not work.
Please use SQL_Latin1_General_CI_AI or SQL_Latin1_General_CP437_CI_AI as the collation instead.

Um, that chunk of log doesn't mention the collation at all.

But, it is a valid warning.  Collation is a setting about how a database compares characters in data.  You don't need to worry too much about the precise reasons why this might be a problem, but you do need to switch to a database with supported settings.

But how looks like that supported settings? Database in MS SQL was created automatically, and JIRA can see connection if I click "Test connection", but when I Start Jira, it tell that something wrong. I was try install jTDS driver but dont find easy documentation for someone who does not know Java.I think that jTDS can resolve this problem. I look a lot web site but cant find the answer ((

No, it's not that, although I do understand why you thought that might be it, and your idea is good.

The database for MS-SQL was not created automatically.  Your database administrator had to set up an empty one, with a user who has full access to it.  JIRA then used that user to create all the base data it needed.  But, collation is a setting done at the database creation time, not initial population.  The database has been created with a collation that does not work for JIRA - you'll need to convert it to a collation type that works, or start with a new empty one that has the correct collation set at the time your admin creates it.

Oh, thank you I think I start understand what to do next..

The database for MS-SQL was not created automatically - yes , When I make database in MS SQL I was following the instructions on the site documentation for JIRA. but probably i miss some important detail.. Dont remember anything about collation. can you please tell what collation  I will need to set when I will try make new database for jira? what collation is right for jira?

Thank you very much. I will try following this instruction.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted 7 hours ago in Jira

We want to know what Jira Service Desk apps you're using!

Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...

27 views 0 5
Join discussion

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