Windows service fails to start: The process terminated unexpectedly

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

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

(Auto-migrated image: description temporarily unavailable)

Cause

  1. The user that's running the service is root and 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.

Solution

  1. Make sure that the user running Bamboo is a local user and not root: 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.8.0_255)

  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.8.0_255/bin/java.exe).

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.