Excel Application scope stopped working abruptly

excel
activities

#1

Scenario: Use excel application scope , read range/write range activity

Steps to reproduce: Create a dummy excel with some data. Use excel application scop activity and provide the path of the excel. Use read range activity to read the data from excel.

Current Behavior: The bot hangs on reaching the excel application scope activity.No error is thrown,nor does the bot stops.It needs to be manually stopped. The excel application scope was working as expected until few minutes back and stopped working when tried running later. Is this due to some security patch of excel?

Expected Behavior:The excel application activity should go through as expected.

Studio/Robot/Orchestrator Version:2016.2.6344

Last stable behavior:
Last stable version:
OS Version:
Others if Relevant: (workflow, logs, .net version, service pack, etc):


#2

Hi @sucnayak

Could you please check if there is any update for the Excel package? Manage packages -> Update


#3

Hi,
How about “Read Range” activity under workbook tab.

readrange


#4

I am also facing same issue. I have to open at least 20 excel files one by one. But unfortunately, uipath stops working during read-range activity with error message “Uipath robot has stopped working”. Can somebody help me in this.


#5

Hi,

Facing the same issue while trying to read Excel file using Read range activity in Excel application Scope. It was working fine before; before some days back it started giving error as ‘Uipath robot has stopped working abruptly’. Sometime it’s working but getting error once in a while.
Excel activity that currently in use : 2.0.6479.13204

Anything related to Excel Activity package ?


#6

Please try with below methods to resolve bot crashing issue:

  1. Do not keep multiple Excel scopes in single workflow where all the excels are reading huge amount of data . It crashes because of memory which can be seen in Event viewer as well
  2. Keep these excel scopes in separate workflow and check in “Isolated” property of all the workflows
  3. Check if any data table arguments is not used both as “In\Out” direction. It should be either used as “In” or “Out” at a time

Check all of above three. It should work.


#7

Can you provide any reason for your suggestions?