Upgrading JIRA 7.8 to 7.13.0 Jira won't start "Jira Access problem"

[Jason Ferris]

Ran Jira 7.13.0 Core installation for Windows for my upgrade. Everything went fine for upgrade. When I launched Jira for the 1st time I received a window saying

Jira encountered the following problems during startup. You need to fix any errors before you start Jira again. 

Database: Update the JDBC URL - We've shipped a new driver for your database. You'll need to run the JIRA config tool (bin/config.bat or config.sh) and click Save. It will make the necessary changes for you.  | I tried this but it just says: 

No JRE_HOME or JAVA_HOME environment variable is set - attempting to just run 'j
ava' command
*******************************************************************************
******* Wrong JVM version! JIRA requires at least 1.8 to run. *******
*******************************************************************************

I do not have JRE installed on this server. Is this something I need to install now or from what I read it was supposed to install with my install? I am looking at this page

https://confluence.atlassian.com/jirakb/update-the-microsoft-sql-server-jdbc-url-in-jira-server-934718842.html

Or do I need to change the URL and Driver-class lines to match format of this? I am running Microsoft SQL DB 2012. 

This is in my test env so i'm thankful i'm testing this out!  Can someone please help me? I'm stuck and not sure what else to do other than restart my upgrade. 

Thank you!

[Moses Thomas · Accepted solution]

@Jason Ferris 

From the logs  it states that there is a problem with with Database connection,  there could be something  wrong with  the user and password that connects Jira to  database or dbconfig.xml is corrupted ,  i suggest you make a copy of the file somewhere else, and then remove this file in the JIRA home folder.

Default is C:\Program Files\Atlassian\Application Data\JIRA (on Windows)

 Try to  restart  JIRA again,  enter the right  user and password to connect to Db,  the  dbconfig.xml  should be regenerated again.

NOTE: the user and password should be in this file if you don't remember

And the user running Jira  should have permission to this file (read, and execute )

Best regards,

Moses

[Kian Stack Mumo Systems]

@Moses ThomasOne thing to keep in mind is that Jira won't let you establish an initial connection to a database if there is already content in there. If you remove the dbconfig file and perform a restart, Jira will think it is a fresh installation. Then it won't let you connect back to that database.

[Moses Thomas]

@Kian Stack Mumo Systems Yes you right! but he cannot connect to db, I would establish a connection first  to a fresh db, then export old db to fresh db but he would need to know how to do this.

[Jason Ferris]

@Moses Thomas @Kian Stack Mumo Systems  If I use the username and password in my dbconfig file and open SSMS I can connect to the DB just fine. The login works without issue. Is there another way I should test to make sure it works or should I try copying my dbconfig.xml file out and letting JIRA recreate one? Maybe it's corrupted and not the login?

[Moses Thomas]

@Jason Ferris   Ok this is good so we cross this case out  user/password, then  Jira  should be able to  connect to data base with this user.

The worst case is that the dbconfig.xml file is corrupted now  i doubt. But  even  so  then you would want to consider create new DB and then  connect to allow jira  start then export old DB to new DB(Worse case)

But if the test connection works,  then Jira  should start with no problems.

Kind regards,

Mo

[Jason Ferris]

@Moses Thomas @Kian Stack Mumo Systems  Here is what my dbconfig.xml file looks like. 

<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mssql</database-type>
<schema-name>jiraschema</schema-name>
<jdbc-datasource>
<url>jdbc:sqlserver://servername:1433;databaseName=/JIRADB</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<username>jiraloginid</username>
<password>xxxxxxxx</password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>

<validation-query>select 1</validation-query>
<pool-test-while-idle>true</pool-test-while-idle>
<pool-test-on-borrow>false</pool-test-on-borrow>
</jdbc-datasource>
</jira-database-config>

[Moses Thomas]

@Jason Ferris  This looks absolutely fine,   which user are you using to  start jira ?  does user have permission to  dbconfig.xml ?

[Jason Ferris]

@Moses Thomas The Atlassian Jira Service on my server is using the local system account to run that service. and our SQL Server is using a domain service account for SQL service. This server is an exact copy of the one we have in production but isolated in a test environment for upgrade testing.  The user that is in the dbconfig file is a local account in SQL so it's not a domain account. 

