Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,638,568
Community Members
 
Community Events
196
Community Groups

installing bamboo using mssql brings this error.

2019-08-03 07:24:18,491 WARN [http-nio-8085-exec-4] [TextProviderHelper] The default value expression 'help.prefix' was evaluated and did not match a property. The literal value 'help.prefix' will be used.
2019-08-03 07:24:18,491 WARN [http-nio-8085-exec-4] [TextProviderHelper] The first TextProvider in the ValueStack (com.atlassian.bamboo.ww2.actions.setup.SetupDatabaseConnectionAction) could not locate the message resource with key 'db.mysql'
2019-08-03 07:24:18,491 WARN [http-nio-8085-exec-4] [TextProviderHelper] The default value expression 'db.mysql' was evaluated and did not match a property. The literal value 'db.mysql' will be used.

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 05, 2019

Hi @Wellard

These warning messages are not conclusive by themselves. We will need to check what error messages were logged before them to get better clues on what could be causing this scenario.

I was able to find a similar case in our support channel and it was caused by a SQL Server not being able to accept connections from Bamboo.

Please check what error messages you see right before the warning messages you see. If you can share them here we might be able to give you some directions to move forward.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events