I am having issues with a specific workflow/.xaml file whereby the robot will crash at a specific sequence within the workflow. This only occurs on some occasions when running the workflow (other times it runs completely fine), and there seems to be no pattern as to whether the robot crashes or the workflow completes.
I have attached a screenshot of the error below- Selecting ‘debug the program’ brings up an error message within UiPath stating “Job ‘Name of Workflow’- stopped due to unexpected process termination!”. Exception type- exception. The error does not seem to appear in logs.
Update I’ve now found that the point at which the workflow sometimes crashes is when attempting to ‘read range’ for a sheet within an excel file- the excel file opens fine (I have visible set on the application scope) but the robot crashes when then trying to read the sheet range.
I was having the similar issue with OCR and Read/Write to excel(high volume), the robot used to crash sporadically. I moved these activities to a separate workflow and the issue seems to have resolved.
A good test here would be to create a separate Test Workflow and see if you still get errors. If so then you know it’s the spread sheet causing the problem else it’s other factors.
From what I can see the issue only occurs when I try to read a selective range within the Spreadsheet (e.g. A:T). When I read range setting ‘A1’ as the range- it reads the entire spreadsheet without issue. I’ve then used Datatable activities to get my selective range and this works fine.
I think that potentially when reading the selective range in the spreadsheet, UiPath is populating the datatable with far more rows than are actually populated in the excel. Moving the read range to its own workflow and using the selective range also crashed the roboot.
Has there been any resolutions to Read Range causing UiPath to crash? I’m helping a colleague who is experiencing the issue. Excel file is 1066 rows long with many empty rows. It works if we refine the range to only a few columns but if we choose too many or entire spreadsheet it crashes.
@richarddenton
I guess this problem was with excel application scope previous package versions to read some of blank rows it was failing but read range for workbook. It was working.Now a days its works fine.
It’s doing it with both Read Range in Scope and outside of scope. Also, the rows weren’t completely blank, but it did it even with the blank rows. I also tried Clearing the Content of all the cells outside of the data. The crashing didn’t happen on a smaller excel file.
I have only seen this problem now since we just updated to 2016.2.6379 which was needed to resolve an issue with Orchestrator RDP. Maybe the 6393 fixes it? Our link to install Studio did not give us that version though.
There is also another problem with Write Range now where it says Range does not exist that never was there before.
I have also tried rolling back the Excel package to an older version with no success.
Surely, we aren’t the only ones experiencing some of these critical bot-breaking issues, lol.
I guess we will create another ticket with support next week.
Older version of Excel Activies I copied from a machine not being used for development at the moment.
UiPath.Excel.Activities.2.0.6361.22986
Newest version that was being used when the problem started coming up:
UiPath.Excel.Activities.2.0.6382.14545
To me, it seems like it’s related to the Studio update, not the Activity package.
I think I would need to ask the owner permission to send the Excel file since it’s not my file. I might try and duplicate the issue with another file of similar size. It’s the weekend though and so I might not get to to doing that til next week
I’m having the same issue, reading a xlsx file with 300 000 rows in it. Robot Crashes in a few seconds.
The file is quite big, even when I open it manually it takes a while to load.