Com server permission error on Process.start
Hello, Using test execute version 1575 and up I encounter an issue in com server permission settings. Another application will run Process.Start to start a third application. TestExecute will then...
Forum Discussion
I figured this out. Process.start was opening up the third program in Session 0 which is non-interactive and dedicated for background processes. TestComplete was running in Session 1 which is the interactive user session. The the task scheduler is a workaround to this issue because it used the /IT flag, which forces that third application into session 1. Without that flag you hit the same set of permission issues as proccess start when using task scheduler.
I'm not sure why this was not an issue on older versions of test complete.