JIRA Service Fails To Start in Windows - Is Not a Valid Win32 Application
JIRA Service fails to start in Windows with the following error in the Windows event log:
Event ID 7000 and "%1 Is Not a Valid Win32 Application"
The following appears in
commons-daemon.log for Apache Tomcat:
[2012-11-24 13:37:25] [info] Running 'jira' Service... [2012-11-24 13:37:25] [info] Starting service... [2012-11-24 13:37:25] [error] %1 is not a valid Win32 application. [2012-11-24 13:37:25] [error] Failed creating java C:\Progra~2\Java\jdk1.6.0_24\jre\bin\server\jvm.dll [2012-11-24 13:37:25] [error] %1 is not a valid Win32 application. [2012-11-24 13:37:25] [error] ServiceStart returned 1 [2012-11-24 13:37:25] [error] %1 is not a valid Win32 application. [2012-11-24 13:37:25] [info] Run service finished. [2012-11-24 13:37:25] [info] Commons Daemon procrun finished
There are a number of known causes for this problem:
- Windows has issues with services that have spaces in the file path as described in this Microsoft article. The root cause of this issue can be due to the the JIRA service using the JRE/JDK that is installed in the system rather than the bundled JRE that came along with the Standalone Installer for Windows. And the installed JRE usually has a space in the path as it is usually at the location "
C:\Program Files (x86)\Java" or "
- JIRA has been installed in a 64-bit Windows version using the 64-bit installer, however is using 32-bit Java.
- JIRA has been installed in a 64-bit Windows version using the 32-bit installer, however is using 64-bit Java.
- Service.bat could be pointing to the wrong version of Tomcat. If JIRA is using 64-bit Java on 64 bit Windows, service.bat could be pointing to the 32bit tomcat8w.exe, hence the incompatibility and not being able to start the service.
- Due to a known bug - JRA-30699Getting issue details... STATUS the installer has not defaulted to the bundled JRE.
When installing JIRA onto a 64-bit Windows, we recommend to use the 64-bit installer and bundled JRE as using 32-bit on 64-bit architecture is known to cause problems as in our JIRA crashes when running as a Windows Service KB article.
Try to start JIRA using the start-jira.bat file in JIRA's bin directory to restore access until the Windows Service is fixed. If this doesn't work, it could be due to the
%JAVA_HOME% variable pointing to the incorrect JVM as well.
Verify that JIRA is using the correct JVM by editing the service, as in our Setting Properties and Options on Startup documentation. If the bundled installer was used, the JVM should be the following:
This may be in
Program Files (x86)if using Windows 64-bit and JIRA 32-bit. If this is how your JIRA is configured, we recommend migrating to 64-bit JIRA on 64-bit Windows.
- Start JIRA using the Service.
- If this does not resolve the problem, delete the
%JAVA_HOME%environment variable, as set in our Installing Java docs.
Reinstall the service with the following, executing on the command line in
service.bat remove service.bat install
- After reinstalling the service, attempt to start it.
Check the service.bat file and make sure it is pointing to the right version of tomcat. If using 32 bit Java: set ”EXECUTABLE=%CATALINA_HOME%\bin\tomcat8w.exe” If using 64bit Java: set “EXECUTABLE=%CATALINA_HOME%\bin\tomcat8w.exe.x64”. Remove and Reinstall service.
"There has been some report as "tomcat8w.exe.x64" is being removed after the upgrade process from under the bin folder so you need to install the 64 bit tomcat and place it under the bin folde for the "atlassian-jira-software.x.x.x\bin"."