Ranorex Forum

Hi.
I have a problem with Ranorex, where it stops detecting controls when run through Psexec. Did any of you come across similar issue?
My setup
Fully coded test installs our AUT, runs a bunch of tests on it and then uninstalls it. Everything runs fine when run locally but when running through Psexec uninstallation dialog is not recognized. Uninstallation dialog shares some components with installer, these are recognized fine when installing and not when uninstalling.
My psexec command
psexec.exe \\dkvm-mercury-10 -accepteula -w "C:\RunDir" -u domain\test -p test. -i -h C:\RunDir\SmokeTester.exe -p=xpe
Attached are two snapshots. One of installer dialog made during installation and the other one during uninstallation made during the same run.
Any help with this would be appreciated.

Hi,

Uninstallation dialog shares some components with installer, these are recognized fine when installing and not when uninstalling.

RxPaths of e.g. the "Continue" buttons of installation/uninstallation are NOT the same. They also do not have the same attributes.

Are you able to highlight the repository-elements for uninstallation? What does the path look like (locally/with rsexec)?

Please make sure that the path is the correct one for each of the elements for installation as well as for uninstallation.

Kind Regards,
Larissa
Ranorex Support Team

Snapshot made during unistallation is what my tests 'sees' when running through Psexec. When starting spy or running tests locally paths are the same (containers and button instead of elements) and can be highlighted.

Hi,

Do you get report messages which provide any information about this behavior (try to turn report-level to debug). How is your installation and uninstallation started (e.g. start application or mouseclick)? If they are not started the same way, this behavior may be the consequence.

Regards,
Larissa
Ranorex Support Team

No helpful messages in report. We always run with debug level, but all tests are coded from scratch so besides a few warning we control everything that gets into report.

Install is started by Process.Start from C#.
Uninstall is started through Programs and Features window in windows.

I'll see if running Uninstall through Process.Start helps.