Problem with installing Confluence standalone(zip file) as windows service with 64 bit JDK/JRE

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

Confluence service does not start after installing Confluence as Service

[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 'confluence' 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:\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

Diagnosis

Open Windows Command Prompt, type java -version

Expected result:

java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

Cause

By default, standalone installation is running on tomcat6/tomcat7/tomcat8 32 bits

Resolution

Change the tomcat6/tomcat7 to 64 bits

By default, Confluence standalone comes together with 64 and 32 bits tomcat

  1. Shutdown Confluence
  2. Go to ConfluenceInstallationDirectory/bin
  3. Look for :
    1. tomcat6.exe (for confluence 5.5 and above, confluence is using tomcat7)

    2. Rename it to tomcat6.exe.32
    3. Rename tomcat6.exe.x64 to tomcat6.exe
  4. Start Confluence Service

 

Please uncheck the "hide file extension" for your windows if you can't change the file type

http://windows.microsoft.com/en-my/windows/show-hide-file-name-extensions#show-hide-file-name-extensions=windows-7

Last modified on Nov 2, 2018

Was this helpful?

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