Installing ODBC driver causing Ranorex to abort test

[jupton]

Hello,
I'm trying to test our Suite Installer (InstallShield) using Ranorex, but it seems that when our installer gets to the point of installing the S2 ODBC driver, the Ranorex test quits.

No reports or failures are generated. Is there a way to bypass this via Ranorex?

Thanks in advance!

[Support Team]

Hello Jeff,

Unfortunately, it is difficult to help you with your issue with the information you provided.
Would you mind giving us more information about the issue? Which version of Ranorex are you using?
At which point exactly does Ranorex stop the test?
Are there any error messages in the Windows Event Log?

Sincerely,
Bernhard

[jupton]

Hello Jeff,

Unfortunately, it is difficult to help you with your issue with the information you provided.
Would you mind giving us more information about the issue? Which version of Ranorex are you using?
At which point exactly does Ranorex stop the test?
Are there any error messages in the Windows Event Log?

Sincerely,
Bernhard

Thanks for the reply Bernhard,

I'll have to get some more detailed information about the ODBC driver that we're installing, but I can say that I originally ran Ranorex v7.2.1 and then upgraded to v8.0.0; both have the same issue.

The Ranorex test appears to stop right after the ODBC driver is installed, but there are no errors logged in Event Viewer that I can see.

The only things that I can find are relating to "Windows Installer reconfigured the product"

[Support Team]

Hello Jeff,

Would you mind sending me the error log of your test? The file should be available in the Ranorex\Logs directory.
C:\Users\YOUR_USER\Documents\Ranorex\Logs\YourTestExecutable.log

Are there any entries in the Ranorex Report?
Also, is it possible for you to create a support ticket and upload your Ranorex Solution, so that we can analyze the issue in more detail?

Sincerely,
Bernhard

[jupton]

Thanks Bernhard

I've created a support ticket. I have the log for the particular UserCode that is running when the TestRunner stops, unfortunately it's too large to attach here. (I've uploaded it as part of the Support Ticket)