Resolve Common Scheduling Issues


I would like to use Test Studio's Scheduling feature. I've configured the Scheduling Server and attached a Remote Execution Server (those two might be located on the same machine) to it successfully. However, scheduled executions are never fired on the Execution Server.


First try opening the results from Test Studio's Results view. The results might simply disappear. Alternatively, you might get a message giving you some details on the problem.


Here are solutions to the most common Scheduling issues:


  1. Check the Scheduling Log for errors

    The Scheduling Log is located in Test Studio's installation folder. By default its location is:

    • C:\Program Files (x86)\Telerik\Test Studio\Bin\Telerik.TestStudio.Scheduling.Log.exe


    Take a look at the events in the log (especially near the end). Identify the error indicating why Scheduling failed.


  3. Ensure the Scheduling Server and each Execution Server is running the same version of Test Studio

    The Scheduling service is not designed to be cross-version. Your Scheduling Server and Execution Servers can run under different version of Windows, but never under different versions of Test Studio (Standalone, Visual Studio plugin, and Run-Time editions). We recommend using the latest available version, especially for Scheduling since it's being improved with each release.


  5. Restart the Telerik Test Studio Scheduling Service and make sure it stays running 

    The Test Studio Scheduling Service must be running on the Execution Server in order for you to be able to execute tests on this machine. This service is started when you configure the machine as an Execution Server. 


    Log on to the Execution Server and bring up the Windows Services menu. (It's in Task Manager in Windows 7; in XP you access it by running services.msc from Start > Run).


    Find the service, stop it, and start it again in order to restart it. Make sure it remains running (i.e. it doesn't immediately switch back to stopped):




  7. Clear the event log file

    If you restart the service manually and it immediately stops, the TelerikWebUIServiceSourceLog may be full. Launch Event Viewer and expand the Applications and Services Logs node. Right click TelerikWebUIServiceSourceLog and select Properties. On the General tab you can increase the maximum log size. Also, set it to Overwrite events as needed when the maximum log size is reached.



  9. Ensure the Telerik Test Studio Client application is running

    The Test Studio Client application must be running on the Execution Server in order for you to execute tests on this machine. This process is started when you configure the machine as an Execution Server. Log on to the Execution Server and bring up the Windows Process menu. Ensure this process is running:



    If it's not there, run the Configure as Execution Server application:



  11. Ensure your project location is accessible from the Remote Execution Server

    When you connect your project to a Scheduling Server, you configure the project location:



    The Scheduling service running on the Execution Server uses this location to get access to the project and execute your test list (by default it points to the current project location). You have to make sure the Scheduling service on the Execution Server can readily access this location. By default the Scheduling service runs under the Local System account. This means that you will have to give Everyone Read/Write permission to access your project location share. Log on to the machine on which the share is located. Right-click on the shared folder and open Properties. Under Sharing you'll find the sharing configuration. Add Everyone



    Alternatively, you can change the account under which the Scheduling service is running to your own (i.e. the one with which you're logged on to the Execution server) and add your account to the Permissions list for the share location (the same way you would add Everyone as described above). 



    In this case you won't need to grant Everyone access to the share. The drawback to this is that you will need to be logged on to all machines involved with this same account.


  13. Execute the test from a different location 

    You've opened a project in Test Studio. At the same time a scheduled execution on a Remote Machine is trying to execute a test list from this project from the same location. By opening it you've locked the project and you've denied all other applications (including the scheduled Remote Execution) access to it.There are two things you can do to avoid this issue. You can simple refrain from having the Project opened in Test Studio during scheduled test runs. Or you can copy the project to a different location and connect your project to that location.  


  15. Ensure the Execution Server is in the same Domain as the Scheduling Server:

    This is how you can check what Domain a machine is located in Windows 7:


    Right click on My Computer and select Properties > Remote settings > Computer Name Tab > Change. Edit the Domain field under the Member of section.


    Here is an article that describes how to do this in XP.


    Domain name displayed 


  17. Wait a few minutes

    From the Scheduling configuration app you can set the tick period.



    The tick period indicates how often Test Studio will check the database for scheduled runs. If you set it to 5, this means that Test Studio will check 5 every minutes to see whether there are test lists to execute.


    Now if you schedule a test run for 12:00 and a tick is set to go off at 12:05, then the test will be executed at 12:05 when Test Studio checks and determines there's something to execute. If you refresh your Results view in the period 12:00-12:05, you will get a warning message (in earlier versions your scheduled test list would disappear with no explanation). This happens because tests scheduled in the past (i.e. past 12:00 in this case) are considered executed. Test Studio tries to load the results for these tests. However, since in practice the test hasn't been executed yet, there are no results to load.


    You should wait as many minutes as you've set in the Configure Scheduling Server wizard to be 100% certain your scheduled test will run. By default it's set to 5 minutes, so if you haven't changed it then that's how long you should wait. For instance, if you set a test for 12:00, you might have to wait until 12:05 for the tick. 


  19. Open port 8009 in Windows Firewall

    The Windows Firewall on the remote machines may be blocking the connection attempt from the local machine. Here is an article on how to configure Windows Firewall to allow the Test Studio connection through. (The article is written for the Performance port 8010. Simply substitute in the Scheduling port 8009).