- Release Notes
- Getting Started
- Installation and Upgrade
- Access and Permissions
- Interacting with Insights
- Logs
Insights
This page provides an overview of common errors and mistakes that can occur during Insights installation, and potential methods to avoid or remedy them.
To improve the response time and efficency of the support team, make sure to find out how to capture logs if needed to debug by in Capturing logs page.
If logs aren't flowing in the intended pattern (ie all logs, or only last logs or error logs), make sure your configuration is correct.
- If using self-signed certificates, you must use the FQDN for your server (i.e.
insights.corp.uipath.comnotinsights). - The Orchestrator certificate must be placed in the Local Machine 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 Machine 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.
Selecting the Insights language is done from the Orchestrator tenant settings. All users in that tenant share the same language.
The specified domain does not exist or cannot be contacted
- The Orchestrator certificate must be placed in the Local Machine Trusted Root store on the Insights machine.
- The Insights certificate must be placed in the Local Machine Trusted Root store on the Orchestrator machine.
- Ensure Orchestrator and Insights have the same
TLSsetting.
- Check the port that you specified in the installation, to make sure it is enabled in the machine and in Windows Firewall.
- Make sure the HostName is DNS resolvable.
After installing Insights, if you go to , you may get the following error:
There was an error while performing this operation.
Details:
Filename: \\)?\C:\...your installation pathThere was an error while performing this operation.
Details:
Filename: \\)?\C:\...your installation pathThis error may occur if the IIS Hosting Bundle was not installed correctly.
To fix this issue, take the following steps:
- Go to Add or remove programs, search for
Microsoft .NET Core, and click Modify
- 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.
System.Exception: Migration failed then, you should use the following scripts to manually index the RobotLogs and Queueitems.
RobotLogs Index
IF NOT EXISTS(SELECT * FROM sys.indexes WHERE Name = 'IX_TenantId_ProcessName' and OBJECT_NAME(object_id) = 'RobotLogs')
CREATE NONCLUSTERED INDEX [IX_TenantId_ProcessName] ON [dbo].[RobotLogs]
(
[TenantId] ASC,
[ProcessName] ASC
)IF NOT EXISTS(SELECT * FROM sys.indexes WHERE Name = 'IX_TenantId_ProcessName' and OBJECT_NAME(object_id) = 'RobotLogs')
CREATE NONCLUSTERED INDEX [IX_TenantId_ProcessName] ON [dbo].[RobotLogs]
(
[TenantId] ASC,
[ProcessName] ASC
)QueueItemEvents Index
if not exists (select * from sysindexes where id=object_id('dbo.QueueItemEvents') and name='TenantId_ProceStatus_QI_INDEX')
CREATE NONCLUSTERED INDEX [TenantId_ProceStatus_QI_INDEX] ON dbo.QueueItemEvents (TenantId, ProcessingStatus) INCLUDE (QueueItemId);if not exists (select * from sysindexes where id=object_id('dbo.QueueItemEvents') and name='TenantId_ProceStatus_QI_INDEX')
CREATE NONCLUSTERED INDEX [TenantId_ProceStatus_QI_INDEX] ON dbo.QueueItemEvents (TenantId, ProcessingStatus) INCLUDE (QueueItemId);If you receive the The term ‘Get-WindowsFeature’ is not recognized as the name of… error, follow these steps:
- Go to the Windows search bar and search for Environment variables.
- Click Environment variables from the System Properties window.
- Click Edit on the Path variable and add the path here:
C:\Windows\system32\WindowsPowerShell\v1.0\Modules. - On first use of the product, if a dashboard is showing incomplete data, it may be because of a cache. Try going to "Dashboard actions" and then select "Clear cache and refresh".