[Moses Thomas]

@Jason Ferris  To be honest every thing should work fine, try to start jira again

[Jason Ferris]

@Moses Thomas  yeah i'm still getting the http://jira/secure/errors.jsp   and Page heading of Jira access problem. I looked at log again after stopping and starting Jira and same things in there. 

2020-03-09 10:17:54,651 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-03-09 10:17:54,652 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
This could be because:
- Your database isn't running
- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

There are several other solutions you can try, review our documentation and see what works for you.

2020-03-09 10:17:54,657 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2020-03-09 10:17:54,657 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2020-03-09 10:17:54,833 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 62 MiB. Committed: 566 MiB. Max: 1002 MiB
Non-heap memory : Used: 43 MiB. Committed: 65 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 105 MiB. Committed: 631 MiB. Max: 2538 MiB
---------------------------------------------------------------------------------

My Jira security log shows this I don't know if this helps?

2020-03-09 09:03:21,155 http-nio-80-exec-2 anonymous 543x2x1 - <ip address>/secure/errors.jsp HttpSession created [zgx4yg]
2020-03-09 10:08:05,208 http-nio-80-exec-22 anonymous 608x7x1 - <ip address> /secure/errors.jsp HttpSession created [1uoom60]
2020-03-09 10:21:05,737 http-nio-80-exec-4 anonymous 621x2x1 - <ip address> /secure/errors.jsp HttpSession created [82dsrs]

[Moses Thomas]

@Jason Ferris  please show more logs,   catalina.out, atlasian-jira.log

C:\Program Files\Atlassian\JIRA\logs\catalina<Date>.log

C:\Program Files\Atlassian\Application Data\JIRA\log\atlassian-jira.log

May be fire wall is blocking connection , I need these logs to see whether i  could get something more 

[Jason Ferris]

@Moses Thomas 

atlassian-jira.log

****************
JIRA starting...
****************

2020-03-09 10:55:29,081 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 7.13.0#713000-sha1:fbf406879436de2f3fb1cfa09c7fa556fb79615a
Build Date : Wed Nov 28 00:00:00 CST 2018
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/8.5.32 - Servlet API 3.1
Java Version : 1.8.0_181 - Oracle Corporation
Current Working Directory : C:\Program Files\Atlassian\JIRA
Maximum Allowable Memory : 910MB
Total Memory : 488MB
Free Memory : 442MB
Used Memory : 46MB
Memory Pool: Code Cache : Code Cache: init = 33554432(32768K) used = 11628864(11356K) committed = 33554432(32768K) max = 536870912(524288K)
Memory Pool: Metaspace : Metaspace: init = 0(0K) used = 22130448(21611K) committed = 22986752(22448K) max = -1(-1K)
Memory Pool: Compressed Class Space : Compressed Class Space: init = 0(0K) used = 2597848(2536K) committed = 2801664(2736K) max = 1073741824(1048576K)
Memory Pool: PS Eden Space : PS Eden Space: init = 134742016(131584K) used = 31137728(30407K) committed = 130547712(127488K) max = 309854208(302592K)
Memory Pool: PS Survivor Space : PS Survivor Space: init = 22020096(21504K) used = 0(0K) committed = 23592960(23040K) max = 23592960(23040K)
Memory Pool: PS Old Gen : PS Old Gen: init = 358088704(349696K) used = 21069368(20575K) committed = 358088704(349696K) max = 716177408(699392K)
JVM Input Arguments : -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Dcatalina.home=C:\Program Files\Atlassian\JIRA -Dcatalina.base=C:\Program Files\Atlassian\JIRA -Dignore.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Program Files\Atlassian\JIRA\conf\logging.properties exit abort -Xms512m -Xmx1024m
Java Compatibility Information : JIRA version = 7.13.0, Java Version = 1.8.0_181

___ Java System Properties ________________

