Execution Server - running as a service

Summary: When the Execution Server is installed it is a standard application (process). Some customers may prefer to use the execution server as a service so that a user does not need to be logged into windows on the Execution Server for the process to run. Please follow the instructions below in order to convert the Execution Server process to a service.

Limitations:The following features cannot be used when running the execution server as a service due to technical limitations.

1. GUI automation (Ranorex)
2. Writing to Excel through the Filesystem library prior to Library version 5.1.1
   
3. Libraries which must launch a GUI - example: IxNetwork
4. Studio Function - Capture Image

Instructions:

Stop QsExecutionServer process
1. Right click on "TestShell Execution Server" icon in the windows tray
2. Select EXIT option
3. Start->All programs->Startup folder
4. Delete "TestShell Execution Server" icon

Create and run windows service:
1. Open CMD
2. Run -> sc create TestShellExecutionServer binpath= "[PATH]\QsExecutionServer.exe" type= own start= auto displayName= "TestShell Execution Server"
3. Start->Run->services.msc
4. Start "TestShell Execution Server" service

Note:In the future, if you run the execution server configuration wizard, the default configuration will be reset and the application will be added back to windows startup. In case this occurs you will need to follow again the "Stop QsExecutionServer process" procedure above. To ease on that, you can create a simple batch file and "run as administrator" whenever needed. The file will look like this:

taskkill /im qsexecutionserver.exe
cd c:\users
del /S "TestShell Execution Server.lnk"
sc startTestShellExecutionServer

 It first stops the process that was started after the configuration, then deletes the links from the startup folders of all users and then starts the service again (since the configuration wizard stopped it).