"The target Element was not specified for this activity" Error

[Anamika15 (Anamika)]

I have attached one workflow that reads column “0” from excel sheet and performs action based on the text written in the first Column e.g Add, update or delete.
While running this workflow I am getting following error:

Please tell me how can I resolve this issue.
Thanks in advance!!!

HRMS_Report V2.1.xaml (75.6 KB)

[Palaniyappan (Forum Leader)]

@Anamika15

I have attached one workflow that reads column “0” fro

–keep the cick ‘input’ activity inside the attach window activity and make sure that you have selected the element in attach window activity
as you have browser variable in attachwindow its look fine

Cheers @Anamika15

[Anamika15 (Anamika)]

Done… Still getting the same error.

[Palaniyappan (Forum Leader)]

We have click input in two sequences
Make sure that they are placed in both the sequences
cheers @Anamika15

[Anamika15 (Anamika)]

Done… But now getting above mentioned error…

[Palaniyappan (Forum Leader)]

Fine kindly try with other browser
Cheers @Anamika15

[chenderson (Cary Henderson)]

Good morning Anamika,

In regards to your HRESULT issue, do either of these solutions resolve the issue?

@Kit

Having tried every suggestion to fix the “Error HRESULT E_FAIL has been returned from a call to a COM component” from across the forums, none of which worked for me, I found my own fix, so posting it in the hope that someone in future may find it useful.

I determined that, in my environment, the Chrome Native Messaging capability within Chrome itself was broken, determined by finding a few other Google Extensions from the Play store that required this capability, none of which worked.

So - not a UiPath problem, but a Chrome one, despite running the latest version of Chrome.

The fix was to uninstall and re-install Chrome - remembering to install from https://google.com/chrome (to avoid the multitude of 3rd party Chrome builds that come up top in the search page rankings, which come bundled with hidden Spyware)

@Rohit

I think this error is related to loading of websites which uses some javascript framework for content. I was getting this error in Get Attribute activity. This was solved by adding a delay. Just put a delay of few seconds before the activity on which you are getting this error.