Forum Discussion
$ "C:\Program Files (x86)\SmartBear\TestComplete 11\bin\TestCompleteService11.exe" //LogonAndExecute //lDomain: "vmbld06it" //lName: "administrator" //lPassword: ******** //lTimeout: "300000" //lUseActiveSession: "true" //lCommandLine: '""C:\Program Files (x86)\SmartBear\TestComplete 11\bin\TestComplete.exe" "c:\jenkins\workspace\testcomplete bpreg\bpreg-test1.pjs" /run /SilentMode /ForceConversion /ns /exit "/ExportLog:c:\jenkins\workspace\testcomplete bpreg\3888101.tclogx" "/ExportLog:c:\jenkins\workspace\testcomplete bpreg\3888101.htmlx" "/ErrorLog:c:\jenkins\workspace\testcomplete bpreg\3888101.txt" "/ExportLog:c:\jenkins\workspace\testcomplete bpreg\3888101.mht" /Timeout:120 /project:bpreg-test1 /unit:bpreg_setup /routine:bpreginit"' [TestComplete] Test runner exit code: -10 (Unable to create a user session).
Same error unfortunately.
Thanks for answering. it is the classic question of keeping a acrive interactive desktop alive.
Our testExecute server runs from within a win7 pro guest under vmware player. We never stop that RDC session, then
the errors fails. Unfortunately this server is in another domain and installing vmware player and a separate win7 guest seems like a bit to much.
Hi Mortenb123,
If this doesn’t help, I recommend that you contact our TestComplete Support Team ( http://support.smartbear.com/product-list/ ) so that they could investigate this behavior.
- ParthiMSD8 years agoRegular Visitor
Hi,
Any updates on this. I'm also having the same issue for a longtime.
Thanks,
Parthiban J
- TanyaYatskovska8 years agoSmartBear Alumni (Retired)
Hi Parthiban,
I cannot locate the support case from mortenb123 in our case-tracking system.
If you have the issue, I recommend that you make sure that you are using the up-to-date product version - Ready! API 1.9. If you are, please contact our Support Team: http://support.smartbear.com/product-list/
- mortenb1238 years agoContributor
Hi Parthiban,
The way we solved this was by using a win7 workstation guest (and jenkins slave) in a vmware player. This autologs in using console0, and we then just keep it running. Then when jenkins fires off a testcomplete test on this slave the interactive console is active. We keep it open stading there. Major security concerns so it runs in a separate domain.
Windows server uses winlogon which creates a separate non interactive console for you, unless you are on the console.