Hi, I have spent the last couple of days trying to make community edition (18.1.3) work to no avail. The fundamentally issue is, after installing, I have no uirobot service visible in services.msc. I have tried to:
Install on two different machines (windows 10) to check if there any peculiar config issues – same problem on both machines
Use both ‘logged on user’ with local admin rights and evaluated rights to install – same result
I can run UiRobot.exe (as logged on user or with elevated rights) which gives a tray icon but fails to connect to the non-existent service. This makes sense since no service has been installed
@Doug please open folder “Uipath studio” if uipath was updated from previous versions Under " Uipath Studio" folder u will see version installed on your system open the latest version folder, you will find robot file run it once afterwards you can find robot in “Icons tray”
I have found the file …\AppData\Local\UiPath\app-18.1.3\UiRobot.exe - is this what you mean by “robot file”. If I run this the tray icon will appear but after about 5-10 seconds goes red and reports that it can’t find the UiPath Service.
I have only installed the community edition. All the symptoms I have recounted thus far relate to community.
So, I am correct in understanding that, if I install the community edition, there is no service? If so, when I run the tray app and it says “Error connecting to the UiRobot Services” this is by design?
OK, so if this is the case, when a workflow is executed from Studio the process is created? If I try running from studio it fails with:
14:05:12:819 => [ERROR] [UiPath.Workflow.Logging.StudioTraceListener]  System.AggregateException: One or more errors occurred. —> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/UiPath/service/duplex/agent/xxx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/UiPath/service/duplex/agent/xxx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.