Problem
When navigating to a ExoInsight in a Chrome browser window, an error message with HTTP ERROR 500 followed by a bunch of coding errors is displayed.
Cause
This is caused by one of the following:
- Adding an Essbase, PBCS, or FCCS environment with a space or special character in the name
- Manually modifying the ExoInsight configuration file and introducing a syntax error
Solution
If an Essbase, PBCS, or FCCS environment was added that contained a space or special character in the name, the name must be fixed. To do so, open the configuration file located at the following location in a text editor:
<installation directory>/casabase/config
Find the entry with the special character or space in the name and remove the special character or space, or remove the entry entirely. Save the file, then refresh ExoInsight.
If a syntax error was made when manually modifying the configuration file, make sure the following is true:
- Every open bracket has an associated closing bracket
- There are no empty lines at the bottom of the file