I updated Jira Software today. From version 7.4.3 to 7.11.0.
The requirements were fulfilled: Windows Server 2008 SP1, 64bit system, 4 GB RAM and 2x 2.20 GHz CPUs. Java version 8.0 and later.
I stopped the JIRA process and then started the installation. Everything went smoothly.
But when I wanted to restart JIRA I just got the following error.
So I followed the instructions and suggestions and checked the database.
This has also been restarted, reset the password and is fully functional.
With other programs, I can connect to the database, so I rule out this problem before.
Then I checked the configuration.
I edited the config.xml via config.bat.
Both the user, password and the database URL correspond to the original information. For safety's sake, I even consulted the old settings. They are identical except for a different spelling.
This is the old spelling:
<url>jdbc:jtds:sqlserver://SERVERNAME:1433;instance=INSTANCE/jira</url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
And that's the new spelling:
<url>jdbc:sqlserver://;serverName=SERVERNAME;portNumber=1433</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
But I always get the following error when trying to connect:
It can't be a network error either, because I run JIRA as a local server.
The user has access rights and the port is free.
And it should be a JIRA database since it's the same one used in version 7.4.3.
Do I have to change anything in the SQL database, which was not explicitly stated in the instructions?
Has anyone had a similar problem and how to solve this?
What version of MS SQL is your database? I ask because this newer version of Jira does not support the 2008 version of MS SQL any more. Please see the Supported platforms documentation. For MS SQL databases, this version of Jira has to use a 2012, 2014, or 2016 version.
In Jira 7.5 and higher versions, the database driver for MS SQL type databases has changed from the jtds dirver to use the microsoft database driver instead. While you're driver-class tag looks ok, I think your URL tag specified for the database looks incorrect to me.
Please see the example in the Connecting Jira to SQL server 2012. The sample dbconfig.xml file there will have a syntax like this:
<url>jdbc:sqlserver://dbserver:1433;databaseName=jiradb</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Now we have another problem. We set JIRA back to the working version. But now the linked CONFLUENCE does not start anymore, although nothing has changed.
JIRA works as before. Is there a connection lost between JIRA and CONFLUENCE by the process?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Confluence isn't exactly my specialty. It might be better to create a new question in the Confluence collection instead. For a start, I would take a look at the startup logs when trying to start Confluence to see if we can better understand what might be causing this startup problem. But I can't see any clear relation to a Jira upgrade effecting the ability of Confluence to start up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can not explain it now, but this morning everything went as usual.
Maybe it was some processes that did not stop completely. So now everything is working again.
We are updating our database and then try again with the JIRA update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.