{"id":4694,"date":"2018-04-21T21:01:07","date_gmt":"2018-04-22T04:01:07","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=4694"},"modified":"2019-12-16T09:13:03","modified_gmt":"2019-12-16T17:13:03","slug":"start-app-at-boot","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/start-app-at-boot\/","title":{"rendered":"Q & A: What Setting will Help AlwaysUp Start my App at Boot?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I\u2019m running on Windows Server 2016. I have noticed on my most recent install that AlwaysUp doesn\u2019t start at boot, I have to do an interactive\/RDP login and then open the AlwaysUp GUI to have the services started. Is there any setting that I need to change to make this happen please? <\/p>\n

— Robert<\/p>\n<\/div>\n

\nHi Robert. There could be many reasons why a generic Windows Service doesn’t start at boot<\/a>. But when AlwaysUp is involved, the failure is usually because your service\/application is trying to start too soon<\/b>. Here are a couple of reasons why:<\/p>\n

    \n
  1. \n

    Your application depends on a Windows Service<\/b><\/h2>\n

    System software will often be deployed as a windows service. Notable examples include the Apache web server<\/a>, the MySQL relational database<\/a> and the Redis memory store<\/a>.<\/p>\n

    If your application depends on a service, then you should configure the dependency on the Startup tab. Check the Ensure that the following services have started<\/b> box and select your service from the list below:<\/p>\n

    \"Set<\/a><\/div>\n

    However, this setting may not work as expected. While it ensures that the critical service has started before AlwaysUp launches your application, there is no guarantee that the service will actually be ready<\/i>. <\/p>\n

    For example, suppose the Redis service takes a minute to initialize before connections are accepted. If your application tries to start before those 60 seconds have elapsed, it will fail to connect to Redis and will likely crash or exit with an error.\n<\/li>\n

  2. \n

    You are running AlwaysUp on a Domain Controller (DC)<\/b><\/h2>\n

    Let’s say that your machine is a Domain Controller<\/a> and you have specified a domain account on the AlwaysUp Logon tab. If Windows tries to kick off AlwaysUp before the DC is fully ready, the AlwaysUp service will fail to start because it can’t log in. You will see a cryptic message like this in the Windows\/Application section of the Event Log<\/a>:<\/p>\n

    \"Windows<\/a><\/div>\n

    To resolve this scenario, add a dependency on the “Workstation” service on the AlwaysUp Startup tab. Some customers have had success with that change but it hasn’t worked for others.\n<\/li>\n<\/ol>\n

    General Solution: Delayed Startup on Boot<\/b><\/h2>\n

    Irrespective of the underlying problem, many customers have profited from a simple solution: delaying the startup of your AlwaysUp application. Your application is very likely to start properly once it avoids the “mad rush” of programs straining to start as your PC comes alive.<\/p>\n

    To delay startup, choose the Automatically, but shortly after the computer boots<\/b> option on the General tab:<\/p>\n

    \"Delay<\/a><\/div>\n

    With that modification, your application will start 1-2 minutes after your computer boots<\/a> — when all critical components should be happily running.<\/p>\n

    Hopefully this easy change will do the trick. Please be sure to get in touch<\/a> if the problem persists!<\/p>\n