I set up a new instance of stash, selected SQL server as the external database and entered all the details correctly.
The setup continued correctly and all was good...
until I shut down TomCat and restarted it. Then I started getting this error message.
The following problem occurred which prevents Atlassian Stash from starting correctly:
I reinstalled stash from scratch and tried again, just stopping and starting TomCat and got the same error.
Can anyone provide any insight?
Worked it out. The stash-config.properties contained this:
which has an unescaped \ in it. I put in an extra one to make it:
and it worked fine when I restarted TomCat.
Obviously the setup procedure sets up the connection correctly but the restart which reads this file doesn't.
Unfortunately, the reason this happened is that you're using a "feature" Stash actually doesn't have; it just happens to accidentally work correctly on the setup and migration screens. I assume you entered "servername\instance" in the hostname box, since Stash doesn't have a separate text field for instance names. This usage is not actually supported. Stash just doesn't have an explicit check to prevent \ in the hostname. Because it's not supported, when the setup/migration changes are persisted to stash-config.properties, the \ is not escaped because it was not expected to be there.
You may want to vote for/watch https://jira.atlassian.com/browse/STASH-3108, which is the issue that was created to track this.
Apologies for the inconvenience!
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot