Community Chat

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Hi Gavin Rudling,

I have issues in the past in some cases if I add "--force-renderer-accessibility" after the URL while launching the application it resolved it.

But found this knowledge base article try this and please let me know how it goes.
https://support.blueprism.com/en/support/solutions/articles/7000084193--notification-updated-18-sept-23-latest-versions-of-chrome-and-edge-browsers-causing-issues-with-u

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Oh man have I scratched my head on this one - thanks a lot for the tip on "=complete" command!!

For those interested you can see the difference with the "edge://accessibility" url command. 

Hi Gavin Rudling,

I have issues in the past in some cases if I add "--force-renderer-accessibility" after the URL while launching the application it resolved it.

But found this knowledge base article try this and please let me know how it goes.
https://support.blueprism.com/en/support/solutions/articles/7000084193--notification-updated-18-sept-23-latest-versions-of-chrome-and-edge-browsers-causing-issues-with-u

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Hi Gavin

Did your VMs update Edge browser to v117.0.2045.31 on Sunday? If so:

The latest versions of the following browsers are causing Accessibility/UIA spying to fail within Blue Prism Enterprise:

·         Google Chrome Version 117.0.5938.63 - released 13-Sept-23

·         Microsoft Edge Version 117.0.2045.31 - released 15-Sept-23

This issue occurs because these latest browser updates have changed the default behaviour of the --force-renderer-accessibility flag (which enables UIA mode to spy on the browser elements). As a result, 'Complete' is no longer part of the force-renderer-accessibility command by default. 

How to work around this issue

Pass in the command "-force-renderer-accessibility=complete", which should resolve the issue and allow for UIA spying.

If some of your automations have started not working (properly) this may well be the cause

This was gleaned from BP support by @Ian Meldrum

I had an automation failing that was using the old version of the --force-render-accessibility parameter and it started working again by removing that from the launch url

Not tried the above solution yet myself

Regards

Kirk

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Hi Gavin

Did your VMs update Edge browser to v117.0.2045.31 on Sunday? If so:

The latest versions of the following browsers are causing Accessibility/UIA spying to fail within Blue Prism Enterprise:

·         Google Chrome Version 117.0.5938.63 - released 13-Sept-23

·         Microsoft Edge Version 117.0.2045.31 - released 15-Sept-23

This issue occurs because these latest browser updates have changed the default behaviour of the --force-renderer-accessibility flag (which enables UIA mode to spy on the browser elements). As a result, 'Complete' is no longer part of the force-renderer-accessibility command by default. 

How to work around this issue

Pass in the command "-force-renderer-accessibility=complete", which should resolve the issue and allow for UIA spying.

If some of your automations have started not working (properly) this may well be the cause

This was gleaned from BP support by @Ian Meldrum

I had an automation failing that was using the old version of the --force-render-accessibility parameter and it started working again by removing that from the launch url

Not tried the above solution yet myself

Regards

Kirk

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Hi,

For what it's worth, we had exactly the same issue yesterday. It was fixed using the solution above, but using the parameter --force-render-accessibility=complete when launching Edge, instead of just --force-render-accessibility.

Hopefully yours will be fixed as easily - the hardest part was finding the fix!

John

Hi Gavin

Did your VMs update Edge browser to v117.0.2045.31 on Sunday? If so:

The latest versions of the following browsers are causing Accessibility/UIA spying to fail within Blue Prism Enterprise:

·         Google Chrome Version 117.0.5938.63 - released 13-Sept-23

·         Microsoft Edge Version 117.0.2045.31 - released 15-Sept-23

This issue occurs because these latest browser updates have changed the default behaviour of the --force-renderer-accessibility flag (which enables UIA mode to spy on the browser elements). As a result, 'Complete' is no longer part of the force-renderer-accessibility command by default. 

How to work around this issue

Pass in the command "-force-renderer-accessibility=complete", which should resolve the issue and allow for UIA spying.

If some of your automations have started not working (properly) this may well be the cause

This was gleaned from BP support by @Ian Meldrum

I had an automation failing that was using the old version of the --force-render-accessibility parameter and it started working again by removing that from the launch url

Not tried the above solution yet myself

Regards

Kirk

Good Day team, Trust you are all well.

We, all of a sudden on a particular BPC VM have started to experience elements that can no longer be found on an MS Edge browser process. We have used multiple spy methods, like Browser mode and UIA mode.

For some reason all the UIA mode elements are throwing this error.

This is an existing process been running for over a year and this error just started this last Sunday.

When trying to re-spy the elements the UIA mode is only giving us the outer window element.

Has anyone else experienced this and if so, are there any recommendations?

Kind regards

Gavin

Hi,

For what it's worth, we had exactly the same issue yesterday. It was fixed using the solution above, but using the parameter --force-render-accessibility=complete when launching Edge, instead of just --force-render-accessibility.

Hopefully yours will be fixed as easily - the hardest part was finding the fix!

John