Tests Crashing When Run as Administrator

Ask general questions here.
rphmee
Posts: 6
Joined: Tue Jun 05, 2018 2:46 pm

Tests Crashing When Run as Administrator

Post by rphmee » Fri Oct 05, 2018 2:55 pm

When running Ranorex as Administrator and then trying to run my tests, the tests crash after the first few seconds of running and give no indication as to why. The same tests when run normally run to completion without issue. There are certain tests in my test suite that require admin privileges so I need to be able to do this.

Is there any known issue that may be causing the crashes?

User avatar
Stub
Posts: 173
Joined: Fri Jul 15, 2016 1:35 pm

Re: Tests Crashing When Run as Administrator

Post by Stub » Fri Oct 05, 2018 3:43 pm

I always run Ranorex as Administrator. Works fine for me on our application I'm afraid! I've been using Ranorex since v6.0.

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

Re: Tests Crashing When Run as Administrator

Post by odklizec » Fri Oct 05, 2018 3:53 pm

Hi,

My guess is that there is corrupted something on the system level? Maybe .Net or any of the required VC redistributable libs?

What version of Ranorex do you use and on what OS? Could you please check Ranorex tracing logs? Maybe there is something useful in them. You can find them here:
%userprofile%\Documents\Ranorex\Logs

Please make sure that you are using most recent Ranorex version (either 8.2.1 or newest 8.3). If it crashes with older Ranorex, your only hope is to try to uninstall and reinstall both Ranorex and all required libs.
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

rphmee
Posts: 6
Joined: Tue Jun 05, 2018 2:46 pm

Re: Tests Crashing When Run as Administrator

Post by rphmee » Fri Oct 05, 2018 4:30 pm

Thanks for the response.

I'm using 8.2.1 on Windows 10. It seems that uninstall/reinstall temporarily fixes the issue, but once it pops back up it remains. I'll take a look at the logs when I get a chance.