Problems launching Edge in AWS

Hello Forum Members,

I’m in the midst of deploying an unattended robot on AWS for the first time, and I’ve hit a snag with Microsoft Edge. My process has been running smoothly as an attended bot on my personal laptop for a while now. It either launches Edge or utilises an existing tab if Edge is already open.

I’ve recently set up an AWS EC2 instance, installed Edge, and added the necessary extension. However, I’ve encountered a hiccup. When I initiate the unattended process, whether it’s unattended through a trigger on Orchestrator or manually via Studio under troubleshooting mode, it tries to launch Edge—you see the Edge icon flash and a blue UiPath icon appears in the Start menu—but then Edge shuts down.

Oddly enough, if Edge is already running, the process runs fine, although it doesn’t latch onto the current tab and instead, it opens a new tab and runs as expected. This is slightly different to the way it behaves in attended on my laptop.

I’ve attached a screenshot to provide more context on the issue.

This is really starting to bug me and so any help is really appreciated!

Mark

@Mark007

  1. As you have studio on aws try to check if there are any differences in selectors
  2. Check the event viewer logs if you see something unusual when edge opens

Cheers

Hi @Anil_G

Thanks for your response.

  1. Given the workflow is the same won’t the selector be the same. Assuming you meant test it, using Studio I opened up the selector and it validates the Edge Browser in AWS no problem.

  2. I have checked the event logs which are as follows:

UiPath.Executor 23.10.0.0
System.Runtime.InteropServices.COMException (0x80040234): Exception from HRESULT: 0x80040234
at UiPath.UiSystemClass.StartBrowser(String bstrSelector, String bstrURL, String bstrArguments, UiBrowserName browserType, Int32 timeoutMs, UiBrowserFlags browserFlags)
at UiPath.UIAutomationNext.Services.UiSystemService.<>c__DisplayClass17_0.b__0()
at UiPath.UIAutomationNext.Services.DriverServiceCore.WrapCom[T](Func`1 toExecute)

UiPath.Executor 23.10.0.0
System.Runtime.InteropServices.COMException (0x80040234): Exception from HRESULT: 0x80040234
at UiPath.UiSystemClass.StartBrowser(String bstrSelector, String bstrURL, String bstrArguments, UiBrowserName browserType, Int32 timeoutMs, UiBrowserFlags browserFlags)
at UiPath.UIAutomationNext.Services.UiSystemService.<>c__DisplayClass17_0.b__0()
at UiPath.UIAutomationNext.Services.DriverServiceCore.WrapCom[T](Func`1 toExecute)

UiPath.Executor 23.10.0.0
System.Runtime.InteropServices.COMException (0x800402FF): Exception from HRESULT: 0x800402ff
at UiPath.UiNodeClass.FromSelector(String bstrSelector)
at UiPath.UIAutomationNext.Services.DriverService.<>c__DisplayClass17_0.b__1()
at UiPath.UIAutomationNext.Services.DriverServiceCore.WrapCom[T](Func`1 toExecute)

UiPath.Executor 23.10.0.0
System.Runtime.InteropServices.COMException (0x800402FF): Exception from HRESULT: 0x800402ff
at UiPath.UiNodeClass.FromSelector(String bstrSelector)
at UiPath.UIAutomationNext.Services.DriverService.<>c__DisplayClass17_0.b__1()
at UiPath.UIAutomationNext.Services.DriverServiceCore.WrapCom[T](Func`1 toExecute)

This doesn’t mean much to me, but it would be great if you could give me any insight from them!

This is the Output from Studio:

image

Thanks

Mark

@Mark007

Looks like youa re trying to load feeds in linkedin…and when in local may be it is using yourlogin directly but on aws it isredirecting to a different window

can you check the same

cheers

Hi @Anil_G - it is using LinkedIn using a local account and I have logged in manually to ensure it is already logged in. As I mentioned above if I open the browser first and then run the process from Studio it runs no problem. Note I simply open the browser manually, I don’t navigate from the browser home page and so this really appears to be a Edge launch issue, not a log in issue as it never gets far enough to navigate to a page (“no open windows found”).

Hi Anil_G

Just to close this off. Given how odd the behaviour was, I thought I would just spin up another AWS instance and see if I could recreate the issue. The workflow works fine on this new instance and so clearly this is just an issue with the AWS install!

Thanks for your help.

Mark

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.