Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,467,448
Community Members
 
Community Events
177
Community Groups

Error upgrading to atlassian-bamboo-5.14.4.1 failed wirh error

mersinport
mersinport May 06, 2020

We are currently using 5.10.3. While upgrading to 5.14.4.1 we get error

2020-05-06 18:23:01,648 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)

Answer
Watch
Like Be the first to like this
184 views

1 answer

1 accepted

1 vote
Answer accepted
Moses Thomas
Moses Thomas Community Leader May 06, 2020

@mersinport   This is a bug which is already  registered by  Atlassian , but you can apply the workaround  mentioned in the  ticket  https://jira.atlassian.com/browse/BAM-17511

 

Kind regards,

Mo

Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS

Atlassian Community Events

See all events