Hi,
Yes, I did and uninstall it. I will read through the post you linked.
Thx!
Hi @loginerror,
So I did all steps like described in the post and still have the same issue 
Pls note this is only problem when robot service UiPath.Service.Host is installed and robot disconnected from Orchestrator.
Normally the issue is fixed by clearing the licensing folders here and here:
%userprofile%\AppData\Local\UiPath\License
%userprofile%\AppData\Local\UiPath\LicenseInternal
And then re-activating your Studio. It is strange that it would persist after full fresh installation though.
Did you have to re-register your Studio upon reinstallation?
Yes, I did re-register. It seems the UiPath.Service.Host service is not taking the same license…
Could you try clearing this folder here:
C:\ProgramData\UiPath\License
Hi,
I did but it did not help neither
But maybe I found the root case (but not yet workarround)
When the UiPath.Service.Host service is installed it is running under LocalSystem account.
The path to folders with license files is %userprofile%\AppData\Local\UiPath
Given that LocalSystem and actual user (e.g. robot007) will have a different %userprofile%\AppData\Local\UiPath means that UiPath.Service.Host service (running under LocalSystem) can not read license in profile of “robot007”
I changed the UiPath.Service.Host service to run under “robot007” and the message “To execute processes, please activate a license.” 
But I get another error: RemoteException wrapping System.Exception: Could not start executor. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
I believe this page might make it more clear:
Basically, for Community Edition it is always the User Mode Robot Service. The issue you are having is common whenever the two installers (Community and Enterprise) were once installed on one machine. This would result in two services (machine-wide and user-mode one) ‘colliding’ and thus causing unexpected behaviour.
I would definitely try again with the fresh install, removing all the files and then restarting the machine both after uninstall and after the fresh installation was completed (just to be sure all services are properly started).
One other cause of this issue can be an auto-update feature. During auto-update to the latest version, it can be that the user Robot service will get stuck on the older version while Studio is already running on the latest one. Typically a computer restart after the auto-update process will also fix this issue.
I suppose yet another cause would be if Studio cannot contact the licensing service while it is disconnected from Orchestrator.
I hope one of these ideas can help you with the solution here.
Thx for explanation. That means Community Edition can not coexist with UiPath.Service.Host service and therefore can not be used for Unattended Execution, right?
Not without some manual tweaks. When @Pablito is back from holidays, I’m sure he’ll be happy to provide you with some insights on how to get it to work with some powershell magic.
Basically, it is possible to create a machine-wide service using the Community Edition files, but it is not officially supported way due to several constraints (it can’t auto-update, if I were to list one, so you will need to manually run the script every time your Studio updates).
1 Like
I found quite simple solution:
1/ Change “license.config” file to store license in a “neutral” place where “user” and LocalSystem can reach it, e.g.
C:\Users\All Users\UiPath\License
C:\Users\All Users\UiPath\License
This needs to change in two places:
C:\Users<user>\AppData\Local\UiPath\app-
C:\Users<user>\AppData\Local\UiPath\app-\UiPath
2/ Install “UiPath Robot Service” service
run “UiPath.Service.Host.exe install”
note: Make sure that “UiPath.Service.UserHost” service is not running
3/ Activate trial license
run “regutil.exe activate /email=your@email.com”
4/ Restart “UiPath Robot Service”
Anil_G
Shakib
ashokkarale
sharu_priya
sven.wullum1
Babjee.Vangipurapu
Prathamesh_Trimurti_Hulav
riley
sharazkm32
A_Learner