Excel Application Scope Crash

Help
, ,
1

Hi,
During my Workflow i have a Excel Application Scope activity that wont work even though the excel spreadsheet exists and works in the workflow prior to the stage in the workflow where it crashes.

Any Suggestions?

Thanks,
Shawn

2

What is the error you are getting?

1 Like
3

Yes show us the error so we can understand better

1 Like
4

@ecarles @parasmanichauhan
Please check this
image

image
image454×592 11.5 KB

Detailed Log:

18.4.3+Branch.master.Sha.9888b477be8d3ec8a832306fc59c34ba6edad108

Source: Excel Application Scope

Message: Exception from HRESULT: 0x800A03EC

Exception Type: UiPath.Excel.ExcelException

An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
UiPath.Excel.ExcelException: Exception from HRESULT: 0x800A03EC ----> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800A03EC
at Microsoft.Office.Interop.Excel.Workbooks.Open(String Filename, Object UpdateLinks, Object ReadOnly, Object Format, Object Password, Object WriteResPassword, Object IgnoreReadOnlyRecommended, Object Origin, Object Delimiter, Object Editable, Object Notify, Object Converter, Object AddToMru, Object Local, Object CorruptLoad)
at UiPath.Excel.WorkbookApplication.InitializeCurrentWorkbook(WorkbookArguments workbookArguments, Workbooks workbooks)
at UiPath.Excel.WorkbookApplication.Initialize(WorkbookArguments args)
— End of inner ExceptionDetail stack trace —
at UiPath.Executor.WorkflowRunner.EndExecute(IAsyncResult result) in D:\a\1\s\Robot\UiPath.Executor\WorkflowRuntime.cs:line 208
at UiPath.Core.Activities.InvokeWorkflowFile.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

Thanks,
Shawn

5

@parasmanichauhan @ecarles Please see response

6

@shawnmurray - I am ain’t too sure of this error but I got this once when the excel was open …can you check the excel program is closed? Also, can you try renaming your filename (without spaces) ? Let me know if this solves.

1 Like
7

@parasmanichauhan I will check that it is not running in the background or something.

If i run this activity on its own regardless of the workflow it works fine so i am unsure.

cheers

8

Hi @shawnmurray

Are you processing the same Excel file just before this activity that throws the exception?

I have seen some reports on the Forum that killing the Excel process just before the Excel scope that causes the error should help here.
Additionally, you could try delaying this error prone Excel scope until the previous action is saved.

Could you also provide us with all the information about your environment:

  • Studio version
  • Excel activity package version
  • Windows version
  • Excel version
1 Like
10

Studio Version: 2018.4.3

Excel Activity version: 2.5.2

Windows Version: Windows 10 Pro 64-bit

Excel Version: Excel 16

@loginerror

11

One thing to try would be to try with the latest Excel 2.6.3 first to see if it changes anything in the behaviuor.

12

I typically get this when the excel workbook is open - or if another user has the excel file open

13

Hi @gconn

What do you mean by “excel workbook is open”?

Typically Excel Application Scope should ‘take over’ that open Excel and work on it. Is it maybe open in a Read Only mode or with some other non-standard message? Does it happen to all the files, or maybe only ones that are password protected?

For example, if you were to replace the Excel file in your problematic sequence with a new one that you have just created and saved on your desktop, would it simply start to work?

1 Like
14

Hi,

This is still an issue.

Excel seems to be staying open in the background.

Any ideas how to resolve this?

Thanks
Shawn

15

Hi @shawnmurray

To have a better look at the issue, please contact our technical support to have a look here:

1 Like