Posted onApril 21, 2018 (Revised December 16, 2019)
I’m running on Windows Server 2016. I have noticed on my most recent install that AlwaysUp doesn’t 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?
— Robert
Hi Robert. There could be many reasons why a generic Windows Service doesn’t start at boot. But when AlwaysUp is involved, the failure is usually because your service/application is trying to start too soon. Here are a couple of reasons why:
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 box and select your service from the list below:
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.
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.
You are running AlwaysUp on a Domain Controller (DC)
Let’s say that your machine is a Domain Controller 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:
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.
General Solution: Delayed Startup on Boot
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.
To delay startup, choose the Automatically, but shortly after the computer boots option on the General tab:
I have tried AlwaysUp to let OneDrive run as a service. Everything works perfectly, but is it possible to create multiple OneDrive services? I have tried it and when I start the second service event logs suggest that the application crashed.
— Bernhard
Hi Bernhard. Here is what we have learned from experimenting with Microsoft OneDrive on our Windows Server 2016 machine:
You can run multiple copies of OneDrive on your PC
We created two user accounts and installed OneDrive in each. Setup went smoothly and both users were able to start OneDrive normally. Here you can see the two copies of the executable running in the Task Manager:
Next, we installed OneDrive as a windows service in one of the accounts. That arrangement worked fine as well, with a copy of OneDrive.exe running in the isolated Session 0 and another in a regular, interactive login session (#3):
Note that we had to turn off the “Stop all copies…” setting on the AlwaysUp Startup tab (to avoid terminating the non-service copy):
But you cannot run multiple copies of OneDrive in one Login Session
When we setup both users to run OneDrive as a windows service, the first copy started but the second one failed. AlwaysUp kept trying to launch OneDrive, but it simply refused to start:
It seems that multiple copies of OneDrive won’t run in Session 0.
Removing AlwaysUp from the equation, we see the same behavior in a regular login session. The first instance of OneDrive started fine, with the usual “clouds” tray icon showing up on the taskbar. However, when we launched a second copy:
A new OneDrive.exe process appeared in Task Manager (in the Details/Advanced tab)
A File Explorer window opened, listing the contents of our OneDrive folder
The new process exited, disappearing from Task Manager
It is very likely that the second copy of OneDrive, on detecting an instance already operating in the same session, sent an “activate yourself” message to the first before promptly quitting. As far as we can tell, this is how the folks at Microsoft have designed OneDrive to work. There is no way around it.
So no, you will not be able to run multiple copies of OneDrive as windows services in Session 0 with AlwaysUp. 🙁
However, all may not be lost, because…
You can run a single OneDrive with two cloud accounts
Instead of running two copies of the OneDrive application, you may be able to serve two online accounts with a single instance of OneDrive.
To set up a second account:
Right-click the OneDrive task tray icon ()and select Settings
In the window that appears, move to the Account tab
Click the Add an account button
Sign in to OneDrive with the email address and password of your second online account:
Click OK to dismiss the settings window and save your changes.
You should now see two OneDrive cloud icons in your task tray. And when you start OneDrive as a windows service with AlwaysUp, both accounts should be synchronized.
Does your old (but important) desktop application need to run all the time?
Should it start immediately after a reboot, even when no one is there to log on and kick it off?
If so, you should consider installing your program as a Windows Service — the technology Microsoft invented to support mission-critical, 24×7 applications. Use a “service wrapper” (like our AlwaysUp) to install your application as a service in 5-10 minutes.
But not all legacy applications will operate smoothly when installed as a service. Here are three questions you should ask to determine if a windows service is a good fit for your situation:
Do you need to see (or interact with) your program while it’s running?
Windows services run in the background. Any windows displayed by a service appear on a “hidden desktop” called Session 0. When your legacy application is running as a service, you will not see its windows on your own desktop.
As a consequence, it doesn’t make much sense to run an intensively interactive application (like a word processor) as a windows service. Indeed, any application that demands your constant attention will be a poor fit. Does yours?
But if you only need to see your application from time to time, a service may still be an option because you can quickly switch to the Session 0 desktop whenever you need to see your application.
Even though there is no taskbar and the usual desktop icons have vanished, we can interact with iTunes just fine in Session 0. For example, we were able to add tracks to iTunes, create a playlist, and even change settings — just as we would if iTunes was running on our regular desktop.
So is occasionally switching to Session 0 good enough for your situation? If not, you should rule out a windows service.
Will your application occasionally prompt for input?
An application that periodically pops up windows and expects you to respond can be a problem when installed as a windows service. Those popups/windows will appear on the Session 0 desktop — effectively hidden from you. You will not know that your program is stuck waiting for you to enter a password or click the OK button!
So a “needy” application is not a great candidate for running in the background as a windows service. Does your legacy application fit the mold?
However, if you only have to get past one or two prompts, our AlwaysUp service wrapper may provide an elegant solution. Simply write an automation script that dismisses the prompt and plug the script into AlwaysUp. This page dives into the details.
For example, when launching iTunes as a service, this error message is the first to appear:
Clicking the “X” in the title bar will expel the window and allow iTunes to start. To achieve the same effect when no one is around to click, we provided this simple one-line script (which sends the “ESC” key to the iTunes window) to AlwaysUp. Now AlwaysUp automatically dismisses the warning on our behalf whenever it appears!
Does your application read from or write to files on a network drive?
Like a regular application, a windows service can access remote/network devices. Permissions are granted based on the account running the service.
However, a service can’t use a mapped drive — at least not without some extra work to explicitly map the drive letter.
So if your legacy application references network files via their full UNC path (like “\\ServerName\ShareName\Path”) it will be fine as a windows service. But if your program uses files via a mapped drive (like “J:\Path”, where J is mapped to “\\ServerName\ShareName\”), a service may not be in your future.
Mapped drives may not be an issue when using AlwaysUp though. Most drives will be mapped and available to your application if you check the “Attempt to automatically reconnect all network drives” box on the Startup tab when configuring your application.
Next step? Try it yourself!
If none of these questions have ruled out your legacy/desktop application, you should go ahead and try it as a windows service. Any service wrapper (like AlwaysUp) will do the trick in a few minutes. What have you got to lose?
Posted onFebruary 14, 2018 (Revised January 7, 2023)
We are currently using AlwaysUp for one of our customers to run Dropbox (inside a terminal server). Lately we have been having an issue where items stop syncing to Dropbox however AlwaysUp says the state is running. In order to get this working again we need to restart the Dropbox service using AlwaysUp. Any support would be appreciated.
Hi Fulton. Based on what we have seen with other customers, these are the likely culprits:
Dropbox is automatically upgrading itself
Dropbox is designed to automatically download and install new versions of itself. This feature does a great job of keeping your software up to date (applying necessary security patches as soon as possible), but it can lead to unexpected behavior when running in a 24×7 environment. What happens if something goes wrong? Suppose there is a “bad build”? And how do we prevent AlwaysUp from launching new copies of Dropbox as it goes up and down while the update is being applied?
This article on Dropbox auto-updates describes a solution. Please review and apply the recommended settings to avoid interruption in the face of automatic updates.
Your Dropbox folder was temporarily inaccessible
Dropbox will stop dead in its tracks if it is unable to access the folder holding shared files. It may throw up a message like this:
Is your Dropbox folder on a network drive? Perhaps there was a problem getting to the network as your machine booted. If that is the case, we recommend setting Dropbox to startup Automatically, but shortly after the computer boots. This will give critical services an extra 1-2 minutes to properly initialize before the software tries to access your network folder.
Dropbox is running into another transient problem
Problems are not limited to network drives. There are a host of other reasons why Dropbox will fail to start properly. These include:
In these situations, Dropbox may be trying to tell you what is wrong. But because it is running in the background as a windows service, you will not see any error popups on your desktop.
When you discover that Dropbox isn’t working, try switching to Session 0 to see if Dropbox is showing an error message:
A helpful error message may indicate how to resolve the problem.
Please be sure to get in touch if none of these tips help your situation!
I’m using ncrack to monitor our network. I recently started running it as a windows service under AlwaysUp. Everything is working perfectly except that sometimes ncrack stops capturing traffic. The CPU goes to zero and nothing else is written to the log files. Is there some way to get AlwaysUp to terminate ncrack and start a fresh instance?
— Michael
Hi Michael. AlwaysUp doesn’t have an “idle CPU” monitor built in, but you can use a Sanity Check Plugin to solve your problem.
What is a “Sanity Check Plugin” you ask?
The Sanity Check feature allows AlwaysUp to detect arbitrary problems with your application running as a windows service. At its heart is a special plugin (a script or executable) that informs AlwaysUp when decisive action — such as restarting your application or rebooting the machine — is necessary. Dig into the technical details at the Sanity Check page.
Our pre-configured CheckForCPUActivity plugin will empower AlwaysUp to restart ncrack if it sits idle for too long. Here is how to set it up:
First, make sure that you have AlwaysUp version 10.2 or later on your machine. That release (from June 2017) introduced important enhancements to the Sanity Check feature.
Select Help > About AlwaysUp… to check what version of AlwaysUp you have installed:
Next, download the CheckForCPUActivity utility from our web site. Save it in your AlwaysUp installation folder, usually C:\Program Files (x86)\AlwaysUp\
Edit your application in AlwaysUp.
Switch to the Monitor tab. Check the Whenever it fails a “sanity check” box and click the triple-dots button:
Working with the “Configure Sanity Check” window that comes up:
In the Run field, enter the following command line:
This will check ncrack for any CPU activity over 60 seconds.
Using the Every controls, specify how often AlwaysUp should inspect ncrack. Every 10 minutes should be sufficient but feel free to tune as you like.
Click the OK button.
And finally, click the Save >> button to record your changes.
With these settings in place, AlwaysUp will launch CheckForCPUActivity every 10 minutes. Each run will watch ncrack for 60 seconds and if no CPU activity is detected over that period, AlwaysUp will restart ncrack.
A note to other customers: This approach will work with any application where minimal CPU usage indicates a failure. The solution presented is not specific to ncrack.
(888) 881-CORE
We are currently using AlwaysUp for one of our customers to run 