atlassian.standalone : JIRA
awt.toolkit : sun.awt.windows.WToolkit
catalina.base : C:\Program Files\Atlassian\JIRA
catalina.home : C:\Program Files\Atlassian\JIRA
catalina.useNaming : true
common.loader : "${catalina.base}/lib",
"${catalina.base}/lib/*.jar",
"${catalina.home}/lib",
"${catalina.home}/lib/*.jar"
file.encoding : Cp1252
file.encoding.pkg : sun.io
ignore.endorsed.dirs : C:\Program Files\Atlassian\JIRA\endorsed
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.headless : true
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 52.0
java.home : C:\PROGRA~1\ATLASS~1\JIRA\jre
java.io.tmpdir : C:\Program Files\Atlassian\JIRA\temp
java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory
java.naming.factory.url.pkgs : org.apache.naming
java.runtime.name : Java(TM) SE Runtime Environment
java.runtime.version : 1.8.0_181-b13
java.specification.name : Java Platform API Specification
java.specification.vendor : Oracle Corporation
java.specification.version : 1.8
java.util.concurrent.ForkJoinPool.common.threadFactory : org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory
java.util.logging.config.file : C:\Program Files\Atlassian\JIRA\conf\logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager
java.vendor : Oracle Corporation
java.vendor.url : http://java.oracle.com/
java.vendor.url.bug : http://bugreport.sun.com/bugreport/
java.version : 1.8.0_181
java.vm.info : mixed mode
java.vm.name : Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Oracle Corporation
java.vm.specification.version : 1.8
java.vm.vendor : Oracle Corporation
java.vm.version : 25.181-b13
mail.mime.decodeparameters : true
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
org.dom4j.factory : com.atlassian.core.xml.InterningDocumentFactory
os.arch : amd64
os.name : Windows Server 2012 R2
os.version : 6.3
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.tomcat.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.jasper.,
org.apache.naming.,
org.apache.tomcat.
server.loader :
shared.loader :
sun.arch.data.model : 64
sun.boot.library.path : C:\PROGRA~1\ATLASS~1\JIRA\jre\bin
sun.cpu.endian : little
sun.cpu.isalist : amd64
sun.desktop : windows
sun.io.unicode.encoding : UnicodeLittle
sun.jnu.encoding : Cp1252
sun.management.compiler : HotSpot 64-Bit Tiered Compilers
sun.os.patch.level :
tomcat.util.buf.StringCache.byte.enabled : true
tomcat.util.scan.StandardJarScanFilter.jarsToScan : log4j-web*.jar,
log4j-taglib*.jar,
log4javascript*.jar,
slf4j-taglib*.jar
tomcat.util.scan.StandardJarScanFilter.jarsToSkip : bootstrap.jar,
commons-daemon.jar,
tomcat-juli.jar,
annotations-api.jar,
el-api.jar,
jsp-api.jar,
servlet-api.jar,
websocket-api.jar,
jaspic-api.jar,
catalina.jar,
catalina-ant.jar,
catalina-ha.jar,
catalina-storeconfig.jar,
catalina-tribes.jar,
jasper.jar,
jasper-el.jar,
ecj-*.jar,
tomcat-api.jar,
tomcat-util.jar,
tomcat-util-scan.jar,
tomcat-coyote.jar,
tomcat-dbcp.jar,
tomcat-jni.jar,
tomcat-websocket.jar,
tomcat-i18n-en.jar,
tomcat-i18n-es.jar,
tomcat-i18n-fr.jar,
tomcat-i18n-ja.jar,
tomcat-juli-adapters.jar,
catalina-jmx-remote.jar,
catalina-ws.jar,
tomcat-jdbc.jar,
tools.jar,
commons-beanutils*.jar,
commons-codec*.jar,
commons-collections*.jar,
commons-dbcp*.jar,
commons-digester*.jar,
commons-fileupload*.jar,
commons-httpclient*.jar,
commons-io*.jar,
commons-lang*.jar,
commons-logging*.jar,
commons-math*.jar,
commons-pool*.jar,
jstl.jar,
taglibs-standard-spec-*.jar,
geronimo-spec-jaxrpc*.jar,
wsdl4j*.jar,
ant.jar,
ant-junit*.jar,
aspectj*.jar,
jmx.jar,
h2*.jar,
hibernate*.jar,
httpclient*.jar,
jmx-tools.jar,
jta*.jar,
log4j*.jar,
mail*.jar,
slf4j*.jar,
xercesImpl.jar,
xmlParserAPIs.jar,
xml-apis.jar,
junit.jar,
junit-*.jar,
hamcrest-*.jar,
easymock-*.jar,
cglib-*.jar,
objenesis-*.jar,
ant-launcher.jar,
cobertura-*.jar,
asm-*.jar,
dom4j-*.jar,
icu4j-*.jar,
jaxen-*.jar,
jdom-*.jar,
jetty-*.jar,
oro-*.jar,
servlet-api-*.jar,
tagsoup-*.jar,
xmlParserAPIs-*.jar,
xom-*.jar
user.country : US
user.dir : C:\Program Files\Atlassian\JIRA
user.home : C:\Windows\system32\config\systemprofile
user.language : en
user.name : servername$
user.script :
user.timezone : America/Chicago
user.variant :

