You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi I've tried everything here (https://confluence.atlassian.com/bamkb/windows-service-fails-to-start-the-process-terminated-unexpectedly-376833593.html) - with except on the wrapper.conf--how do I recreate this??
Bottom line I continue to get the 1067 when trying to start as a service. Appreciate the feedback.
Hi @Jason_Smith ,
If you have recently upgraded Bamboo to 7.0.2+ and you have installed the service that comes with the installer and you do not see any entry in atlassian-bamboo.log when the service is started, please be informed that the default Windows service is run as Local Service instead of Local System. As a result, the service user will not have permission to write to your server logs. This is due to changes in recent versions of Tomcat and the Commons Daemon.
To work around the restrictions of the Local Service user, our recommendation is to run the service as a local user as described in this KB article - Running Bamboo as a Windows service as the local user
Hope that helps.