[TestExecute version 12.6]
I don't understand why since a few months when I launch TestExecute from command line with /exit, /DoNotShowLog, and /SilentMode parameters it don't launch TestExecute.
So I remove the /SilentMode parameter hoping that TestExecute will show me the issue, but no : at this moment it just works !
Is there any known issues with the /SilentMode please ?
Solved! Go to Solution.
Just an idea: you may check if Silent.log file contains some useful info. https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/..., \SilentMode parameter paragraph.
One possibility: If you are running a different version of TestExecute than the project was created in, there might be a converstion being attempted. What happens when you add the "/ForceConversion" flag when you run in SilentMode?
One more idea:
If I remember it right, I had an issue with TestExecute that /exit (or /e) parameter had to be the last one in the command line.
Does it help if you change your command line so that /e is at its end?
One more idea: instead of simple command line try something like batch file (https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/...) and check what exit code is returned when TE does not start. My guess is that it may be the problem related to the licensing, another instance still running, etc.
Ah, yes... if you're using floating licenses, it's entirely possible that the intermittent problems are that all the licenses are being consumed.