AlumniHi Joshua,
Do I get it right that the tests are executing fine on Windows Server 2012 right after the server restart? Can you identify the period after which the tests stop executing and you have to reboot the server?
I've managed to narrow this problem down a little further... So here goes.
I previously had a GPO in place to launch our tested application and TestExecute when the machines were started. If I disable this GPO, I have to manually start both the tested application and TestExecute. When the TE application is started manually, the applicaiton will run the scripts without failure. If I allow the GPO to start the tested application and TE, then the test will launch Internet Explorer ( a step required to generate data for the tested applicaiton) and then it appears to lose scope of the the IE browser.
When TE and the tested app are launched via GPO, and the test fails, I can then cause a crash with the TE applicaiton by simply right clicking the TE system tray icon and using the applicaiton's built in exit command. Exiting the application in this manner (the intended manner), causes the crash, which reports a problem with asComm in TestExecute.
