Windows service launches old version after upgrade
Symptoms
After upgrading Stash the Service launches the old Stash release.
Cause
The service hasn't been installed or updated for the new instance.
The Stash installer offers an option for installing Stash as a service and you probably chose not to install it as a service, which causes this situation.
Resolution
Service Name
If you don't know the exact name of your old Stash service, you can find out what they are by following the steps below:
- Navigate to 'Control Panel' > 'Administrative Tools' > 'Services'.
- The 'Services' window should appear.
- Right-click on the service you wish to find out the name of, and select 'Properties' from the popup menu.
- The 'Service name' should appear in the 'General' tab.
- Use this parameter as a substitute for
<ServiceName here>on the command below.
- Use this parameter as a substitute for
Steps to remove the existing service:
- Navigate to the Stash installation directory.
- Open an administrator level command-prompt
- Remove the old service, the service is likely named "AtlassianStash". You can check the actual name by viewing the Properties of the service:
service.bat remove <ServiceName here>
Sometimes, executing the command above might result on the following message:
The JAVA_HOME environment variable is not defined correctly. This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JREIf that happens to you, make sure your
JAVA_HOMEis pointing to a JDK as opposed to a JRE. For example, we've had customers pointing toc:\programs\java\jdk1.8.0_05\jreand changing it temporarily intoc:\programs\java\jdk1.8.0_05\jrewith aSET JAVA_HOME=c:\programs\java\jdk1.8.0_05before executing the command above fixes it. Install the new service using the instructions from this document: