run-time not restarting on reboot

5 posts, 0 answers
  1. Adam
    Adam avatar
    7 posts
    Member since:
    Jun 2014

    Posted 24 Oct Link to this post

    I have 5 virtual machines setup to run tests during the week. Over the weekend our VMs reboot to pickup any windows updates and to refresh the systems. When the systems reboot the run-time edition instances running on these machines do not start up even though I have the "Run On Start Up" checkbox checked. This means that my Monday morning test cases don't run until I come in to the office and restart the run-time edition instances. Any help in getting this resolved would be great.

  2. Nikolay Petrov
    Admin
    Nikolay Petrov avatar
    81 posts

    Posted 25 Oct Link to this post

    Hello Adam,

    Which version of the product do you use?

    Which operating system you have on those machines? Are there any exceptions logged in the remote execution log after the restart of the OS?

    As a work around you may follow these instructions on how to add manually the execution server to start on system startup. If you choose this approach - un-check the option before that.

    Regards,
    Nikolay Petrov
    Telerik by Progress
     
    The New Release of Telerik Test Studio Is Here! Download, install,
    and send us your feedback!
  3. chris
    chris avatar
    6 posts
    Member since:
    Dec 2015

    Posted 26 Oct in reply to Adam Link to this post

    I Ran into the same problem. I delayed the telerik scheduling service on startup and it seemed to fix the problem. 
  4. Nikolay Petrov
    Admin
    Nikolay Petrov avatar
    81 posts

    Posted 31 Oct Link to this post

    Hi Chris,

    Thank you for being an active user and for sharing this information.

    Adam, do you still experience the initially reported problem or the proposed fix worked for you too?

    Regards,
    Nikolay Petrov
    Telerik by Progress
     
    The New Release of Telerik Test Studio Is Here! Download, install,
    and send us your feedback!
  5. Adam
    Adam avatar
    7 posts
    Member since:
    Jun 2014

    Posted 01 Nov in reply to Nikolay Petrov Link to this post

    I believe I found a solution. I used the Task Scheduler to trigger the client to startup after a system startup. That seems to be working for now.

     

    Thanks for you help and ideas everyone,

    Adam

Back to Top