UiPath Documentation
insights
2020.10
false
Insights
  • Release Notes
    • 2020.10.0
      • 2020.10.2
  • Getting Started
  • Installation and Upgrade
    • Hardware and Software Requirements
    • Upgrading
    • Troubleshooting
  • Insights in Orchestrator
  • Insights Portal
important :
As of December 31st, 2023, any version of UiPath Insights older than 2021.10, including all Insights dashboards, will no longer be accessible at all, without moving to a later version.

Troubleshooting

This page provides an overview of common errors and mistakes that can occur during Insights installation, and potential methods to avoid or remedy them.

Important:

Be sure that you have followed the Insights Installation instructions closely.

Installation Logs​

The log file most helpful in debugging installation issues can be found in the %USERPROFILE%\AppData\Local\Temp directory with the name UiPathInsightsInstaller_<xxxx>_CommandExecutor.log.

Enable verbose logging during installation by passing the /L*V parameter along with a target file where the logs are to be written. For example: /L*V log.txt.

Common Errors​

Basic Validation Errors​

  • Servers must be resolvable between Orchestrator**>Insights and Orchestrator>Client>**Insights. Ensure that you can:
    • Access Orchestrator from the Insights machine. For example: https://<orchestrator_server>:<port>/.
    • Access Insights from the Orchestrator machine. For example: https://insightsserver:port/app/account/login.
    • Access Insights from the Insights machine.
  • The Insights server must have at least 16GB RAM and 50GB free disk space.
  • The user installing Insights must have administrator rights.
  • For existing or failed installations, make sure there are no Sisense folders located in either the C:\Program Files and C:\ProgramData directories.

Certificate Errors​

  • If using self-signed certificated, you must use the FQDN for your server (i.e. insights.corp.uipath.com not insights).

  • The Orchestrator certificate must be placed in the Local Computer Trusted Root store on the Insights machine.

  • If you are encountering errors when trying to change your Insights certificate, make sure to follow the instructions provided in Updating Your Insights Certificate.

  • The Insights certificate must be placed in the Local Computer Trusted Root store on the Orchestrator machine.

    Note:

    If you are generating a self-signed certificate for Insights manually, please make sure it is marked as exportable with the private key and imported into the Personal store.

Insights Installation Errors​

Unable to export PFX for certificate with subject name <name>

  • When importing the certificate, ensure that you selected export the private key option.

ERROR|DeleteSisenseFoldersCommand|System.ApplicationException: Failed to delete folder at C:\Program Files\Sisense -System.UnauthorizedAccessException: Access to the path 'node.exe' is denied.**

  • Ensure the user installing Insights has administrator rights.

ERROR|SetupSslCommand|System.ApplicationException: Unable to create self signed certificate with subject name xxxx.xxxx.com System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'CERTENROLLLib.CX509PrivateKey'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{728AB362-217D-11DA-B2A4-000E7BBB2B09}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).**

  • Insights only supports Windows 2016+, ensure you are not using an earlier version.

ERROR|UpdateOrchestratorConfigCommand|System.ApplicationException: Failed to update Analytics settings in Orchestrator

  • Make the Insights parameters were correctly passed during Orchestrator installation/upgrade.

ERROR|CustomizeBrandingCommand|System.ApplicationException: Failed to Authenticate HTTP client

  • Ensure that you have local firewall rules configured for the Insights port and set program=any, and that you have enabled the same port through your cloud hosting provider (AWS, Azure, etc.).

INFO|UpdateOrchestratorConfigCommand|Response Content : {"message":"Configured encryption key is not in a valid Base64 format.","errorCode":1801,"resourceIds":null} INFO|UpdateOrchestratorConfigCommand|Response status has no error - 'Configured encryption key is not in a valid Base64 format.

  • Ensure the APP_ENCRYPTION_KEY from the Orchestrator UiPath.Orchestrator.dll.config file is valid or not in the correct format.

No Errors in_CommandExecutor.log file

  • Ensure that you meet all Insights hardware requirements.

Insights AdminTool Errors​

Failed to retrieve tenant informationMicrosoft.Rest.HttpOperationException: Operation returned an invalid status code BadRequest

  • Ensure you can access Insights and Orchestrator at their respective URLs, and are using valid credentials for the Orchestrator host tenant.

Exception while starting WarmStartCommand(s) : A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

  • Ensure you have enabled Named Pipes and TCP/IP in SQL Server Configuration Manager.

Failed to setup RobotLogs table - Failed while running Portal caused by Sisense returned unsuccessful status code

Exception occurred during backfilling jobs : Invalid object namedbo.IngestionMarkers.

  • Ensure the Insights database specified during Orchestrator installation still exists on the SQL Server specified. Please make sure that Insights database is not already created on the SQL machine from a previous installation.

Failed to retrieve tenant information- System.InvalidOperationException: Sequence contains no elements

  • Ensure you are passing the correct tenant name.

Could not start connector

If you specified a custom port number for the Host Servername on the machine where the Insights database is located with a comma, such as sql.uipath.com,1733, this could cause the connector not to start.

  • On the Insights machine:

  1. Navigate to C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost and open the 'uipath_insights.properties' file.

  2. Find the 'insights.db.conn' property, and check to that the hostname and port are separated by a colon.

    Ex:

    insights.db.conn=jdbc:sqlserver://insightscore.database.windows.net:1433;Database=insights;user=uipath
insights.db.conn=jdbc:sqlserver://insightscore.database.windows.net:1433;Database=insights;user=uipath

If they are not, replace the separator with a ":".

Usability Errors​

Feature is not licensed

  • Ensure that Insights is licensed at host level. Remove any license added at tenant level.

Could not connect to the server (#101) error

  • Ensure that you have restarted IIS on all Orchestrator nodes and closed all open browsers prior to attempting to access Insights.
  • Check that you can access Insights from https://<insightsserver>:<port>/app/account/login, and accept any certificate warning, if applicable.

widget type : inputwidget is not registered

  • Make sure the Sisense.Plugin service is running.

All widgets on a dashboards show a red "X"

  • A data cube build is in progress, wait a few seconds and refresh the page.

No Elasticcube servers are available

  • Ensure that you have successfully enables the respective tenant using the Insights AdminTool.

No data in dashboards

  • Ensure that you have successfully enables the respective tenant using the Insights AdminTool.
  • If this is the first time data is being loaded into Insights, it may take up to an hour to complete.

The ElastiCube Default-Cube build on LocalHost has failed

  • Perform a Replace All build from app/data or run the Insights AdminTool using the rebuild command.

java.lang.Exception: Schema of the requested table has been changed. Please update your model.

  • Perform a Replace All build from app/data or run the Insights AdminTool using the rebuild command.

Duplicate column errors in Orchestrator or connector logs.

  • Follow the instructions to change the case sensitive flag to false. Duplicate columns will be merged into one.

TLS Errors​

The specified domain does not exist or cannot be contacted

  • The Orchestrator certificate must be placed in the Local Computer Trusted Root store on the Insights machine.
  • The Insights certificate must be placed in the Local Computer Trusted Root store on the Orchestrator machine.
  • Ensure Orchestrator and Insights have the same TLS setting.

Verifying the Insights Services​

After Insights installation has finished, navigate to the following URL to check that all services are running: https://insightsserver:port/app/test.

If any service is not running, navigate to the following URL and restart it: https://localhost:3030.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated