You can use the Orchestrator license if its a mandatory field in Zendesk.
Thanks Gabriel! I cant see any license number in the orchestrator. But, I can see an Orchestrator API key, which looks similar to a license code. Can I use this?
No, API key is something different. You should
Have the key on an email from UiPath i think.
Okay I see. I will check with my lead and create the ticket accordingly. Thanks for your help Gabriel!
Hi All,
I’m also facing the same problem with my BOTs. UiPath.Executor has stopped working error. I can’t see any resolution above. Any one has any idea?
Was there ever a solution to this issue posted?
It’s a generic error. Just from the message we cannot figure out what’s the cause, so could you please tell us what’s your case?
- the error pops when running a project from Studio
- the error pops when running a project from Robot
- what is the installer you have: exe or msi?
- what’s the Studio/Robot version?
- can you provide the logs in Event viewer?
This information can help us figure out what’s going on.
I am facing a similar issue with uipath robot not working. I have a process that works with multiple excel,i had the process in production for 6 months now and since last couple of days I am facing this issue. I have gone back to my code and made several changes in the code but the error still persist.
I have looked at forums and the recommended solution but the error still exist.
To answer couple of your questions above
- the error pop up when running from studio, tray or orchestrator.
- we have the msi version
- robot version is 2018.1.1
Please suggest. @Gabriel_Tatu @ovi
Hmm, this seems somewhat similar to what we started experiencing at the end of last week. A process that worked ok until that point started suddenly giving “Robot has stopped working” errors in seemingly random fashion. Excel is used in this process to modify a workbook (delete a few rows, then save it as tab-delimeted text file), but the error happens when robot tries to load a file into SAP. So Excel is not in use at this point anymore. However, looking at the error message in event viewer I can see:
Application: UiRobot.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidCastException at System.StubHelpers.StubHelpers.GetCOMIPFromRCW(System.Object, IntPtr, IntPtr ByRef, Boolean ByRef) at Microsoft.Office.Interop.Excel.ApplicationClass.set_SheetsInNewWorkbook(Int32) at UiPath.Excel.WorkbookApplication.Dispose() at UiPath.Excel.WorkbookApplication.Finalize()
Which to me suggest it is somehow related to Excel. Also this error message comes up always at the same time:
Faulting application name: UiRobot.exe, version: 18.1.3.0, time stamp: 0x5ab8e91b
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18938, time stamp: 0x5a7dd8a7
Exception code: 0xe0434352
Fault offset: 0x00015ef8
Faulting process id: 0x31e0
Faulting application start time: 0x01d4660aee50c7e9
Faulting application path: C:\Program Files (x86)\UiPath\Studio\UiRobot.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: fd4d8682-d1ff-11e8-80f1-0050569b3c4d
Faulting package full name:
Faulting package-relative application ID:
We are typically able to process several files before the error happens. It is usually 10th file or so that might give the “robot has stopped working error”. Any help in solving the issue would be appreciated.
- the error pops up when running from studio, tray or orchestrator (we have 3 robots per server in HD environment, Win Server 2012).
- we have the msi version
- robot version is 2018.1.3
- no changes in environment when started (to our knowledge at least), problems started already last week, there was windows patching done on weekend though.
- no heavy log message or write line activities in the workflow (well, depends what is meant with “heavy” - only what we regard as normal logging, one line here and another there)
Is the job running from Orchestrator? RDP or Login to Console?
Can you monitor the memory and CPU of the uirobot service and executor process?
How ofted does this issue appear?
We have tested it by running from the Studio, form the system tray (on robot server) and from Orchestrator. In each case the error can happen, in both the development and production environment. We are using the “login to console = false” as we have a HD server.
I could monitor memory and CPU by looking at the keep task manager / resource monitor while running the process, but haven’t done that yet. If I look at the server level performance logs (Nagios), the memory usage has been quite stable, CPU has some spikes but not correlating at least 1:1 with the issues.
First time this appears was on 10.10. and now there are 50+ occurences, here’s from today from our dev server where we have been running this quite frequently throughout the day:
first of all we need to narrow down what causes the crash - if its a specific workflow/activity etc
did you raise a ticket on our support platform?
I was with the support team yesterday for 2 hrs. We could not figure out why uipath shows the .net framework version v4.0.030319 when my .net framework has the v4.7.
Reason I say this because the minimum requirement for uipath .net framework is v4.5.
I disabled a lot of kill activities and disable activities from my workflow.
Using constructive logs to identify where the bot stopped helped.
But the issue still persist with .NET FRAMEWORK version.
first of all we need to narrow down what causes the crash - if its a specific workflow/activity etc
did you raise a ticket on our support platform?
Yes we created a ticket. This error was related to one automation and could happen in two places in it (in both places we are uploading a file to SAP). Thanks to detailed logging we knew those places exactly. What we found strange was that the event log error messages were pointing out to something related to Excel which was not in use at the point of the crash.
With regards to the ticket we created, unfortunately technical support was not able to give any detailed assistance as it seemed to be related to the automation, not the platform. They just gave some pointers on debugging and what could perhaps cause the issue.
Yesterday we did some more googling and found out that “Exception code: 0xe0434352” relates to StackOverflowException Class (StackOverflowException Class (System) | Microsoft Learn) and started reorganizing activities inside one of the workflows with most Excel activities. There seems to have been too many nested methods in use there and after restructuring the workflow, we have been able to run the whole automation without errors since yesterday evening.
What we still find strange is what “tipped the boat over” as it was working until 10.10. when we first encountered the error and cannot point to any specific change that would’ve been implemented to the automation at that point. To us it seems it just started out of blue…
In any case - I think we can now say we found the root cause and have been able to overcome the error
But the issue still persist with .NET FRAMEWORK version.
In the event log I can also see these lines:
Application: UiRobot.exe
Framework Version: v4.0.30319
But I guess that refer to some other Framework than .NET Framework? Our installed .NET Framework version is 4.7.1.
its just a bad reporting issue for the version number
We have been seeing this as well the last few days with a process that was running without exception.
What do you mean by too many nested methods? Too many activities nested within one another?
We’re running the same UiRobot 2018.1.3, but our .Net Framework is v4.6.2
I also have the same problem. How did you solve it? Thank you very much.
应用程序: UiPath.Executor.exe
Framework 版本: v4.0.30319
说明: 由于未经处理的异常,进程终止。
异常信息: System.InvalidCastException
堆栈:
在 System.StubHelpers.StubHelpers.GetCOMIPFromRCW(System.Object, IntPtr, IntPtr ByRef, Boolean ByRef)
在 Microsoft.Office.Interop.Excel.ApplicationClass.set_SheetsInNewWorkbook(Int32)
在 UiPath.Excel.WorkbookApplication.Dispose()
在 UiPath.Excel.WorkbookApplication.Finalize()
With nested methods I mean for example manipulating a variable with many methods within the same activity (methods like toString, Replace etc.). This seemed to be the root cause for the problem in our case. After separating them, we have not received the error anymore.