Issue with TestExecute loading projects from a remote command
Apologies if this is covered in another thread, but I couldn't find this particular issue. We are trying to kick off TestExecute tests from our continuous integration build server (TeamCity), and are having trouble launching the tests via remote command session (not RDP).
I have TestExecute 9 installed on a machine, and I have created batch files and powershell/COM scripts that run my tests and export logs successfully. The scripts work when I run them locally, but if I kick them off remotely via psexec or powershell, the TestExecute process runs but the project suite does not load.
I have found that if I create a scheduled task with elevated privileges that runs the batch file (or powershell script), and start the task manually via the TSKSCHED.exe command, it starts successfully, but this is not a suitable workaround since the exit code will always be 0 from the TSKSCHED command. Nevertheless, the fact that it works as a scheduled task with elevated privileges leads me to believe the problem has something to do with UAC, but I have turned UAC off and still cannot kick off the tests via powershell or psexec.
Is this a known issue? I can post the script to troubleshoot, but perhaps someone has an easy workaround?
I have TestExecute 9 installed on a machine, and I have created batch files and powershell/COM scripts that run my tests and export logs successfully. The scripts work when I run them locally, but if I kick them off remotely via psexec or powershell, the TestExecute process runs but the project suite does not load.
I have found that if I create a scheduled task with elevated privileges that runs the batch file (or powershell script), and start the task manually via the TSKSCHED.exe command, it starts successfully, but this is not a suitable workaround since the exit code will always be 0 from the TSKSCHED command. Nevertheless, the fact that it works as a scheduled task with elevated privileges leads me to believe the problem has something to do with UAC, but I have turned UAC off and still cannot kick off the tests via powershell or psexec.
Is this a known issue? I can post the script to troubleshoot, but perhaps someone has an easy workaround?
