Install JIRA 6.3.3 says me "column 'scheme' is not valid"

Deleted user August 12, 2014

I'm trying to install JIRA 6.3.3 with JIRA Agile 6.4 on a SQL Server 2012 Enterprise Edition.

After setup is finished, JIRA says the message "column 'scheme' is not valid".

The stack trace is:

Exception thrown during upgrade: Il nome di colonna 'scheme' non è valido.
java.sql.SQLException: Il nome di colonna 'scheme' non è valido.
	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.getMoreResults(TdsCore.java:632)
	at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1166)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1119)
	at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
	at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6325.doUpgrade(UpgradeTask_Build6325.java:66)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSuccess(UpgradeManagerImpl.java:693)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:542)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:471)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:413)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:348)
	at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:106)
	at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:54)
	at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:42)
	at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:133)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:324)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:214)
	at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:115)
	at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:31)
	at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:78)
	at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:34)
	at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:73)
	at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:71)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
 
Please, help me.

4 answers

1 accepted

0 votes
Answer accepted
ohernandez
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 18, 2014

Hi Samuele,

In order for JIRA to communicate correctly with SQL Server 2012, it must be configured as per the docs at - https://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+SQL+Server+2012

Especially this bit:

Collation type must be case-insensitive, for example, 'SQL_Latin1_General_CP437_CI_AI' is case-insensitive collation type. If your SQL Server installation's collation type settings have not been changed from their defaults, check the collation type settings.

Hope this helps.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

0 votes
Deleted user August 13, 2014

I think is summer for Atlassian team too :) Just joking! :)

Maybe September'll be a better month for a brand new installation :D

0 votes
joe_shomphe August 13, 2014

We are having the same issue setting up a brand new/clean jira server. After clicking upgrade to the latests greenhopper/agile release and restarting the service, we got the same error

Now Jira will no longer start.

0 votes
Deleted user August 12, 2014

this is my current dbconfig.xml, created after JIRA setup

<jira-database-config>

  <name>defaultDS</name>

  <delegator-name>default</delegator-name>

  <database-type>mssql</database-type>

  <schema-name>dbo</schema-name>

  <jdbc-datasource>

    <url>jdbc:jtds:sqlserver://192.168.1.50:1434/jira</url>

    <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

    <username>jira</username>

    <password>jira</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>

  </jdbc-datasource>

</jira-database-config>


Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events