2020-03-09 10:55:29,670 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Program Files\Atlassian\Application Data\JIRA\dbconfig.xml
2020-03-09 10:55:30,408 JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "/JIRADB" requested by the login. The login failed. ClientConnectionId:ddde8ecc-cc4e-4553-9ff4-7d1038a4e63c
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:256)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:108)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4290)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3157)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:82)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3121)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2026)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:569)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.getTestDatabaseConnection(DefaultAtlassianBootstrapManager.java:347)
at com.atlassian.jira.config.database.JdbcDatasource.getConnection(JdbcDatasource.java:211)
at com.atlassian.jira.config.database.DatabaseConfig.testConnection(DatabaseConfig.java:88)
at com.atlassian.jira.health.checks.DbConfigurationAndConnectionCheck.doPerform(DbConfigurationAndConnectionCheck.java:60)
at com.atlassian.jira.health.HealthCheckTemplate.perform(HealthCheckTemplate.java:23)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.runCheck(DefaultHealthCheckExecutor.java:74)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.lambda$applyAndCollectExceptions$1(DefaultHealthCheckExecutor.java:53)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.applyAndCollectExceptions(DefaultHealthCheckExecutor.java:53)
at com.atlassian.jira.health.DefaultHealthCheckExecutor.performHealthChecks(DefaultHealthCheckExecutor.java:42)
at com.atlassian.jira.health.HealthChecks.executeChecksAndRecordResults(HealthChecks.java:164)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:154)
at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66)
at com.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:48)
at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:115)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:101)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:100)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at java.lang.Thread.run(Thread.java:748)
2020-03-09 10:55:30,453 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-03-09 10:55:30,453 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
This could be because:
- Your database isn't running
- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

There are several other solutions you can try, review our documentation and see what works for you.

2020-03-09 10:55:30,458 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2020-03-09 10:55:30,459 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2020-03-09 10:55:30,636 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 129 MiB. Committed: 470 MiB. Max: 1001 MiB
Non-heap memory : Used: 43 MiB. Committed: 65 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 171 MiB. Committed: 535 MiB. Max: 2537 MiB
---------------------------------------------------------------------------------

[Jason Ferris]

@Moses Thomas 

Catalina log

09-Mar-2020 10:55:01.331 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.32
09-Mar-2020 10:55:01.336 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 20 2018 19:50:35 UTC
09-Mar-2020 10:55:01.337 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.32.0
09-Mar-2020 10:55:01.337 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2012 R2
09-Mar-2020 10:55:01.337 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 6.3
09-Mar-2020 10:55:01.337 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
09-Mar-2020 10:55:01.338 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\PROGRA~1\ATLASS~1\JIRA\jre
09-Mar-2020 10:55:01.338 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
09-Mar-2020 10:55:01.338 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
09-Mar-2020 10:55:01.338 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\JIRA
09-Mar-2020 10:55:01.338 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\JIRA
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
09-Mar-2020 10:55:01.339 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
09-Mar-2020 10:55:01.340 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Atlassian\JIRA
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Atlassian\JIRA
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp
09-Mar-2020 10:55:01.341 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Atlassian\JIRA\conf\logging.properties
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms512m
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx1024m
09-Mar-2020 10:55:01.342 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Atlassian\JIRA\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Idera\SQLsafe\;C:\Program Files\Puppet Labs\Puppet\bin;;.]
09-Mar-2020 10:55:01.685 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]
09-Mar-2020 10:55:01.697 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1071 ms
09-Mar-2020 10:55:01.720 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
09-Mar-2020 10:55:01.721 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.32
09-Mar-2020 10:55:29.331 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-80"]
09-Mar-2020 10:55:29.373 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
09-Mar-2020 10:55:29.389 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 27691 ms

