{"id":11707,"date":"2024-03-18T06:24:15","date_gmt":"2024-03-18T13:24:15","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=11707"},"modified":"2024-03-18T06:24:15","modified_gmt":"2024-03-18T13:24:15","slug":"run-batch-file-as-a-windows-service","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/run-batch-file-as-a-windows-service\/","title":{"rendered":"Q&A: How do I make AlwaysUp run my Batch File as a Windows Service?"},"content":{"rendered":"
\"How<\/div>\n
\n  We purchased AlwaysUp to run a batch file that runs a web front end for a database. But when we plug it in it doesn’t work. AlwaysUp tries to run the script but gives up after five tries.<\/p>\n

The script contains a couple of commands:<\/p>\n

\ncd "C:\\Program Files\\Simtec Viewer"
\nstart \/max simtecw.exe\n<\/div>\n

Is there a way to get it to run constantly, as a service?<\/p>\n

— Roy W.<\/p>\n<\/div>\n

Hi Roy, thanks purchasing AlwaysUp. We really appreciate your support!<\/p>\n

Thanks also for including the batch file in your support request. Because of that, we were able to spot exactly what’s going wrong for you.<\/p>\n

Let’s dig into the problem and highlight the solution.<\/p>\n

The problem: The “start” command doesn’t wait for your application to finish<\/h2>\n

AlwaysUp has trouble because of how the batch file launches your executable — with the Windows start command<\/a>.<\/p>\n

Most importantly, the start command is non-blocking. That is, after it launches your application, it exits. It doesn’t wait for your application to complete its work and close.<\/p>\n

With that understanding of the start command in place, here’s how things play out when you start your batch file entry in AlwaysUp:<\/p>\n

\n
    \n
  1. \n

    Your AlwaysUp Windows Service starts<\/p>\n<\/li>\n

  2. \n

    AlwaysUp launches your batch file<\/p>\n<\/li>\n

  3. \n

    The batch file executes<\/p>\n<\/li>\n

  4. \n

    The batch file runs the “cd” command, which changes the working directory to “C:\\Program Files\\Simtec Viewer”.<\/p>\n<\/li>\n

  5. \n

    The batch file runs “start \/max simtecw.exe”<\/p>\n<\/li>\n

  6. \n

    The start command launches “simtecw.exe”<\/p>\n<\/li>\n

  7. \n

    The start command exits<\/p>\n<\/li>\n

  8. \n

    The batch file exits<\/p>\n<\/li>\n

  9. \n

    AlwaysUp detects that the batch file has exited<\/p>\n<\/li>\n

  10. \n

    AlwaysUp restarts the batch file (as configured on the Restart tab<\/a>)<\/p>\n<\/li>\n

  11. \n

    Repeat the cycle, starting at step 3<\/p>\n<\/li>\n<\/ol>\n<\/div>\n

    After five attempts, AlwaysUp gives up at step 10 and shuts down the Windows Service. Your run ends in failure — all the time.<\/p>\n

    Fortunately the fix is very simple. You just need to add 6 characters to your script to make it work as desired with AlwaysUp. \ud83d\ude42<\/p>\n

    The solution: Make the “start” command wait for your application to finish<\/h2>\n

    The key is to get the start command to block while your main executable is running. That way the script won’t exit immediately and AlwaysUp won’t try to restart it again and again.<\/p>\n

    To get the start command to block, simply add the \/wait<\/b> parameter to the command line, like this:<\/p>\n

    \nstart \/max \/wait simtecw.exe\n<\/div>\n

    And with that adjustment, a healthier pattern should unfold when you start the batch file in AlwaysUp:<\/p>\n

    \n
      \n
    1. \n

      Your AlwaysUp Windows Service starts<\/p>\n<\/li>\n

    2. \n

      AlwaysUp launches your batch file<\/p>\n<\/li>\n

    3. \n

      The batch file executes<\/p>\n<\/li>\n

    4. \n

      The batch file runs the “cd” command runs which changes the working directory to “C:\\Program Files\\Simtec Viewer”.<\/p>\n<\/li>\n

    5. \n

      The batch file runs “start \/max \/wait simtecw.exe”<\/p>\n<\/li>\n

    6. \n

      The start command launches “simtecw.exe”<\/p>\n<\/li>\n

    7. \n

      The start command blocks waiting for “simtecw.exe” to exit<\/p>\n<\/li>\n

    8. \n

      “simtecw.exe” exits<\/p>\n<\/li>\n

    9. \n

      The start command exits<\/p>\n<\/li>\n

    10. \n

      The batch file exits<\/p>\n<\/li>\n

    11. \n

      AlwaysUp detects that the batch file has exited<\/p>\n<\/li>\n

    12. \n

      AlwaysUp restarts the batch file (as configured on the Restart tab<\/a>)<\/p>\n<\/li>\n

    13. \n

      Go to step 3<\/p>\n<\/li>\n<\/ol>\n<\/div>\n

      \nThe end result is that AlwaysUp will run your executable 24\/7, quickly restarting it if it crashes or stops for any reason.\n<\/p>\n

      And you’ll be able to rest assured, knowing that AlwaysUp is on the case!<\/p>\n

      \n
      \n\n\n\n
      More articles about AlwaysUp…<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n