Could not determine database type

Can you help me connect the DB? It seems the new install wizard blocks me from moving to MS SQL Server.

I have Jira 6.1 on WinSvr 2008 and am switching DB from HSSQL to a named instance of MS SQL 2008 with NTLM Authentication.

The behavior is

1) that if there's not username & pswd in dbconfig.xml, the initial setup wizard runs in the browser.

2) If the username is added, then the error occurs: HTTP Status 500 - org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)

3) The new MS SQL DB instance was setup, and the connection URL was tested with SQuirreL and the ntlmauth.dll file added to the default path.

jdbc:jtds:sqlserver://ab-sqlp01:1433/Jiradb;instance=APPS

It successfully opens the DB if submitted without the username and password when run from the same administrative service account that Jira runs under.

JDBC Driver CLASSNAME net.sourceforge.jtds.jdbc.Driver
JDBC Driver CLASSPATH C:\Program Files\squirrel-sql-3.5.0\jtds-1.2.4.jar
getURL jdbc:jtds:sqlserver://ab-sqlp01:1433/Jiradb;instance=APPS
isReadOnly false
getUserName domain\service name
supportsSchemasInDataManipulation true
getDriverName jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
getCatalogSeparator .
storesMixedCaseIdentifiers true
storesUpperCaseIdentifiers false
supportsCatalogsInTableDefinitions true
supportsSchemasInTableDefinitions true
getDatabaseProductName Microsoft SQL Server
getDatabaseProductVersion 10.50.2550

~~~~~~~~~~~~~~~

The dbconfig.xml is:

<?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:jtds:sqlserver://ab-sqlp01:1433/Jiradb;instance=APPS</url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<username> <domain>\<username> </username>
<password></password>
<pool-min-size>15</pool-min-size>
<pool-max-size>15</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<pool-max-idle>15</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
</jdbc-datasource>
</jira-database-config>

~~~~~~~~~~~~~~~

Thejiradb.properites file is still for HSSQL:

#HSQL Database Engine
#Thu Dec 19 13:49:59 PST 2013
hsqldb.script_format=0
runtime.gc_interval=0
sql.enforce_strict_size=false

...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error from browser with only username in dbconfig.xml file:

HTTP Status 500 - org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user 'ABNOLOGY\SVC_Jira'.)


type Exception report

message org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)

description The server encountered an internal error (org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)) that prevented it from fulfilling this request.

exception

com.atlassian.util.concurrent.LazyReference$InitializationException: org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)
	com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
	com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
	com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
	com.atlassian.jira.config.properties.PropertiesManager.getPropertySet(PropertiesManager.java:27)
	com.atlassian.jira.config.properties.ApplicationPropertiesStore.getStringFromDb(ApplicationPropertiesStore.java:268)
	com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getString(ApplicationPropertiesImpl.java:50)
	com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getEncoding(ApplicationPropertiesImpl.java:113)
	com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getContentType(ApplicationPropertiesImpl.java:135)
	com.atlassian.jira.web.filters.JiraEncodingFilter.getContentType(JiraEncodingFilter.java:59)
	com.atlassian.core.filters.encoding.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:39)
	com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
	com.atlassian.jira.web.filters.PathMatchingEncodingFilter.doFilter(PathMatchingEncodingFilter.java:49)
	com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
	com.atlassian.jira.startup.JiraStartupChecklistFilter.doFilter(JiraStartupChecklistFilter.java:78)
	com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:87)
	com.atlassian.jira.web.filters.JiraFirstFilter.doFilter(JiraFirstFilter.java:57)

root cause