[Jason Ferris]

@Moses Thomas  The DB is running on the same server it's an all in one. I don't believe this would be a firewall issue in this case. 

[Jason Ferris]

@Moses Thomas  Should I attempt the steps in creating a new DB and then exporting original DB data into the new DB? Is that what we are leaning on at this point?

[Moses Thomas]

@Jason Ferris   It is clear now, it  is having problem with this DB configuration.

dbconfig.xml

The Url in the dbconfig.xml  should be like this

<url>jdbc:sqlserver://dbserver:1433;databaseName=jiradb</url>

In your Db config file it is  like this

<url>jdbc:sqlserver://servername:1433;databaseName=/JIRADB</url>

Servername is the IP adress of the DB server  e.g 172.3.0.x.x

and i will remove the  /    save file and then  restart again

Please give feed back, Good luck.

Best regards,

Mo

[Jason Ferris]

@Moses Thomas  I excluded what was in my URL line for the "servername" as what it really shows is my actual servername so //server1:1433;databaseName=/JIRADB. I will take out the / and change to lowercase jiradb and see if that works. The DB name in SQL is in CAPS so I figured it had to match?

[Moses Thomas]

  @Jason Ferris  the server name (can be hostname  or Ip adress of the host and the DB name is the name exactly as in the database),  then just remove  / and try :)

it should work.

[Jason Ferris]

@Moses Thomas  And you are awesome! It works!!!!! Thank you thank you!!!! Whats strange is it was in caps on the previous version so guessing that changed when I upgraded it.  Good to know. I appreciate your help very much!

[Moses Thomas]

@Jason Ferris 

:D  :D Great, I am  happy that we are able  to  fix this,  so  to be clear  the syntax in the dbconfig.xml  is different  in 7.13.X  and when you  ran  the   config.bat ,  the Microsoft SQL driver was updated and  this was important to  be compatible  with  the new Jira version 7.13.x

Have a nice evening!

[Kian Stack Mumo Systems]

Jason,

You don't need to install java in order to run Jira as it comes bundled with the installer. However, it appears that the bat file is expecting a certain java version but your machine doesn't have those variables set. One option would be to set them following the instructions found here (you should be able to find java within the Jira files).

Otherwise, you  should be able to just update your file manually to the format expected and perform a restart.

[Jason Ferris]

I found JRE/JAVA in C:\Program Files\Atlassian\JIRA\jre\bin. Is this the correct directory? I added the environment variable pointing to this and the Variable name is JRE_HOME.  Still receiving same error when launching but now getting this. I did reboot as well. 

JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "/XXXDB" requested by the login. The login failed. ClientConnectionId:14a5bc9f-9ec7-466d-8089-f59db0852aa9

This could be because:
- Your database isn't running
- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

After the upgrade I did change my dbconfig.xml to the updated information for URL and driver-class

<url>jdbc:sqlserver://server:1433;databaseName=/XXXDB</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>

should I change this back to what it was before? which was 

<url>jdbc:jtds:sqlserver://server:1433/XXXDB</url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

[Kian Stack Mumo Systems]

Both of the two that you have set up look correct.

Sometimes you have too pass it the scheme. According to the documentation, try this:

<url>jdbc:sqlserver://sqlserver_hostname\instance_name;databaseName=jiradb</url>

[Jason Ferris]

@Kian Stack Mumo Systems Hello. I am just getting back to this as I put this ticket in Friday and am back at work today.  The adjustment you are suggesting to that URL line, what should be in the "instance_name" part? I am not using a clustered environment and I don't think this is a "named instance" DB.  I think the command below tells me it's a default instance?

when opening command prompt and typing sqlcmd -S <myjiraserver> it comes back with a prompt  of

1>