UiPath Robot has stopped working

robot
p_qa

#41

I also have the same Robot fault. Here is the related log. Please help analyze the reason. Thank you.
Excel-crash-report.zip (174.7 KB)


#42

Hi, I am also facing same problem in process, which has been running without any problem (from 03/2018) until today. Has anyone solution? Thank you very much


#43

i´m also facing the same problems in soutions what already have months without error, but until around 6 days, i facing many problems with this

Log:

Application: UiPath.Executor.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()

uirobot version 2018.3.1


#44

Hi,
Did you find any solution yet?
We upgraded from 2018.1.3 to 2018.3.1 and trying to test it in UAT and we are facing this issue, randomly. Some runs are successful and some aren’t.

Application: UiPath.Executor.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._Application.set_SheetsInNewWorkbook(Int32)
at UiPath.Excel.WorkbookApplication.Dispose()
at UiPath.Excel.WorkbookApplication.Finalize()


#45

Hi Nautilus,
I have have the same exact scenario. The only difference is that we updated from 2018.1.3 to 2018.3.1. This is in production for 3 months now on 2018.1.3 and we are looking to update it to 2018.3.1 and started testing it out in dev and UAT windows servers and we are facing the same exact error 1 out of 10 times. Did you find out what the below error means?
“at UiPath.Excel.WorkbookApplication.Dispose()
at UiPath.Excel.WorkbookApplication.Finalize()”


#46

I went through with the process of creating a ticket and working with the support people to fix the issue.
We started by creating log messages after each activity to find out where it was exactly failing. The work flow was failing at random steps but all the steps were related to excel. When working with the support people all we did was find out where the issue appears. We tried putting some delays and close excel application activity before and after each excel activity. It worked all fine during the time with support. Almost 3 hrs.
But again the next day the process fails when running from start to finish. The issue was with excel activity again. SO here are couple of questions that I have…

  1. My process uses a lot of excel application scope activity.( It should open and close the excel application by itself when the activity executes). I still have close excel workbook just to close it in case. Issue is it is not closing the excel every time, any suggestions?
  2. My process opens and closes excel each time when it reads a row from the data table. is there a better way to design so the excel application is closed every single time it opens?
  3. I tried using delays and kill application but those are not the most efficient activity to use. I t can throw you a different error.
  4. When only running the excel part my process executes start to finish 100% every time, but when running the whole process it always fails at that particular excel part.
    Those who can relate please provide feedback.

#47

Hi sherpa,
Are you seeing the same error, in your event log. If so what is the excel package and uipath version are you using?
“at UiPath.Excel.WorkbookApplication.Dispose()
at UiPath.Excel.WorkbookApplication.Finalize()


#48

yes on my even viewer the error is the same as yours.


#49

If your excel package version is 2.4.6856.xxxxx, downgrade it to 2.3.6682.26635 and test it out.


#50

can you share me the link to downgrade?


#51

You can use manage packages in your studio.


#52

Thank you , will provide the feedback when the process runs tomorrow.


#53

Hello,

I am also struggling with what seems to be the very same issue. Event Viewer points at UiPath.Excel.WorkbookApplication.Dispose() and UiPath.Excel.WorkbookApplication.Finalize(), when the UiPath.Executor crashes. There seems to be no logic at when and why the crash happens. For example, I inserted more log message activities to find out what is going on, but that changed where in the process the crash actually happened.

I did what priyatham suggested and downgraded the Excel package from (the newest) v2.4.6863.30657 to the latest 2.3, v2.3.6682.26635. And just like that, all problems went away. This would suggest there is something fundamentally wrong with the latest version of the package.


#54

Did you find out what the below error means?

No I did not find anything specific related to those lines.

If your excel package version is 2.4.6856.xxxxx, downgrade it to 2.3.6682.26635 and test it out.

I did what priyatham suggested and downgraded the Excel package from (the newest) v2.4.6863.30657 to the latest 2.3, v2.3.6682.26635. And just like that, all problems went away. This would suggest there is something fundamentally wrong with the latest version of the package.

Very interesting find. We are currently using 2.4.6856.17931 in the affected automation and have been able to get rid of the error by eliminating nested methods as mentioned before. But I definitely agree this should not be happening in the first place and did not happen before. I guess I cannot find out anymore whether the Excel activities package was updated around that time (10.10.) when we started seeing this?


#55

exactly my problems gone with the downgrade


#56

i dont have any nested methods and fail, the only solution was downgrade the package


#57

my issue also got fixed with the downgrade


#58

I try to do the downgrade, but uipath can’t find the excel activities, but, i executed the program on other machine (without downgrade) and works fine,