RMS Fails to load after 4.7 Upgrade
Frequently Asked Questions
Brand:
- AMX
Models:
- Resource Management Suite [RMS]
Question:
Why does RMS Fail to load after 4.7 Upgrade?
Answer:
RMS 4.7 Upgrade Failure
Due to a change in Tomcat, an issue has been discovered when performing the upgrade process from previous versions of RMS to RMS 4.7. When the issue occurs, the Tomcat service will start, but the RMS webpage cannot be accessed. You will receive an error in the Tomcat stderr log, but nothing in the actual RMS logs located under Program Data because this error never allows the RMS program to start.
Starting with Tomcat 9.0.24 there was a new option added into the Tomcat configuration. If you open the Tomcat Configuration tool you will see a new tab called Log On. This allows you to configure what account is used to run the Tomcat service. When an upgrade is completed for RMS, the choice “Local Service account” is selected by default in the Tomcat configuration tab. This is what causes the failure to occur.
In order to correct the issue:
- Stop the Tomcat service
- Open the Tomcat configuration program
- Select the Log On tab
- Change the “Log on as:” selection to “Local System account”
- Click Apply
- Start the Tomcat service