Insights Admin Tool Fails With Error " Failed to setup RobotLogs table"

How to resolve when Insights Admin tool fails with: Error Failed to setup RobotLogs table ?

Resolution

  1. The error message for this issue can be found in the Uipath Insights Admin tool that is generated in the same folder as the tool. In order for the log to be generated, the tool needs to be ran as an Administrator
  2. The most common cause of this error is that Windows Auth is being used and the following services are running as LocalSystem:
    • Sisense.CLRConnectorsContainer
    • Sisense.JVMConnecotrsContainer
  3. To check which user these services are running as, go to services.msc and search for them. (look under the Log On As field).
  4. To check if Windows Authentication is being used, check the connection string for the Insights DB in the UiPath.InsightsAdminTool.exe.config file in the same directory as the Admin tool.
    • The DB connection string shall have 'WindowsAuth=True'
  5. If Windows Authentication is being used, then a service account with Windows Auth needs to be used to run the services.
    • For changing the user running the account, see more at Windows Authentication Configuration
    • Alternatively, LocalSystem can be given access to the SQL database by adding the user <domain name>\<computer name>$ - where the computer name is the Insights machine - to the SQL DB.
  6. If the issue is not with Windows Authentication, check the following log:
    • %programdata%\Sisense\DataConnectors\DotNetContainer\Logs\connectors.log
    • The log message should contain an error message that pertains to the issue.
  7. If no log is present, then that most likely means the service is not started.
    • Go to Services.msc and make sure that Sisense.CLRConnectorsContainer is running.
    • If the service is running but there are no logs, that usually means the service account user is not 'LocalSystem' and that the user who is running the process is not an admin account. If this is the case add the user to the local admin group.
  8. If the issue still occurs, open a ticket with UiPath and share the following:
    1. C:\Program Files (x86)\UiPath\Orchestrator\Tools\UiPath.InsightsAdminTool.exe.config
    2. C:\Program Files (x86)\UiPath\Orchestrator\Tools\log.txt
    3. Everything in %programdata%\Sisense\DataConnectors\DotNetContainer\Logs\
  9. Typically when a failure is still occuring, the next step is to capture the failure with a fiddler trace. Since the failure occurs when the UiPath Insights Admin tool makes an API call to Insights, the captured request can provide more information.