The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

Help
1

exception source: UiPath.Excel
exception stack trace: at UiPath.Excel.WorkbookApplication.Initialize(WorkbookArguments args)

at UiPath.Excel.WorkbookApplication.Initialize(Application excelApp, WorkbookArguments args)

at UiPath.Excel.Activities.ExcelApplicationScope.Execute(NativeActivityContext context)

at System.Activities.NativeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)

at System.Activities.ActivityInstance.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

Does anyone has any idea why this is happening?
Only happens occassionally.

2 Likes
2

Hi @inyourgravity,
Can you send the screenshot of the your code and exception message, so that I ll guide you

Regards,
Arivu :slight_smile:

3

excel%20cct
excel%20cct932×746 33.9 KB

I had a kill excel process before excel application scope cause we have had issues with excel not writing into range when file is in use (by robot previous excel application scope)

4

Hi @inyourgravity,

Don’t use workbook write range activity, use excel write range activity, then it will not through this error.

Inside excel application scope you must use the excel activities

Regards,
Arivu :slight_smile:

5

That was not the workbook write range, that was the excel write range.

6

Hi @inyourgravity,

can you send the xaml file so that i will check and update you.

Regards,
Arivu :slight_smile:

7

Hello,

I have encountered the same error after updating Excel package to newest version (2.7.2).
This error appeared at Excel Application Scope activity and it’s strange that sometimes it works, sometimes throws this error.

The solution in my case:
1.Surround the Excel Application Scope with a Try Catch.
2.In Catch: Kill EXCEL process and after that continue with the same Excel Application Scope from above.

Cheers,
Vlad

1 Like
8

well good idea

9

I am also facing the same , can anyone tell what is the reason for having this, as i can’t go with the solution as we manipulating the excel multiple times we don’t know at which point it is failed and we don’t want to start it from scratch again.

10

I am also facing this issue. Does someone find any concrete solution to this problem?