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.
When modifying or repairing your Insights installation, note that if using a non-standard SQL instance compared to the original installation, you must:
- On your Insights machine, open the
This file can be found in the
- Add a second forward slash (
\) in the JDBC connection string between the server and instance. For example:
- Save your changes to the
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.
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:
- Navigate to
C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrostand open the 'uipath_insights.properties' file.
- Find the 'insights.db.conn' property, and check to that the hostname and port are separated by a colon.
If they are not, replace the separator with a ":".
Updated about a year ago
|Insights Portal Troubleshooting|