Windows service fails to start: The process terminated unexpectedly

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Running Bamboo as a Windows service fails with: The process terminated unexpectedly.

Cause

  1. The user that's running the service is not a local user.
  2. Incompatible JDK version or having more than one JDKs (Example: 32-bit JDK and 64-bit JDK). 
  3. The "wrapper.conf" file is missing from <bamboo-installation-directory>/conf due to an unfinished/corrupted installation or upgrade.

  4. JAVA_HOME is not set up or not pointing to the correct directory.

  5. The PATH environment variable doesn't include the JDK directory or it's located after the system32 path.

Workaround

  1. Make sure that the user running Bamboo is a local user: Running Bamboo service on Windows as the local user.
  2. Check that there is only one JDK installed on the machine and that its version is compatible with the version of Bamboo: Bamboo supported platforms. (Check the java version by running java -version)
  3. Make sure that the wrapper.conf file exists in the <bamboo-installation-directory>/conf. If Bamboo can be started manually, it shows that this file exists. 
  4. Run echo %JAVA_HOME% and check if it's pointing to the correct JDK. (Ex.: C:\Program Files\Java\jdk1.7.0_10)
  5. Confirm that the %PATH% environment variable contains the current JDK in its definition and that it comes before the system32 path.
  6. Try to explicitly set the path to the Java installation in the parameter "wrapper.java.command" in the wrapper.conf file. This parameter value is by default java, update it to look into the exact directory (Ex: C:/Program Files/Java/jdk1.7.0_10/bin/java.exe).

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.