org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)
	org.ofbiz.core.entity.config.DatasourceInfo.getDatabaseTypeFromJDBCConnection(DatasourceInfo.java:409)
	org.ofbiz.core.entity.GenericDAO.selectListIteratorByCondition(GenericDAO.java:962)
	org.ofbiz.core.entity.GenericDAO.selectByAnd(GenericDAO.java:630)
	org.ofbiz.core.entity.GenericHelperDAO.findByAnd(GenericHelperDAO.java:131)
	org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:804)
	org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:789)
	org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:766)
	com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.getKeys(OFBizPropertySet.java:82)
	com.atlassian.jira.propertyset.PropertySetCache.bulkLoad(PropertySetCache.java:318)
	com.atlassian.jira.propertyset.JiraCachingPropertySet$12.run(JiraCachingPropertySet.java:785)
	com.atlassian.jira.propertyset.JiraCachingPropertySet.doLocked(JiraCachingPropertySet.java:846)
	com.atlassian.jira.propertyset.JiraCachingPropertySet.init(JiraCachingPropertySet.java:770)
	com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:58)
	com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:31)
	com.atlassian.jira.config.properties.PropertySetUtils.createDatabaseBackedPropertySet(PropertySetUtils.java:34)
	com.atlassian.jira.config.properties.DbBackedPropertiesManager$1.create(DbBackedPropertiesManager.java:26)
	com.atlassian.jira.config.properties.DbBackedPropertiesManager$1.create(DbBackedPropertiesManager.java:22)
	com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:140)
	com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321)
	com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
	com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
	com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
	com.atlassian.jira.config.properties.PropertiesManager.getPropertySet(PropertiesManager.java:27)
	com.atlassian.jira.config.properties.ApplicationPropertiesStore.getStringFromDb(ApplicationPropertiesStore.java:268)
	com.atlassian.jira.config.properties.ApplicationPropertiesStore.getString(ApplicationPropertiesStore.java:346)
	com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getDefaultBackedString(ApplicationPropertiesImpl.java:60)
	com.atlassian.jira.security.auth.trustedapps.UserNameTransformer$ApplicationPropertiesClassNameRetriever.get(UserNameTransformer.java:68)
	com.atlassian.jira.security.auth.trustedapps.UserNameTransformer$Factory.get(UserNameTransformer.java:99)
	com.atlassian.jira.security.auth.trustedapps.TrustedApplicationFilter$OSUserResolver.<init>(TrustedApplicationFilter.java:40)
	com.atlassian.jira.security.auth.trustedapps.TrustedApplicationFilter.<init>(TrustedApplicationFilter.java:25)
	sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	java.lang.reflect.Constructor.newInstance(Unknown Source)
	java.lang.Class.newInstance(Unknown Source)
	org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	java.util.concurrent.FutureTask.run(Unknown Source)
	java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	java.lang.Thread.run(Unknown Source)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error when restarted with password included in dbconfig.xml:

HTTP Status 500 - org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)


type Exception report

message org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)

description The server encountered an internal error (org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.)) that prevented it from fulfilling this request.

exception

com.atlassian.util.concurrent.LazyReference$InitializationException: org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.) com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149) com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112) com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87) com.atlassian.jira.config.properties.PropertiesManager.getPropertySet(PropertiesManager.java:27) com.atlassian.jira.config.properties.ApplicationPropertiesStore.getStringFromDb(ApplicationPropertiesStore.java:268) com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getString(ApplicationPropertiesImpl.java:50) com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getEncoding(ApplicationPropertiesImpl.java:113) com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getContentType(ApplicationPropertiesImpl.java:135) com.atlassian.jira.web.filters.JiraEncodingFilter.getContentType(JiraEncodingFilter.java:59) com.atlassian.core.filters.encoding.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:39) com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31) com.atlassian.jira.web.filters.PathMatchingEncodingFilter.doFilter(PathMatchingEncodingFilter.java:49) com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31) com.atlassian.jira.startup.JiraStartupChecklistFilter.doFilter(JiraStartupChecklistFilter.java:78) com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:87) com.atlassian.jira.web.filters.JiraFirstFilter.doFilter(JiraFirstFilter.java:57)

root cause

