Forum Discussion
Hi agapych
I ran into a similar problem when running my tested app using the Windows Run As command. I found the solution was to run TestComplete with elevated privileges in Windows (run as Administrator). Maybe this will work for you too.
- agapych8 years agoNew Contributor
Unfortunately it is not the case for me - my C# code is executed as administrator. Besides, the issue exhibits only on some environments. While on other VMs everything works good.
However there is one difference I noticed while inspecting the started application using ProcessExplorer tool.
On the environments where TestComplete hook works, the process of the application under test does not have Jobs tab. While on the problematic environments it does have a related job. Not sure if this matters, but this is the only difference I managed to find between the started processes on healthy and problematic environments.
Related Content
Recent Discussions
- 38 minutes agoSvetaG