I've reproduced the issue on my side.
Try use "Start-Process TestComplete.exe". Also if you need to use some parameters read help info for PowerShell "Start-Process" command.
TestComplete is a locally installed executable. So, in order to run it from a CI system (like Jenkins), whatever machine you intend to execute it on HAS to have TestComplete installed. The way Jenkins works is that there is an agent on a remote machine that executes the automation and that remote machine has TestComplete installed.
So, my guess is that you're calling the TestComplete commandline but the machine you're making the call on doesn't actually have TestComplete installed.
Interesting. I am using remote desktop and using it as if it was a local machine. I downloaded it and installed it just like I did on the local machine as well. The Test Complete directory is on the C drive of machine with the executable in it. It just seems like the path to TestComplete is getting passed as the argument for the project path. Could this be a problem with my environment variables or do you have any other ideas?
It might be helpful to know what you're actually doing in the way of a commandline to execute automation. Can you paste in the commandline string you're executing?
This error happen whenever I run this commandline regardless if there are parameters or not. Usually when I run this command without paramaters it just open test complete without any project open but on this machine it seems to be acting differently.
TestComplete.exe
Environment Variables:
