Trying to upgrade from 7.3 to 7.11 SQL connection error

[E-TechOps]

Hello,

I am using sql server 2014 and CentOS7. This is being done in test. I first replicated my production settings and data. The whole setup works fine.

I am trying to upgrade to the new 7.11 version and when I upgrade directly it throws a sql error for which it needed a JDBC update on the xml file which was fixed. Thereafter when I try to open the jira page it throws a sql error.

I installed 7.11 alongside the existing version using different ports and folder locations etc. Now when I open the page to setup jira, in the sql database setup page I always get login failed for the user. When I check the connections from the server I don't see connections originating from this server to the sql server ('ss -plant' on centos box). The first instance is working fine. I tried shutting off the first instance and it still didn't connect and keeps giving this error:

Error connecting to database

Login failed for user 'JiraUser'. ClientConnectionId:df05a9c1-12ca-488e-a93e-4c2f0f33fba9

I checked the account on the sql server and it connects fine to the Jira databases. 

Regards,

Shiham

[Andy Heinzer · Accepted solution]

I'm not sure I fully understand, but if you already have a single Jira instance running, you don't want to have a second instance connecting to the exact same database at the same time.  It will cause corruption.

Instead of using the web setup wizard to connect to the database, there are other methods you can use to configure this.   Check out Connecting Jira applications to SQL Server 2014.   You could set this configuration directly in the dbconfig.xml file and use the sample dbconfig.xml as a reference, or you could even use the Jira Config Tool to accomplish the same.

I recommend that config tool, because if you have already installed Java separately and set the JAVA_HOME variable, that tool can be used.  It provides a separate simple GUI that you can use to test your database credentials before Jira starts.

[E-TechOps]

Hi Andrew,

Thanks for the reply. I was able to get the upgrade option to work. In my original upgrade tries I was running the tool to reconfigure the dbconfig file and thought it ported everything over but didn't. I manually set the options in there and was able to upgrade it directly over the existing install without the use of a second instance.

Thanks again for helping me out. You suggestions to check the dbconfig file helped a lot.

Regards,

Shiham

[Andy Heinzer]

Glad to help out.  Thanks for letting us know this was useful.