Inflectra Customer Forums: RemoteLaunch/SoapUI testrunner freezing (Thread) When invoking SoapUI testrunner from RemoteLaunch a cmd.exe window is opened on the automation host, which remains blank, and never completes or closes by itself. While the cmd window is open, SpiraTeam does not recognise the test run. If the window is closed manually, SpiraTeam will be updated and report the results of the test run. As the whole point is to automate testing, this manual intervention is not viable. Is there a fix/workaround/setting, please? Charlie en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/remotelaunch/automation-engines/219.aspxthreadId=219Charlie Stott (cstott@tnsi.com)RemoteLaunch/SoapUI testrunner freezing When invoking SoapUI testrunner from RemoteLaunch a cmd.exe window is opened on the automation host, which remains blank, and never completes or closes by itself. While the cmd window is open, SpiraTeam does not recognise the test run. If the window is closed manually, SpiraTeam will be updated and report the results of the test run. As the whole point is to automate testing, this manual intervention is not viable. Is there a fix/workaround/setting, please? Charlie Thu, 15 Dec 2011 05:06:19 -05002025-12-09T08:33:32-05:00/Support/Forum/remotelaunch/automation-engines/219.aspxmessageId=421David J (adam.sandman+support@inflectra.com)The plugin simply calls the command-line and waits for it to exit. When you run the tests manually tThe plugin simply calls the command-line and waits for it to exit. When you run the tests manually through the command line (not through remote launch) does it automatically return control back to the command-line? If you run the script from the Windows > Start > Run button, does the command window automatically closeThu, 15 Dec 2011 21:32:40 -05002011-12-15T21:32:40-05:00/Support/Forum/remotelaunch/automation-engines/219.aspx#reply421messageId=424Charlie Stott (cstott@tnsi.com)Hi, Thanks for the reply. Further investigation shows that the tests do eventually complete and retuHi, Thanks for the reply. Further investigation shows that the tests do eventually complete and return results to SpiraTeam. Scheduled runs appeared to run much slower than from the command line, but it seems that our host automation tool is the problem in this situation, taking it's default values from different places depending on how the tool is launched. Kind Regards, Charlie Fri, 16 Dec 2011 00:37:44 -05002011-12-16T00:37:44-05:00/Support/Forum/remotelaunch/automation-engines/219.aspx#reply424messageId=429David J (adam.sandman+support@inflectra.com)OK, glad that cleared things up.OK, glad that cleared things up.Mon, 19 Dec 2011 15:48:50 -05002011-12-19T15:48:50-05:00/Support/Forum/remotelaunch/automation-engines/219.aspx#reply429messageId=7474jack grace (jack425grace@outlook.com) The quick and clean solution is to create a small wrapper batch file that uses the CALL command to The quick and clean solution is to create a small wrapper batch file that uses the CALL command to launch SoapUIs testrunner.bat. Tue, 09 Dec 2025 08:33:32 -05002025-12-09T10:39:48-05:00/Support/Forum/remotelaunch/automation-engines/219.aspx#reply7474