Problem

After upgrading Bitbucket Server or updating the JVM, the  Bitbucket Server service will no longer start. Trying to run "NET START BITBUCKET" gives the following:

The Atlassian Bitbucket Server service could not be started.

A service specific error occured: 1.

The System event log has the following message:

The Atlassian Bitbucket Server service terminated with service-specific error Incorrect function.

The following appears in the log:  <Bitbucket Server install directory>/logs/commons-daemon.YYYY-MM-DD.log

[2013-02-19 20:51:42] [info]  Commons Daemon procrun (1.0.10.0 64-bit) started
[2013-02-19 20:51:42] [info]  Running 'bitbucket' Service...
[2013-02-19 20:51:42] [info]  Starting service...
[2013-02-19 20:51:42] [error] %1 is not a valid Win32 application.
[2013-02-19 20:51:42] [error] Failed creating java C:\devTools\Java\x32\jdk1.6.0_33\jre\bin\server\jvm.dll
[2013-02-19 20:51:42] [error] %1 is not a valid Win32 application.
[2013-02-19 20:51:42] [error] ServiceStart returned 1
[2013-02-19 20:51:42] [error] %1 is not a valid Win32 application.
[2013-02-19 20:51:42] [info]  Run service finished.
[2013-02-19 20:51:42] [info]  Commons Daemon procrun finished

However, Bitbucket Server will be up and running if you run it directly, as in executing the start-bitbucket.bat file. Tomcat comes up running and everything will work.

Cause

1. You have a 64-bit OS and you skipped the custom changes that have to be done to your new installation.
2. There is a mismatch between the Java JVM (32-bit) and the Bitbucket Server binary (64-bit).

Resolution

1. Skipped custom changes

If you are using a 64-bit version of Windows, first ensure that Bitbucket Server uses a 64-bit JVM (check by running java -version  in a Command Prompt, and ensure that the  JAVA_HOME system environment variable points to the 64-bit JVM), and then replace the 32-bit Tomcat binaries with their 64-bit counterparts  in the  <Bitbucket Server installation directory>/bin directory:

cd <BSERV-INST/bin>
rename tomcat7.exe tomcat7.exe.x86
rename tcnative-1.dll tcnative-1.dll.x86
rename tomcat7.exe.x64 tomcat7.exe
rename tcnative-1.dll.x64 tcnative-1.dll

2. JVM mismatch

1. Remove the existing service, e.g. <Bitbucket Server install directory>/bin/service remove
2. Install a 64-bit Java JDK.
3. Open a shell window and ensure JAVA_HOME points to the root install folder of the Java version, e.g. C:\devTools\Java\x64\jdk1.7.0_10
4. Install the service, e.g. <Bitbucket Server install directory>/bin/service install

3. Your Windows service is pointing to the incorrect JVM

 Sometimes you could be

• Open the command window from Start >> Run >> type in 'cmd' >> Enter
• cd to the bin directory the Stash Installation (<Bitbucket Installation dir>/bin).

• Run from there:

• Bitbucket 4.x and older

  tomcat8w //ES//<ServiceName here>

• Bitbucket 5.x and newer

  bservmgr.exe //ES/<ServiceName here>

• A window will pop up. Click on the Java tab. On the field "Java Virtual Machine" check the value that is input.

• It will be %JAVA_HOME%\bin\server\jvm.dll. For example, there was a situation that the customer had:

  • C:\program files\java\jre1.8.0_45\bin\server\jvm.dll
  • But we pointed his service to a different JRE: C:\Program Files\Java\jre1.8.0_60\bin\server\jvm.dll

Make sure the account used to start the service has access to the jvm.dll otherwise, there will be an error message to start Bitbucket Service as following:

[2020-10-13 13:57:43] [info] [ 6896] Starting service...
[2020-10-13 13:57:43] [error] [ 6896] Failed creating java c:\program files\atlassian\jira\jre\bin\server\jvm.dll
[2020-10-13 13:57:43] [error] [ 6896] Access is denied.