After upgrading to Bamboo 5.11.1.1 I can no longer access Bamboo - fatal error MS-SQL
Asked by Neal Culiner:

On the heels of a disaster with JIRA 7.1.5 and MS-SQL now I upgraded Bamboo Server to the latest 5.11.1.1 and now I it's dead!
> Bamboo bootstrap failed: Failed to run pre-bootstrap upgrade tasks. Please contact Atlassian and [https://support.atlassian.com](https://support.atlassian.com/)

```
2016-05-05 11:39:56,311 ERROR [localhost-startStop-1] [AbstractUpgradeManager] java.sql.SQLException: Invalid column name 'ID'.java.sql.SQLException: Invalid column name 'ID'.	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)	at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)	at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:613)	at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:572)	at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:809)	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1288)	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1241)	at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)	at com.atlassian.bamboo.upgrade.tasks.v5_11.UpgradeTask51110DisallowDuplicateTrustedKeys.lambda$doUpgrade$20(UpgradeTask51110DisallowDuplicateTrustedKeys.java:46)	at com.atlassian.bamboo.upgrade.AbstractBootstrapUpgradeTask.withDatabaseConnection(AbstractBootstrapUpgradeTask.java:86)	at com.atlassian.bamboo.upgrade.tasks.v5_11.UpgradeTask51110DisallowDuplicateTrustedKeys.doUpgrade(UpgradeTask51110DisallowDuplicateTrustedKeys.java:42)	at com.atlassian.bamboo.upgrade.AbstractUpgradeManager.runUpgradeTask(AbstractUpgradeManager.java:206)	at com.atlassian.bamboo.upgrade.BootstrapUpgradeManagerImpl.doUpgrade(BootstrapUpgradeManagerImpl.java:59)	at com.atlassian.bamboo.setup.DefaultBootstrapManager.performPersistenceUpgrade(DefaultBootstrapManager.java:359)	at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:77)	at com.atlassian.bamboo.setup.BootstrapLoaderListener.contextInitialized(BootstrapLoaderListener.java:117)	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4812)	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5255)	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)	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)2016-05-05 11:39:56,313 INFO [localhost-startStop-1] [AbstractUpgradeManager] Completed task 51110 successfully.2016-05-05 11:39:56,313 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Pre-bootstrap upgrade tasks failedcom.atlassian.upgrade.UpgradeException: Pre-bootstrap upgrade tasks failed: [Task for build 51110 failed with exception: Invalid column name 'ID'.]	at com.atlassian.bamboo.setup.DefaultBootstrapManager.performPersistenceUpgrade(DefaultBootstrapManager.java:362)	at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:77)	at com.atlassian.bamboo.setup.BootstrapLoaderListener.contextInitialized(BootstrapLoaderListener.java:117)	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4812)	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5255)	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)	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)
```

I guess it's off to support again! Does Atlassian not do any testing or Q/A???

Yes, I googled this error and it's not the license string, it's not the hibernate table (only has one record), etc.


Answers:
author: Neal Culiner
body: Atlassian again has failed in Q/A and just like JIRA 7.1.5 Bamboo is dead due to another MS SQL failure in development and testing. Why Atlassian did not pull this download which continues to affect others is unacceptable!

<https://jira.atlassian.com/browse/BAM-17511>


author: Krystian Brazulewicz
body: Bamboo 5.11.3 has been released and it contains a fix for this problem.

The problem you've experienced is very rare and applies only to the SQLServer instances which were configured as case sensitive with regards to DB schema. IMO this is very unusual SQL Server configuration and we were not testing against it.

comments: author: Neal Culiner
body: The collation is set as outlined in the Bamboo installation guide.


author: Neal Culiner
body: I just double checked and the collation of my SQL Server 2014 instance is set as outlined in your installation guide to *Latin1_General_CS_AS*


Tags: bamboo-administration