UiPath Installation and Upgrade

The UiPath Installation and Upgrade Guide

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 75GB 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.
  • 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.

Orchestrator Installation Errors

  • If the Insights database being passed by the installer already exists, it must be deleted prior to proceeding with the install.

Insights Installation Errors

Unable to export PFX for certificate with subject 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|DeleteSisenseFoldersCommand|System.ApplicationException: Failed to delete folder at C:\ProgramData\Sisense ---> System.UnauthorizedAccessException: Access to the path 'advanced-formula-service.errors1.log' is denied.

  • Verify there are no Sisense folders located in either the C:\Program Files and C:\ProgramData directories.

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 web.config file is not valid or not in the correct format.

No Errors in _CommandExecutor.log file

  • Ensure that you meet all Insights hardware requirements.

Validation of Orchestrator Credentials Fails
If the Orchestrator Host admin password was Reset at first login, that change can result in a failed validation at this step. Perform an additional change of the Orchestrator Host admin password to resolve this issue and then proceed with your Insights installation.

Insights AdminTool Errors

Failed to retrieve tenant information Microsoft.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

  • If using Windows Authentication for SQL, ensure that you have changed the following services to use the Windows account: Sisense.CLRConnectorsContainer and Sisense.JVMConnectorsContainer.
  • Confirm that the Windows account used to connect to SQL is a member of the Local Administrator Group on the server

Exception occurred during backfilling jobs : Invalid object name dbo.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.

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.
  • If Orchestrator and Insights are on different sites/domains you could be getting an error related to cross-site cookies. If you see this issue with the .prism_shared cookie or see Sec-Fetch-Site = cross site on the request to Insights server passing the jwt token please change the Support Cross Site Cookies for Embedding flag to None in the Insights admin page. To access the admin page please go to https://<insightsserver>:<port>/app/account/login and login and then browse to https://<insightsserver>:<port>/app/settings/system#/system. You will see the flag under the Security Setting. Alternatively, you can run setup again so Insights is on the same site/domain as Orchestrator.

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.

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.

Updated about a month ago


Troubleshooting


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.