Issue
- When navigating to the Goliath Console, the webpage is blank and never loads.
- HTTP Error 500 when trying to connect to the Goliath console
Troubleshooting Steps
- Confirm that the "MonitorIT Server Service" is running in Windows Services
- If using remote SQL, the service should be running as an account that has "db_owner" rights to the database
- In task manager, confirm that the process "RPMCCS.exe" is running.
- If it is in a "suspended" state, stop the "MonitorIT Server Service" and confirm that the process stops running then start the "MonitorIT Server Service". Upon restart, depending on the size of your environment, it could take about 5-10 mins for the technology to come back up.
- If this does not work, try disabling the "MonitorIT Server Service", rebooting the Server, and then reenabling and starting the "MonitorIT Server Service"
- If it is in a "suspended" state, stop the "MonitorIT Server Service" and confirm that the process stops running then start the "MonitorIT Server Service". Upon restart, depending on the size of your environment, it could take about 5-10 mins for the technology to come back up.
- Make sure that none of the drives are full on the Goliath Server.
- Ensure in IIS Manager that the site "GoliathWeb" is running and that the application pool "GolAppPool" is running
- SQL Server Issues could also prevent the Goliath Server from not loading.
- The most common issues are permissions, SQL drive space and SQL transaction log size.
- If using remote SQL, the account that is running our MonitorIT Service Service must have db_owner rights on our database via user mappings.
- Search for errors within the "MonitorIT Server Logs" located in the bin folder in the install directory (Program Files (x86)\MonitorIT\Bin). Open the log and search for common error terms (screenshot examples below):
- Catch fault
- Unable to send data
- Unable to open
- communication link failure
- The most common issues are permissions, SQL drive space and SQL transaction log size.
Server Log Examples:
