Insights installation error (Sisense.CLRConnectorsContainer Window service not starting)

We have run the Insights installation successfully. However, we are not able to start the Sisense.CLRConnectorsContainer Window service.

We are using Windows authentication for SQL server and have updated the Log-On properties in the Windows service accordingly.

What could be issue?
Where can we find the logs to debug this issue?

Hello @sam_arc!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

Hey @sam_arc, unfortunately from your screenshots I can’t tell what version of Insights and Orchestrator you have, but your first and best bet is always to go through our prerequisites and make sure you’ve met them all, as well as review our troubleshooting guide. from what we’ve seen, the majority of issues with enablement are because one of the requirements wasn’t met. You can find instructions about how to get the logs on the troubleshooting page

The version we are using is 2020.4.3.

This issue is resolved. It seems that Windows services not starting as it was getting timed out.

We set the ServicesPipeTimeout registry entry to fix the issue


Name: ServicesPipeTimeout
Data: 18000 (milliseconds)