A workflow I was working on suddenly started outputting this bug:
Excel Application Scope: Error HRESULT E_FAIL has been returned from a call to a COM component.
I looked around on the forums and I found many others with this issue, but only regarding Chrome not excel.
The 3.5 fixes I found in those articles were:
1 Use IE instead of Chrome
2 Uninstall UiPath Studio and Reinstall
3 Uninstall and reinstall .NET Framework 4.6 (Most agreed this as a fix)
3.5 Did you type your Path correctly
I tried all solutions to no avail and even uninstalled and reinstalled UiPath excel activities along with some PC restarts after uninstall and reinstall.
Using Excel and even on a fresh workflow and a Hardcoded filepath (not typed but selected from desktop) the error persisted across all excel files
Has anyone encountered this issue? This is halting a bot from going into production I appreciate any help.
No workflow to share, The error is not workflow specific as even a fresh workflow with just an excel app scope yields the same error.
I donāt know what causes this error, but a work around seems to be to add a delay of just one second right before the application scope and another as the first thing inside the scope.
.Net Version has been 3.0 through 4.7 (Due to Azure dev environment with Visual Studio)
Trying to narrow down which one UiPath is using to 4.6.2 since others in the 2018-2019 time period had success with this.
A colleague of mine also just encountered this error with Excel exclusively. The Delay trick did not work either.
The only changes I made were in the Config file but I reverted the changes easily. Additionally my colleagueās issue couldnāt be caused by my config file. The bots are attended no server setup yet.
The changes i meant are on the environment itself, like MS Office changes, protection software like antivirus etcā¦ Unless you are on an old OS like windows 7, you should not need to manually install any version of .NET framework, as this will add an extra set of possible issuesā¦ to be honest if this pc is for uipath only, it would be even better.
ah, I understand. I am on windows 10
Sadly I am unable to manipulate Antivirus/protection software due to business restrictions.
An update may have been pushed to my computer recently Iāll check the update logs.
As you suspected changing, or refreshing .NET did not change anything. I did a fresh install of UiPath too after the changes. Iām at a loss for what to try next.
Wow. I am incredibly surprised that somehow even during restarts across 2 days there was a phantom excel process open in Task manager. I killed it and tried again and it worked.
Thank you so much I will adjust my workflow to try account for this.
Yeah, 60% of our ācodeā is self defense against the apps and VDI we are automating and running on. RPAās dirty secret is that robots are pretty unreliable compared to traditional application platforms.
To be honest is a very important part of the processes that they will clean up the environment so next processes or executions will be fine to runā¦ A lot of those processes that will end up being alive are not something that is 100% avoidable, so it is best practice to have some processes killing at the end of them.
Mintu_Samanta
Raj_esh
dheephiga.am
ashokkarale