org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Login failed for user '<domain>\<username>'.) org.ofbiz.core.entity.config.DatasourceInfo.getDatabaseTypeFromJDBCConnection(DatasourceInfo.java:409) org.ofbiz.core.entity.GenericDAO.selectListIteratorByCondition(GenericDAO.java:962) org.ofbiz.core.entity.GenericDAO.selectByAnd(GenericDAO.java:630) org.ofbiz.core.entity.GenericHelperDAO.findByAnd(GenericHelperDAO.java:131) org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:804) org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:789) org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:766) com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.getKeys(OFBizPropertySet.java:82) com.atlassian.jira.propertyset.PropertySetCache.bulkLoad(PropertySetCache.java:318) com.atlassian.jira.propertyset.JiraCachingPropertySet$12.run(JiraCachingPropertySet.java:785) com.atlassian.jira.propertyset.JiraCachingPropertySet.doLocked(JiraCachingPropertySet.java:846) com.atlassian.jira.propertyset.JiraCachingPropertySet.init(JiraCachingPropertySet.java:770) com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:58) com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:31) com.atlassian.jira.config.properties.PropertySetUtils.createDatabaseBackedPropertySet(PropertySetUtils.java:34) com.atlassian.jira.config.properties.DbBackedPropertiesManager$1.create(DbBackedPropertiesManager.java:26) com.atlassian.jira.config.properties.DbBackedPropertiesManager$1.create(DbBackedPropertiesManager.java:22) com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:140) com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321) com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143) com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112) com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87) com.atlassian.jira.config.properties.PropertiesManager.getPropertySet(PropertiesManager.java:27) com.atlassian.jira.config.properties.ApplicationPropertiesStore.getStringFromDb(ApplicationPropertiesStore.java:268) com.atlassian.jira.config.properties.ApplicationPropertiesStore.getString(ApplicationPropertiesStore.java:346) com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getDefaultBackedString(ApplicationPropertiesImpl.java:60) com.atlassian.jira.security.auth.trustedapps.UserNameTransformer$ApplicationPropertiesClassNameRetriever.get(UserNameTransformer.java:68) com.atlassian.jira.security.auth.trustedapps.UserNameTransformer$Factory.get(UserNameTransformer.java:99) com.atlassian.jira.security.auth.trustedapps.TrustedApplicationFilter$OSUserResolver.<init>(TrustedApplicationFilter.java:40) com.atlassian.jira.security.auth.trustedapps.TrustedApplicationFilter.<init>(TrustedApplicationFilter.java:25) sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) java.lang.reflect.Constructor.newInstance(Unknown Source) java.lang.Class.newInstance(Unknown Source) org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) java.util.concurrent.FutureTask.run(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When run without username and pswd in dbconfig.xml file, no error occurs. Just forced into setup wizard which will not accept instance name in entry fields and therefore never passes the setup wizard:

http://localhost:8080/secure/SetupDatabase!default.jspa

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The same occurs if the username & pswd tags are removed from the dbconfig.xml too.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Here's the log from the last runs switching for username only, username & pswd, and no username nor password.

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

2013-12-27 01:50:38,137 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 6.1.2#6157-sha1:98c729218aad6de1537eb8e98889ee5562c90d96
Build Date : Thu Oct 24 00:00:00 PDT 2013
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/7.0.29 - Servlet API 3.0
Java Version : 1.7.0_25 - Oracle Corporation
Current Working Directory : C:\Program Files\Atlassian\JIRA\bin
Maximum Allowable Memory : 742MB
Total Memory : 247MB
Free Memory : 168MB
Used Memory : 79MB
Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 1819776(1777K) committed = 2555904(2496K) max = 50331648(49152K)
Memory Pool: Eden Space : Eden Space: init = 71630848(69952K) used = 61814912(60366K) committed = 71630848(69952K) max = 214827008(209792K)
Memory Pool: Survivor Space : Survivor Space: init = 8912896(8704K) used = 8912888(8703K) committed = 8912896(8704K) max = 26804224(26176K)
Memory Pool: Tenured Gen : Tenured Gen: init = 178978816(174784K) used = 12196384(11910K) committed = 178978816(174784K) max = 536870912(524288K)
Memory Pool: Perm Gen : Perm Gen: init = 21757952(21248K) used = 17871520(17452K) committed = 21757952(21248K) max = 402653184(393216K)
JVM Input Arguments : -Dcatalina.base=C:\Program Files\Atlassian\JIRA -Dcatalina.home=C:\Program Files\Atlassian\JIRA -Djava.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dmail.mime.decodeparameters=true -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -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 -XX:MaxPermSize=384m -Xms256m -Xmx768m
Java Compatibility Information : JIRA version = 6.1.2, Java Version = 1.7.0_25

___ Java System Properties ________________

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
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.headless : true -Datlassian.standalone=JIRA -Dmail.mime.decodeparameters=true
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 51.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.7.0_25-b17
java.specification.name : Java Platform API Specification
java.specification.vendor : Oracle Corporation
java.specification.version : 1.7
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/<br< a="">> java.vendor.url.bug : http://bugreport.sun.com/bugreport/<br< a="">> java.version : 1.7.0_25
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.7
java.vm.vendor ...


































































































































































































































































































































































































































































http://java.oracle.com/<br< a="">> java.vendor.url.bug : http://bugreport.sun.com/bugreport/<br< a="">> java.version : 1.7.0_25
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.7
java.vm.vendor ...

































































































































































































































































































































http://java.oracle.com/<br< a="">> java.vendor.url.bug : http://bugreport.sun.com/bugreport/<br< a="">> java.version : 1.7.0_25
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.7
java.vm.vendor ...








































































































































































































































































 

3 answers

1 accepted

Thank you for the update.

My database expert was able to find the user comment/solution you listed (https://confluence.atlassian.com/display/JIRA/JIRA+and+MS+SQL+Server+2008?focusedCommentId=264045977#comment-264045977). We did have to go through the process of creating a temporary login account in SQL Server in order to bypass the setup wizard and then update the configuration to use the NTLM authentication once we moved the login domain to the URL manually.

Though it's not your fault it works this way, this is an incredibly poor integration with one of Jira's 'production supported DBs'. Both on the technical level and on the documentation level. The NTLM authentication is a security industry best practice and should be addressed in the standard Jira installation documentation.

Do you know if there's a bug/feature request entered for this that I can 'vote' for, etc.

Thanks,

Mark

Yew Teck En Atlassian Team Jan 01, 2014
awesome. :) I think here's the improvement of the NTLM authentication: https://jira.atlassian.com/browse/JRA-2398
0 vote
Yew Teck En Atlassian Team Dec 26, 2013
Caused by: java.sql.SQLException: Login failed for user 'ABNOLOGY\SVC_Jira'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.&lt;init&gt;(ConnectionJDBC2.java:357)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

The user unable to login due to the following:

Caused by: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource
at com.sun.jmx.mbeanserver.Repository.addMBean(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Unknown Source)

Did your username password contained some special characters? If so you might hit into the bug addressed in this KB article: https://confluence.atlassian.com/display/JIRAKB/JIRA+Does+Not+Start+due+to+InstanceAlreadyExistsException

Try use a password without special character and see how it goes?

Thanks for your response, though the password only has letters and numbers mixed case.

I also checked the mutiple usertransaction defines and there's no conf/Catalina/localhost/jira.xml file to duplicate.

In server.xml, it contains:

-<Engine name="Catalina" defaultHost="localhost">-<Host name="localhost" unpackWARs="true" autoDeploy="true" appBase="webapps">-<Context useHttpOnly="true" reloadable="false" path="" docBase="${catalina.home}/atlassian-jira">
<!-- ==================================================================================== Note, you no longer configure your database driver or connection parameters here. These are configured through the UI during application setup. ==================================================================================== -->
<Resource name="UserTransaction" type="javax.transaction.UserTransaction" jotm.timeout="60" factory="org.objectweb.jotm.UserTransactionFactory" auth="Container"/><Manager pathname=""/></Context></Host>

Any other thoughts?

Yew Teck En Atlassian Team Dec 30, 2013

since you using NTLM authentication, try the suggestion to add the domain to the jdbc URL and use the username(without the domain) as suggested by the user comment over here: https://confluence.atlassian.com/display/JIRA/JIRA+and+MS+SQL+Server+2008?focusedCommentId=264045977#comment-264045977

I had the same error screen, but it turned out that postgresql was not starting.

 

Luckily postgres gave me the information I needed to know when I ran the "sudo service postgresql start" command in ubuntu.

In my case the failure was because of permissions on the postgresql install directory having been changed. Once I ran "chmod 700 the/address/of/postgres -R" and ran "sudo service postgresql start", "sudo service JIRA stop", and "sudo service JIRA stop" everything eventually came back online.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

70 views 0 5
Read article

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