Page 1 of 1

Win Server 2012 R2: Thread aborted exception

Posted: Tue Aug 12, 2014 6:34 pm
by gcushman
We are currently running Ranorex 4.1.4 to test our legacy Windows application. I upgraded to Ranorex 5.1.1 but still get the same issue. Our automation consists of a single testcase bound to a .csv file that contains 1075 rows of data. For the most part it runs without issues on Windows 7. However, all 3 times I've tried to run it on Windows 2012 (twice on Ranorex 4.1.4 and once on 5.1.1), I have encountered the following strange error:

The Ranorex report is open and shows all green. The problem is it only runs about 500 – 550 testcases out of 1075. When I scroll down to the last run test and expand the details I see a ranorex exception ("Thread was being aborted") and no other information. Strange that the report show that all testcases as passed even though it contains an exception.

I initially suspected a low memory condition on the 2012 VM image but that doesn't appear to be the problem.
I am the only one with access to this image (and the error occurs when I am sleeping) so there is no possibility that someone pressed the <Pause> key (and if that were the case, the testcase would show as a failure in the ranorex report).

Are there any recommended Configuration settings (Ranorex and/or OS level) for running on Windows 2012 that I might need to set?
Has anyone else reported anything similar to this problem?

Any feedback greatly appreciated.
Thanks,
Greg

Re: Win Server 2012 R2: Thread aborted exception

Posted: Tue Aug 12, 2014 7:07 pm
by krstcs
The stack trace would be helpful, if you could just expand it and copy-paste the text of it here.

Re: Win Server 2012 R2: Thread aborted exception

Posted: Tue Aug 12, 2014 9:35 pm
by gcushman
Thanks for quick reply, I should have thought to include those.
It is also worth mentioning that on the failing iteration, it looks as if it is trying to run the testcase, 'DTSRun', twice (should only run it once). I attached another screenshot. Iteration '509' ran successfully and shows one instance of testcase named "DTSRun'. Iteration '510' shows 2 instances of 'DTSRun' both in red. You can also see a section titled 'After Test Suite'. Each has a stack, here they are:

Stack for DTSRun Instance #1:
at InsightAuto.DTSRun.Ranorex.Core.Testing.ITestModule.Run() at Ranorex.Core.Testing.TestSuiteModule.RunInternal(DataContext parentDataContext)

Stack for DTSRun Instance #2:
at Ranorex.Core.Testing.TestSuiteModule.RunInternal(DataContext parentDataContext) at Ranorex.Core.Testing.TestSuiteModule.RunWithRepeats(DataContext parentDataContext, ErrorBehavior errorBehavior) at Ranorex.Core.Testing.TestSuiteModule.Run(DataContext parentDataContext, Boolean childSkip)

Stack from 'After Test Suite' section:
at System.Threading.Monitor.Enter(Object obj) at Ranorex.Core.Reporting.ActivityStack.GetInstance(Thread thread) at Ranorex.Core.Reporting.ActivityStack.get_Current() at Ranorex.Core.Testing.TestSuite.Run(String runConfigName, String runLabel, Dictionary`2 parameters) at Ranorex.Core.Testing.TestSuiteRunner.RunInternal(Type containerType, String testSuiteXml, RunParams rp)

I zipped up log files and attached them as well

Re: Win Server 2012 R2: Thread aborted exception

Posted: Wed Aug 20, 2014 1:57 pm
by gcushman
I posted this over a week ago and haven't heard anything from support team. Is there any update on this? Do I need to provide a snapshot or more information?
Any update would be appreciated.

Regards,
Greg

Re: Win Server 2012 R2: Thread aborted exception

Posted: Wed Aug 20, 2014 3:19 pm
by Support Team
Hi Greg,

Sorry for the slow response, we somehow must have overlooked this thread :(!

May I ask you to copy the attached NLog.txt file to the same folder where your executable is located in?
After you copied it please rename it to NLog.config and execute your test.
Please then send us the generated *.log file of such a failed test run to our support email address ([email protected]).
This file will hopefully give us more details about what was happening!

How do you connect to your server vm? Are you sure the connection doesn't get closed or lost during the test run?
Regarding the Windows 2012 Server configuration, there is no specific configuration needed. The same what holds for the normal client machines also holds for the server machines. You need the same requirements: System Requirements.
A Server OS is normally more restrictive in reagards to securtiy and user permissions but this shouldn't be the problem in this case.

Regards,
Markus

Re: Win Server 2012 R2: Thread aborted exception

Posted: Wed Aug 27, 2014 8:06 pm
by gcushman
thanks for the reply. I've been blocked from testing this temporarily but will send you info once I re-visit.