Hi Guys
We are receiving underlying connection was closed. An unexpected error occurred in send when trying to access the asset while running it through orchestrator.
This process runs pretty fine most of the days , however we have recently received this kinda error
regards
Vishnuvarthan
HareeshMR
(Hareesh Madasi)
October 17, 2019, 3:04pm
2
Please check whether the robot is connected to the machine or not in the system tray @vishnuvarthanp
yes Hareesh , the robot is connected to machine
HareeshMR
(Hareesh Madasi)
October 18, 2019, 5:19am
4
Can you try to reconnect the machine once , here are the steps that needed few changes as the orchestrator has lot of changes in the new release
New requirements for Robot to Orchestrator connection!
Since latest update of Community Orchestrator please be careful when connecting Robot to Orchestrator.
Now you need to provide full address like:
https://platform.uipath.com/[AccountName]/[ServiceName]
Before you needed to add just:
https://platform.uipath.com/
You may find the full address in the address bar when you are on Orchestrator Tenant page. Without providing the full address in this form you will get this error:
[imag…
Hi Hareesh
this is happening in production environment. we are using orchestrator version 18.4.4
Hi, am having the same issue, did you manage to solve it?
postwick
(Paul Ostwick)
December 9, 2021, 6:29pm
7
Check how many rows are in your UiPath database Log table. This table gets huge fast and causes performance issues.
Thanks we will check soon… do you have any idea how many rows until this error could happen?
postwick
(Paul Ostwick)
December 10, 2021, 2:07pm
9
No, it depends on your database server etc.
We had lots of problems that didn’t seem like they should be related to the Log table being huge, then we initiated regular maintenance to archive older rows and the problems went away.
Huge thanks for your insight, will definitely try it out and see how it goes.