- Release Notes
- Getting Started
- Access and Permissions
- Installation and Upgrade
- Interacting with Insights
- Historical data export
- Logs
- Performance and Scalability
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.
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.com
notinsights
). - 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
TLS
setting.
- Check the port that you specified in the installation, to make sure it is enabled in the machine and in Windows Firewall.
The Portal may show a 500 because of a few reasons:
- Something went wrong with IIS.
- There may be an issue with the Insights application such as incorrect configuration or issues with the database connection.
To verify IIS issues,
Logging
, you may get the following error:
There was an error while performing this operation.
Details:
Filename: \\?\C:\...your installation path
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:
- Go to Add or remove programs, search for
Microsoft .NET Core, and click Modify.
- Click Repair in the newly open window.
C:\ProgramData\UiPath
Insights\
to check the Insights logs. If you cannot locate the issue, please
contact UiPath support.
During installation you can encounter IIS issues. If the W3SVC service fails to start, you can run the following command.
net start w3svc
net start w3svc
System.Exception: Migration failed
then, you should use the following scripts to manually index the RobotLogs
and Queueitems
.
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
)
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 NOT EXISTS(SELECT * FROM sys.indexes WHERE Name = 'IX_JobEvents_JobId_TenantId' and OBJECT_NAME(object_id) = 'JobEvents')
CREATE NONCLUSTERED INDEX [IX_JobEvents_JobId_TenantId] ON [dbo].[JobEvents]
(
[JobId] ASC,
[TenantId] ASC
)
IF NOT EXISTS(SELECT * FROM sys.indexes WHERE Name = 'IX_JobEvents_JobId_TenantId' and OBJECT_NAME(object_id) = 'JobEvents')
CREATE NONCLUSTERED INDEX [IX_JobEvents_JobId_TenantId] ON [dbo].[JobEvents]
(
[JobId] ASC,
[TenantId] ASC
)
The port 443 (or 543) is being used by another web application or program.
This can be caused by IIS or an Insight uninstall issue.
UiPath Insights
from Sites.
UiPath Insights
and Provisioning
from Application Pools.
The following
applications should be closed before continuing the install: IIS Worker Process (Process Id:
6492 and Process Id: 8808)
This can be caused by w3wp.exe worker process that is
still running.
To solve this issue, open the console or PowerShell and run the following command and then click Retry in the error dialog to continue Insights uninstall.
net stop was /y
net start w3svc
net stop was /y
net start w3svc
If the above command is unsuccessful, you may need to restart the machine and rerun it.
- 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".
- Update the Looker Settings on the Insights Linux Machine.
If you performed the Insights installation, take the following steps to find the logs generated by the installer:
- Navigate to the
%temp%
or%temp%/<sessionID>
folder, where the<sessionID>
is the integer of the session you are in. Example:%temp%
or%temp%/2
. The name of the log file isMSI*****.log
, where the asterisks represent random letters. - You can find the Looker Installation logs in the
%programdata%
folder.If you have upgraded to the latest version, the Looker installation logs are still located in theC:\Users\UserName\_insights
folder. - You can find the Insights Portal logs and
Provision logs in Windows Event Viewer. Use the Filter Current Log option to filter by Event source.
looker-initialization.sh
on a Linux machine or by remotely running Deploy-Looker.ps1
from a Windows machine, the setup runs a system check to ensure the environment meets the requirements. During this system
check, the following error can occur:
The looker server requires at least 16G Memory.
Due to conversion from binary to decimal that may differ between cloud providers, this error can occur even if you have 16 GB memory.
ProcessingExceptionDetails
column in the dbo.QueueItem
and the HostMachineName
column in the dbo.JobEvents
table is altered. If you have a large dataset, this can cause a timeout during upgrade. To avoid this, use the following
script to manually index the items:
IF COL_LENGTH('[dbo].[QueueItems]', 'ProcessingExceptionDetails') IS NOT NULL
AND 'Nvarchar' IN (
SELECT DATA_TYPE FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'QUEUEITEMS'
AND TABLE_SCHEMA = 'DBO'
AND COLUMN_NAME = 'PROCESSINGEXCEPTIONDETAILS'
)
BEGIN
ALTER TABLE [dbo].[QueueItems]
ALTER COLUMN ProcessingExceptionDetails NVARCHAR(MAX)
END
IF COL_LENGTH('[dbo].[JobEvents]', 'HostMachineName') IS NOT NULL
AND 'Nvarchar' IN (
SELECT DATA_TYPE FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'JOBEVENTS'
AND TABLE_SCHEMA = 'DBO'
AND COLUMN_NAME = 'HOSTMACHINENAME'
)
BEGIN
ALTER TABLE [dbo].[JobEvents]
ALTER COLUMN HostMachineName NVARCHAR(MAX)
END
IF COL_LENGTH('[dbo].[QueueItems]', 'ProcessingExceptionDetails') IS NOT NULL
AND 'Nvarchar' IN (
SELECT DATA_TYPE FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'QUEUEITEMS'
AND TABLE_SCHEMA = 'DBO'
AND COLUMN_NAME = 'PROCESSINGEXCEPTIONDETAILS'
)
BEGIN
ALTER TABLE [dbo].[QueueItems]
ALTER COLUMN ProcessingExceptionDetails NVARCHAR(MAX)
END
IF COL_LENGTH('[dbo].[JobEvents]', 'HostMachineName') IS NOT NULL
AND 'Nvarchar' IN (
SELECT DATA_TYPE FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'JOBEVENTS'
AND TABLE_SCHEMA = 'DBO'
AND COLUMN_NAME = 'HOSTMACHINENAME'
)
BEGIN
ALTER TABLE [dbo].[JobEvents]
ALTER COLUMN HostMachineName NVARCHAR(MAX)
END
- Configuring Log Rules
- Certificate Errors
- Changing the Insights Language
- TLS Errors
- Connection Issues
- Portal Showing 500 Error After Installation
- World Wide Web Publishing Service (W3SVC) Does Not Start
- Database Migration Fails During Installation
- RobotLogs Index
- QueueItemEvents Index
- JobEvents Index
- Uninstall Issues
- Application Pool Not Removed
- Uninstall Error Caused by Worker Process
- Miscellaneous Issues
- Accessing Logs
- Insufficient Memory Error
- Issue
- Possible Cause
- Solution
- Upgrade Issues
- Dataset Migration Fails During Upgrade