Troubleshooting installation and upgrade issues
This topic provides troubleshooting information with respect to installation of Remedy Single Sign-On.
When you install Remedy SSO server on the embedded database
The Tomcat does not automatically start after installation, and you see an error when you try to log in.
Stop Tomcat before installation, and start it when the installation is complete.
Alternatively, restart Tomcat if it was running during the installation.
When you install or upgrade Remedy SSO server
The Tomcat can delay its shutdown process triggered by the installer itself, and cause the installer to fail with below error in the installation logs:
Stop the Tomcat, and run the Remedy SSO
installer to upgrade.
The installer can run without Tomcat service up.
For more information about the problem, see knowledge article in BMC Communities.
When you install Remedy SSO server manually
You get the following errors after you have encrypted the database password:
You can ignore these errors. For more information about these errors, see
|When you restart the Tomcat server|
You might encounter the following database credential exception in the Catalina.log file:
You can ignore this exception, as the Remedy SSO database connectivity works fine.
When you upgrade Remedy SSO server from a version earlier than 19.11 to version 19.11 and later
After logging in to Remedy SSO Admin Console as an administrator only Local User tab is displayed. The rest of the administering options are not displayed.
Log out from the Remedy SSO Admin Console, and log in again.
After upgrade from version earlier than 19.11, you have got a role of SaaS administrator.
When you upgrade TrueSight that is integrated withRemedy SSO and is on the embedded PostgreSQL
Remedy SSO service stops and shuts down the embedded PostgreSQL database.
The upgrade fails with the following error:
Perform the following steps: