When I run to open excel file I get this message:
Main has thrown an exception
Message: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
Source: Excel application scope
Exception type: ExcelException.
Can anyone provide me an explanation and what I should do?
Br
Angelos
In addition, please check if your excel file is not corrupted or something. You may check it by simple trying to open it with Excel and if it doesn’t show any error message, then it means that your excel file is ok and the problem is related to UiPath.
I am also having this problem after I have updated the excel activities from package manager.
The excel is not corrupted it is in the format .xls.
I have used excel scope several times for reading and writting.
It sometimes works fine.
Also I am calling a macro and my input file is .xlsm.
Excel package version: 2.0.6526.16321
MS Office: 2010
File format used: .xlsm and .xls
Please refer to the link like below, although is write in Chinese.
Some days before, I installed a software “PDFelement 6 Pro”, it changed the default setting of Excel.
Maybe it caused the exception like 「HRESULT: 0x800706BE」
I also get this error sometimes when I run the process from the orchestrator. Some internal code fails somehow… I think it’s totally independent from the robot, since 2 minutes after getting this error, it was successful again. (Nothing was changed in the code.) UiPath needs to fix this.
invoke vba activity used to work fine until last week, now it cannot run the same macro code it used to run. neither the code nor the excel file used was changed.
it seems like there are many topics opened for the same issue such as the one below;
or this one;
but the solutions suggested didn’t help.
can anyone help solve the issue? what could be the reason for this error?
I was able to overcome this issue by breaking the macro code into two separate parts; I use invoke vba activity twice now. I have only made minor change in the code.
No issues left, thanks for the response
(But I can still share a simplified & sample project if desired.)
I suppose the ideal way to tackle it would be to find the minimum VB code that breaks it when run at once but works when split. This might indicate a bug to be fixed in the activity itself, but that would need to be checked by our team.
If you feel like it, please attach a dummy project with a broken and a working solution. I will create a ticket for our team to investigate