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.

Add INFO Level to RobotLogs

If you've upgraded your Insights version to 2021.10 and want RobotLogs ingestion to include INFO level logs and above, you need to modify Orchestrator settings, as follows:

1. Navigate to C:\Program Files (x86)\UiPath\Orchestrator and open the UiPath.Orchestrator.dll.config file to modify Orchestrator settings
2. Identify the following settings:

   <logger name="Robot.*" ruleName="insightsRobotLogsRule" enabled="false" minlevel="Info" writeTo="insightsRobotLogs">
   <filters defaultAction="Ignore">
   <when condition="level >= LogLevel.Error or ends-with('${message}',' execution ended')" action="Log" />
   </filters>
   </logger>

3. Replace these settings with the following:

   <logger name="Robot.*" ruleName="insightsRobotLogsRule" enabled="true" minlevel="Info" writeTo="insightsRobotLogs"/>

4. Save the file and then restart IIS.

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.

Changing the Insights Language

Selecting the Insights language is done from the Orchestrator tenant settings. All users in that tenant share the same language.

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.

Connection Issues

• Check the port that you specified in the installation, to make sure it is enabled in the VM and in Windows Firewall.
• Make sure the HostName is DNS resolvable.

Portal Showing 500 Error After Installation

After installing Insights, if you go to IIS Manager > UiPath Insights website > Logging, you may get the following error:

There was an error while performing this operation.
Details:
Filename: \)\)\)\)?\)\)C:\)\)...your installation path

This error may occur if the IIS Hosting Bundle was not installed correctly.

To fix this issue, take the following steps:

1. Go to Add or remove programs, search for Microsoft .NET Core, and click Modify
   
   

   

   
   
2. Click Repair in the newly open window.
   
   

   

   
   
   Note: If this does not solve the issue, we recommend uninstalling and then reinstalling the IIS Hosting Bundle.

Miscellaneous Issues

If you receive the The term ‘Get-WindowsFeature’ is not recognized as the name of… error, follow these steps:

1. Go to the Windows search bar and search for Environment variables.
2. Click Environment variables from the System Properties window.
3. Click Edit on the Path variable and add the path here: C:\Windows\system32\WindowsPowerShell\v1.0\Modules.