I have not had any problems running test complete over remote desktop other than when you disconect it locks the computer meaning TestComplete can't use the mouse or keyboard.
If you think that is the problem I would make sure.
I would sit down at that computer even if I had to plug my keyboard, mouse and monitor into it to be sure.
Its likly that the setup is different on that computer. Or like I mentioned if you disconect your remote desktop the computer is locked and it can't access the keyboard or mouse. Also when you are not remoted into that machine and tests are running you most likly will need to have a keyboard, mouse and monitor it probably will not work either.
Thank you BWinkler. I guess it's not related to remote desktop at all because I found a spare keyboard and mouse and plugged them into the 2nd PC (our newly dedicated TC PC), rebooted it; then I opened TC and ran the very basic login script that worked on my own PC 2 days ago. It failed with the exact same error as before, which tells me that the issue is not with remote desktop at all. Arg!
I think I'll open a case. I've copied all the projects and scripts over that worked previously to the new dedicated TC PC. The URL is fine when I access it manually but not when using TC.
What version of FF is on the PC that you are having the errors with? Are you sure you have the right right patches for the version? I would start there first.
If I'm reading this right, you are running your test on a remote machine (with Browser and TestComplete and Project on THAT machine)....
if you intend to leave that session unattended, you need 2 things:
1- Disable screen saver and energy saver
2- If you want to "disconnect" from the session, use the taskmanager /user tab and find your session number...
Type at the cmdline : tscon sessionNumber /Dest:Console to exit the RDP session safely
This will prevent the actual session from being disrupted while running your tests...
Make sure Firefox has the same settings than your own.. (startup page, etc..)
First thing to find out would be if the test works correctly on the remote machine when you are actually logged into it as a primary user (without remote desktop). If that works then refer to this article : https://support.smartbear.com/viewarticle/72139/
It shows us how you will be able to minize the remote desktop after kicking off the test and continue with your work on your PC while the tests continue to run on the remote PC.
I have implemened this and it works great.
