Insights Dashboard Shows: Unknown Error

How to handle when the Insights Dashboard shows: Unknown Error ?

Issue Description: Dashboard widget shows: Unknown Error.

image.png

Diagnosing / Resolving:

  1. If a build is occurring, it could be that the dashboard cannot be displayed why the build is occurring. This is rare and typically will go away after a minute or two. In a case like this, typically all dashboards will show the red X
  2. If the issue persists, login to Orchestrator and then go to the following URL: https:///app/test
    • All services should show green. If they do not, most likely a server needs to be restarted
    • Open services.msc and look for all items with the pre-fix 'Sisense'
    • Any service that is set to Automatic and is not running should be started
    • If a service goes down, the application logs can be checked at C:\ProgramData\Sisense\application-logs. For a given service it will typically have corresponding log. If a service went down, the starting point for diagnosing would be these logs
    • Alternatively, if the machine was restarted, it could be that the service was slow to start and Windows killed it
  3. If everything showed green, go to http://localhost:3030 and select the Restart services button. This will restart the services and possibly fix any service related issue
  4. If restarting the service fixes the issue, but it re-occurs, it would be best to open a support ticket with UiPath. It is also worth trying to restart all Sisense services
  5. If the issue is with one specific widget, most likely the issue is that an invalid formula was used.
    • Login to Orchestrator
    • Go to https:///app/main#
    • Find the dashboard with the problematic issue
    • Try recreating the specific widget that is failing
  6. Additionally, from the dashboard page within insights, try clicking the 'info' icon for the widget
image.png
  1. Capture the error message and share it with support if it is unclear what the issue is
  2. For the specific error: Unexpected token 'CASE' in FunctionParameters definition. can happen when the an asterix is used with out spaces
    • For example it could occur with the following formula
      • CASE
        WHEN(sum([ProcessId],((( all([@Process Baselines.Manual Time(mins)]) *dupcount([ProcessId]) -([Total RuntimeInSeconds]/60) )) /60)*all([@Process Baselines.Hourly Cost])) < 0) THEN 0
        ELSE sum([ProcessId],((( all([@Process Baselines.Manual Time(mins)]) *dupcount([ProcessId]) -([Total RuntimeInSeconds]/60) )) /60)*all([@Process Baselines.Hourly Cost]))
        END
    • Notice that there are no spaces around the '*' character
    • If this is encountered, try adding spaces or try recreating the widget.

If a cube build fails and widgets fail to load It is also possible that the Elastic Cube Catalog has become corrupted.

If while checking the ECM/Query Proxy Logs you see an error along the lines of {"error":{"code":500,"httpMessage":"Internal Server Error","message":"Could not connect to net.tcp:\/\/localhost:811\/CloudManagementService. The connection attempt lasted for a time span of 00:00:02.0044658. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:811. ","status":500}}] then do the following,

  1. Open the start menu or Task Manager and search for 'Services'
  2. Find the following services and stop them
    'Sisense.ECMS'
    'Sisense.ECMServer'
  3. Open the following path - C:\ProgramData\Sisense\PrismServer and rename the 'ElastiCubeCatalog' to 'ElastiCubeCatalog1'.
  4. Open the 'Services' as previously done and start the 'Sisense.ECMS' and 'Sisense.ECMServer' service once again, this will take a bit longer than usual forcing Sisense to create a new catalog folder.
  5. Once the services are back up, try to reload the dashboards