Starting and stopping the Remedy SSO and Presentation Server components
Use the following sections to understand services and scripts used for starting and stopping the Remedy Single Sign-On and TrueSight Presentation Server components. You can also choose to skip the system requirements validation and forcefully start the Presentation Server.
Starting and stopping the Remedy SSO server
Starting and stopping the Remedy Single Sign-On server on Windows
Starting and stopping the Remedy Single Sign-On server on Linux
Verifying the status of Remedy SSO
Starting and stopping the Presentation Server
Failed to execute the [excerpt-include] macro.
Forcefully starting the Presentation Server service
Unless the computer hosting the Presentation Server meets the following system requirements, you cannot start the Presentation Server.
Failed to execute the [excerpt-include] macro.
- Available disk space (in MB): 2,000
You can verify whether you are unable to start the service because of the system requirements validation by looking at the following log files:
If you plan to use TrueSight Presentation Server with the TrueSight Capacity Optimization component only, you can skip validation of the system requirements, which includes the check for 32 GB of RAM, whenever the Presentation Server service starts. When Presentation Server is used with TrueSight Capacity Optimization only, the minimum RAM or memory requirement is 8 GB.
To skip validation of the system requirements and forcefully start the Presentation Server service
- Navigate to the following location:
- For Windows: <installationDirectory>\truesightpserver\conf\custom
- For Linux: <installationDirectory>/truesightpserver/conf/custom
- Edit the csr.conf file, add the following property, and save the file.
skipResourceCheck=true - Restart the product service.
Alternatively, run the following command to forcefully start the Presentation Server service: tssh server start force
However, this method does not guarantee the automatic restart of the Presentation Server service after restarting the Presentation Server host.
Related topic