1 Answer, 1 is accepted
Hi Fred,
This type of error pops up when there is no UI desktop session on the execution machine, or the execution context has no access to it (minimized RDP connection window, for example). It usually appears when trying to run unattended tests on a remote machine. You can refer to another forum thread on the same topic.
The only way to prevent the appearance of this error is to ensure the active desktop session on the execution machine. Test Studio Test Runner provides an out-of-the-box solution with its options, that allow you to control the user session.
On top of these options, there are few workarounds, which we can confirm are feasible options to keep the active user session.
I hope this will help you in sorting out any troubles you might have.
Regards,
Elena
Progress Telerik