TLS Configuration

If the machines where Insights and Orchestrator are being installed are using different TLS configurations, the Insights installation fails. Ensure that both machines are using the same TLS configuration, with TLS 1.2 being recommended.

Repair Installation using New SQL Instance

When modifying or repairing your Insights installation, note that if using a non-standard SQL instance compared to the original installation, you must:

1. On your Insights machine, open the uipath_insights.properties file.

📘

Note:

This file can be found in the C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\ directory.

2. Add a second forward slash (\) in the JDBC connection string between the server and instance. For example: insights.db.conn=jdbc:sqlserver://insightsval\\dev01;Database=insightsval;integratedSecurity=true;.
3. Save your changes to the uipath_insights.properties file.

Deployments using languages that contain non-ascii characters

Multiple issues have been linked to localization issues in languages containing non-ascii characters. For full localization support, please upgrade to the 20.10 Insights release.

Connector Errors

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

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