Crowd 2.8 service 64-bit fails to start - not a valid Win32 application
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
Symptoms
You can successfully install Crowd as a service following Installing Crowd as a Windows Service, however it fails when you try to start the service with an Windows error:
1
2
3
The ApacheTomcat 7 Crowd service could not be started.
A service specific error occured: 1.The System event log has the following message:
1
The Atlassian Stash service terminated with service-specific error Incorrect function.The following appears in the log: <Crowd install directory>/logs/commons-daemon.YYYY-MM-DD.log
1
2
3
4
5
6
7
8
9
10
[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 'ApacheTomcat 7 Crowd' 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 finishedDiagnosis
Unlike the similar scenarios with JIRA and Confluence, in which you cannot install the service, but similarly to Stash in the case of Crowd 2.8 you are able to install the service but cannot start it.
Cause
This is caused by the bundled tomcat version of Crowd being the 32-bit version. This is being tracked here:
Solution
Resolution
The same workaround Problems Installing JIRA applications as a service on Windows 64bit can be used in this case.
1) Replace the executable files according the workaround above.
2) Start CMD as administrator.
3) Remove the existing Crowd service (if it was installed already).
4) Install Crowd service again.
Was this helpful?