I encountered an issue during launch of an updated process from the orchestrator. Before the launch, the process package installation takes longer than 20 minutes and fails with a timeout error. Previously, processes updated without issues and on other servers or under different users they still update normally.
During troubleshooting, I found that the folder for the new version of the process was created, but its access permissions are broken. The account, where the package installs, does not have access to this folder. I haven’t found any changes on the server or in the account settings.
Are there any solutions to this? Is there a way to check the orchestrator logs where the actions during process package installation are recorded?
if you are checking in the folder of the account you are running this process from? Whenever package needs to be installed , it automatically gets installed under c:/users/username/.nugget/packages so installing user would always have access to the folder.
have you tried to update the version of the package manually on that machine, then try running the process?
to access logs, if you open your file explorer and type “% **%localappdata%\UiPath\Logs**% it will take you to folder where logs are stored.
check the robot logs in C:\ProgramData\UiPath\Logs for detailed error messages. Verify that the robot is properly connected to Orchestrator without network issues. If needed, adjust the timeout settings in Orchestrator to allow more time for the process. Ensure the server has sufficient CPU and memory resources for smooth execution. Finally, restart the UiPath Robot service and, if the problem persists, consider reinstalling the UiPath Robot.
If you found helpful, feel free to tick as a solution.
Happy Automation
Yes, during the package installation a folder for the new version is created, but it has access issue for the robot account (which is running the process)
Manual update with the UiPath Assistant also falls with timeout error.
Yes, I checked this folder, but there are no any logs for the package installation. Maybe there are suitable logs on a orchestrator server, but we didn’t find path to them
Look for Orchestrator logs at C:\ProgramData\UiPath\Orchestrator\Logs.
Increase timeout settings in the UiRobot.exe.config file at C:\Program Files (x86)\UiPath\Studio.
Run UiPath Assistant/Studio with administrator rights.
If needed, reinstall UiPath Robot to resolve permission issues.
Does this happen for only this process or any other process also?
Has it never been launched since the package update or it works intermittently?
could you have a look at the windows temp folder on that machine and clear it?
Is there an enough space available in your C:/ drive to install and run the package?
which version of studio you are using? Is it enterprise or cloud version?
We had also faced timeout during process launch multiple times and request was raised to UiPath as well where UiPath had suggested us to switch to 24.10.6 version. Another solution that worked for us were points 3) and 4) mentioned above. In most of the cases, we found out that machine had very less space left in C:/ drive so we had to clear up the temp folder and delete other unnecessary files. And timeout issue got resolved for us.
Additionally, try to install the package manually, follow below thread.