Insights Build Failed

How to handle Insights Build failure?

Issue Description : Insights does not load data, and on Restart Sisence.Proxy service, restart IIS, it still does not load. On opening localhost:14996/paths, the file is obtained.

Resolution :

  1. Try browsing HTTP://localhost:14996/paths and check if there is a response. One possibility could be it prompts to enter username and password which is not supported.
  2. Check the authentication in IIS Server for Sisense.web site and ensure "Windows Authentication " is disabled while "Anonymous Authentication " is enabled.
  3. With the right authentication, Proxy Service will run without any issues and it will also allow communication with ECMS service which will allow cube build.
  4. Try to turn off the Windows Server firewall
    • or at least add outbound and inbound rules in Advanced Settings in Windows Firewall for Sisense Service executable for Query Proxy Service


If still no result, try the below troubleshooting approaches:
If data is returned, like shown in the screenshot below:
![](upload://k6clGvh0X0kdOovzru0ast129Ad.html)
  • Restart the ECMS service by following the steps below:
    • On your Sisense webserver, open the Control Panel
    • Click on 'Administrative Tools'
    • Click on 'Services'
    • For each of the services, please find them in the list and repeat steps 5&6, in the following order:
      • Sisense.ECMS
    • Right-click on it and select 'Stop' (make sure its status field becomes blank)
    • Right-click on it and select 'Start' (make sure its status field changes to "Running")

If data returned is not seen, like shown in the screenshot below:
![](upload://hnFkch3pOW9MBYnwYpAAnulVCa0.html)
  • Restart IIS by following the steps below:
    • On your Sisense web server, go to the Start Menu and type 'cmd'
    • Right-click the shortcut and choose 'Run as Administrator'
    • In the command line, type: 'iisreset' hit Enter and wait for the IIS server to restart.
    • Close the command prompt window.
    • Try to reload the dashboard.

If the steps above did not resolve your issue, do the following to create a new catalog folder which will most likely resolve the issue.

Important Note: Be aware that build-scheduling settings will be erased after the operation, so re-configure these on all ElastiCubes.
  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

Validation Steps: In case all the above suggestions did not help, validate the below points to understand better the issue
  • Duration of facing this issue (Insights not loading data and getting the query-proxy false)?
  • so Insights is up and running/ accessible, but the only thing is that it does not load data?
    • what is the latest data injection displayed?
  • does this happen only with one specific build/ cube?
  • at the moment, does rebuilding the cube manually fails?
  • replicate the issue and collect & share with UiPath Support the following details:
    • (click to rebuild manually the build) > click on F12 (Developer Console)
      • go to the Console tab and take a screenshot(s) to see all the errors. Please share with us the capture(s)
      • go to the Network tab and take a screenshot(s) to see all the errors. Please share with us the capture(s)
    • new fresh Event Viewer traces from the Insights server + Orchestrator server


Add outbound and inbound rules in Advanced Settings in the Windows Firewall for Sisense Service executable for Query Proxy Service. Also there is to be confirmed that only an inbound rule is present which allows everything.

Make sure to implement the same outbound traffic rule: for Sisense Service executable, for Query Proxy Service, and for the rest of inbound services.