Problems with OpenBrowser starting IE on Virtual Desktop

Ask general questions here.
Posts: 9
Joined: Thu Apr 16, 2020 9:54 am

Problems with OpenBrowser starting IE on Virtual Desktop

Post by Polariteit » Thu Apr 16, 2020 10:41 am

Hi there,

We are using Ranorex for a large amount of testcases for about 2yrs now, and it's working fine on our Fatclient-setup. We have several machines, and start scripts on other machines using the ranorex agent.

No we're starting to use Virtual Desktops, and I've installed Ranorex 9.3.1 on it.

Unfortunately it is not possible to use the usercode that we've built to start the webapplication usings IE11 that works fine on our fatclients.

This module looks like this and it doesn't work no the VDI. When running this part, it says 'failed to open URL in IE. Access denied'

Code: Select all

//Host.Current.OpenBrowser("http://"+ TestSuite.Current.Parameters["Omgeving"] + "URL", "ie", "", true, true, true, false, true);
Only after making some changes in the parameters it succeeds:

Code: Select all

  Host.Local.OpenBrowser("http://"+ TestSuite.Current.Parameters["Omgeving"] + "URL", "ie", "", false, true, false, false, false);

On VDI we're using Win10, IE11 and Ranorex 9.3.1. The IE11 plugin is also installed.

Do you have any suggestions? I also tried running Ranorex in Admin-mode, and it gave another error: Failed to get rows from data source: Failed to load Excel data. Microsoft Excel .....

User avatar
Ranorex Guru
Ranorex Guru
Posts: 6797
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Problems with OpenBrowser starting IE on Virtual Desktop

Post by odklizec » Mon Apr 20, 2020 8:17 am


This post should help you with "Access denied" error: ... tml#p46121
Basically, it's timing error and adding short delay before OpenBrowser action should help with Access denied error, caused byt "KillExisting" option. Hope this helps?
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration