Activity works in one Environment but not the other

[PWilliams]

I have an issue where activities stopped working in only one environment. I have three environments, Dev, QA, and Production. The automation is the exactly the same in each environment. Meaning the versions are the same for the automation and the Web Application it interacts with. It runs without issue in Dev and Production, but in QA it stopped working on a Type Into activity; which is one of the first activities it works with. What would cause this to happen? Could a browser version cause this? Example, IE11 is at version 10 in Dev and Prod, but version 11 in QA. Just trying to figure out why something like this would occur.

Error:
Cannot find the UI element corresponding to this selector:
System exception at initialization: Cannot find the UI element corresponding to this selector: at Source: Type Into - Username

[lukasziebold]

Yes, a browser version could cause something like this.

You should check your selector of this Type Into - Username activity und make sure it is dynamic enough for any differences in your environment. Maybe the version number is in the selector somehow? You can wildcard it!

Good luck

[Srini84 (Srinivas Kadamati)]

@PWilliams

As the browser version changed, and the UiElement is dependent on the selector how you build also

So better maintain same configuration across your 3 environments

Hope this may help you

Thanks

[nilesh.mahajan]

Hello,

first try to type with changing properties like “SendWindowsMessage” or “SilumateType”.
hope so your issue will resolved here itself.

[PWilliams]

So, I figured out the issue. We upgraded to Windows Server 2019. With that, IE advanced settings has both “Enhanced Protected Mode” turned on which is causing the issue.