Orchestrator 2020.4.3 - Error 407 - We schedule cases in a job, no job which requires a queue has completed successfully in the past number of weeks, but some cases within the job have completed

Help Orchestrator
,
1

Hello,

I am hoping to try and leverage the knowledge of the broader UiPath community.

We have a pilot instance of UiPath in operation in production, however we have no one currently who is familiar with the tooling as the resource responsible departed last year. Our instance has been running without issue for the past two years, until late May 2023.

Since then, we have been unable to utilise our robot. A consistent 407 issue (details at end) occurs on Orchestrator when updating a work item job details. We schedule cases in a job, no job which requires a queue has completed successfully in the past number of weeks, but some cases within the job have completed. The error always occurs but the time interval it is encountered is unpredictable ranging from 4 minutes to 20 minutes.

Prior to the issue, the Robot was executing jobs without issues. There was no configuration changes to Orchestrator or the Robot prior to the issue. The only recent change in the environment was the deployment of Microsoft security updates from the May release to both Windows Server 2016 and Windows 10. Previous Microsoft security updates were deployed without issue.

We have a simple set up here with 1 robot on a Windows 10 VM, 1 App server and 1 Database server both hosted on their own vm on Windows Server 2016. We are using an older version of Orchestrator 2020.4.3

Todate, we have reviewed event logs and updated the proxy settings. There have been no improvements.

We have also noticed a new need to manually reset IIS nearly daily.

If anyone has experienced a similar issue and resolved it, can you please share your steps

Many thanks

Ray

Error message being logged

UiPath.Service.UserHost 20.10.7.0
System.UnauthorizedAccessException: Access to resource is denied: An error occurred while sending the request. —> System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)

2

Hello @Ray0307, try something along these lines:

1. Proxy Configuration: Ensure that the proxy settings on the machine where UiPath Orchestrator is running are correctly configured. Check if the proxy settings have changed recently or if there are any restrictions on outbound traffic.
2. Windows Firewall: Review the Windows Firewall settings to make sure that it’s not blocking outgoing connections from UiPath Orchestrator or the Robot.
3. IIS Reset: Manually resetting IIS daily might be an indicator of an underlying issue. Investigate why this is necessary. It could be related to application pool recycling, which can sometimes clear cached credentials.
4. Robot User Permissions: Check if the user account running the UiPath Robot service has the necessary permissions to access external resources and the internet, including any proxy authentication required.
5. Update Orchestrator: You mentioned that you’re using an older version of Orchestrator (2020.4.3). Consider upgrading to a more recent version, as newer versions often include bug fixes and improvements.
6. Review Logs: Continue reviewing the logs, especially Orchestrator logs, for any additional error messages or clues about the issue.
7. Proxy Authentication: If your organization uses a proxy server, make sure that the proxy authentication settings (username and password) are correctly configured in UiPath Orchestrator. This information can usually be set in the Orchestrator settings.
8. Network Changes: Investigate if there have been any recent network changes or security policies that might be affecting outbound connections from your environment.
9. Test from Different Machine: If possible, try running the same process on a different machine to see if the issue persists. This can help determine if the problem is specific to the Orchestrator server.
10. Contact UiPath Support: If the issue persists after trying the above steps, consider reaching out to UiPath Support. They can provide specific guidance and assistance for your version of Orchestrator and environment.

Cheers! :slight_smile:

3

Many Thanks Rodrigo for the detailed and very helpful reply

4

If it solved you problem please select the answer as solution so the topic gets closed.

Very happy to help, cheers! :slight_smile: