Run any application as a Windows Service

AlwaysUp Event Log Messages

This page documents the Errors, Warnings and Information messages that AlwaysUp writes to the Windows Event Log when it's running your application as a Windows Service

How AlwaysUp works with the Windows Event Logs

Like other Windows Services, AlwaysUp reports information, warnings, and errors to the Windows Application Event Log. That log is accessible through the Control Panel Event Viewer application.

Each entry is logged on behalf of the related AlwaysUp application. For example, if you have an application called Ollama, then the Event Viewer will show entries with Ollama (managed by AlwaysUpService) in the Source column:

Note that the:

  • Event ID column shows the identifier assigned to the event reported.

  • Task category column displays "AlwaysUp Events" for each entry logged by AlwaysUp, across all applications. Therefore, you can use that value to group all records reported by AlwaysUp.

The following tables present the various messages that can be logged, along with more detailed information for each situation.

Event Log: Information Messages Information messages (Event IDs 100-199)

These are informational messages, intended to keep you up in the loop as AlwaysUp monitors and manages your application. They typically don't require any action.

Message

Event ID

Meaning
The service was installed. 101 An AlwaysUp Windows Service was installed to manage your application.
The service was removed. 102 The AlwaysUp Windows Service managing your application was removed from your computer.
The service has started. 103 The AlwaysUp Windows Service managing your application started.
The service has started (at boot). 103 When your computer booted, Windows automatically started the AlwaysUp Windows Service managing your application.
The service has stopped. 104 The AlwaysUp Windows Service managing your application stopped.
The application was started in Session session-number. 105 AlwaysUp started your application successfully in the specified session.
The application was started in Session session-number with restricted rights. 105 AlwaysUp started your application successfully in the specified session, with admin rights removed.
The application has been restarted (run #run-number) in Session session-number. 106 AlwaysUp restarted your application after a failure or a scheduled stop. run-number indicates how many times your application has been run since the AlwaysUp Windows Service managing your application started.
The application was stopped. 107 AlwaysUp stopped your application.
Updated. 108 Your application was edited in AlwaysUp and changes were saved.
Updated (startup type). 108 The startup type was changed from the AlwaysUp desktop program.
Updated (tag(s) added). 108 The AlwaysUp desktop program added one or more tags to your application.
Updated (tag(s) removed). 108 The AlwaysUp desktop program removed one or more tags from your application.
Updated (service security). 108 The rights and permissions associated with the AlwaysUp Windows Service managing your application were modified from the AlwaysUp desktop program.

For example, the right for a non-admin user to start the service could have been granted.

AlwaysUpService will restart the application at time. 109 The application has stopped and the AlwaysUp Windows Service is noting the time that it will restart the application. This event is reported when AlwaysUp is configured to restart your application after a delay (on the Restart tab).
Run Statistics: metrics 110 This information is used internally by AlwaysUp to generate performance reports for your application. Please ignore it.
Run-Day Statistics: metrics 110 This information is used internally by AlwaysUp to generate performance reports for your application. Please ignore it.
A system shutdown was initiated. AlwaysUpService will now stop. 111 Windows notified the AlwaysUp Windows Service managing your application that the computer is being shut down. AlwaysUp will stop your application and exit.
The application will be stopped as scheduled. 112 The AlwaysUp Windows Service is about to stop your application as specified in the Every section of the Monitor tab.
The computer will be rebooted as scheduled. 113 The AlwaysUp Windows Service is about to reboot your computer as specified in the Every section of the Monitor tab.
Start requested. 114 The AlwaysUp desktop program made a request to start the AlwaysUp Windows Service managing your application.
Start requested (NET START, user). 114 The AlwaysUp Windows Service managing your application was asked to start by the NET START command. The user running the command is noted.
Start requested (SC START, user). 114 The AlwaysUp Windows Service managing your application was asked to start by the SC START command. The user running the command is noted.
Start requested (likely from Services.msc, user(s)). 114 A request was made to start the AlwaysUp Windows Service managing your application, probably from the built-in Services utility. The users running the Services utility on the computer at the time of the request are noted.
Stop requested. 115 The AlwaysUp desktop program made a request to stop the AlwaysUp Windows Service managing your application.
Stop requested (NET STOP, user). 115 The AlwaysUp Windows Service managing your application was asked to stop by the NET STOP command. The user running the command is noted.
Stop requested (SC STOP, user). 115 The AlwaysUp Windows Service managing your application was asked to stop by the SC STOP command. The user running the command is noted.
Stop requested (likely from Services.msc, user(s)). 115 A request was made to stop the AlwaysUp Windows Service managing your application, probably from the built-in Services utility. The users running the Services utility on the computer at the time of the request are noted.
Restart requested. 116 The AlwaysUp desktop program made a request to restart the AlwaysUp Windows Service managing your application.
Remove requested. 117 The AlwaysUp desktop program made a request to remove the AlwaysUp Windows Service managing your application.
Detach requested. 118 The AlwaysUp desktop program made a request to detach — stop the AlwaysUp Windows Service but leave the application running.
Sent an email to address. 119 The AlwaysUp Windows Service managing your application sent an email to the address mentioned.
It appears that OneDrive was automatically updated. Please visit the OneDrive release notes page for additional information: URL. 100 While running OneDrive as a Windows Service, AlwaysUp detected that an automatic update was applied.

AlwaysUp restarted OneDrive, to monitor it closely and keep it running continuously in the background.

Visit the URL to find out what versions of OneDrive are currently rolling out.


Event Log: Warning Messages Warning messages (Event IDs 200-299)

These are important messages that describe a specific problem or inconvenience. They likely deserve your attention but may not require any action.

Message

Event ID

Meaning
AlwaysUpService detected that the application has stopped. 201 Your application stopped but AlwaysUp doesn't know why.

This message is reported when your application stops in an unpredictable fashion, outside of AlwaysUp.
The system has resumed from a sleep/hibernate/low-power consumption state. The application will be stopped. 202 As configured on the Monitor tab, AlwaysUp is stopping the application because the computer has resumed from sleep/hibernation.
The application has been non-responsive to the operating system for longer than number minutes. It will be terminated. 203 AlwaysUp detected that your application has not been responding to Windows for a while (as configured on the Monitor tab).

This usually means that your application is hung or frozen.

AlwaysUp will immediately stop your application and restart it (if so configured).

The application has been running for longer than number minutes. It will be terminated. 204 As configured on the Monitor tab, AlwaysUp is stopping the application because it has been running too long.
Unable to access executable/application (path). The service will be installed but cannot run until the executable is in place. 205 This message is reported when you add your application to AlwaysUp but the application path you specified isn't accessible.
Found number instances of executable-name running. They will be terminated. 206 Before starting your application, AlwaysUp will terminate all other copies of the application found running on the computer (as instructed on the Startup tab). This message notes the number of copies found running.
Found number instances of executable-name running in this session or account. They will be terminated. 206 Before starting your application, AlwaysUp will terminate all other copies of the application found running in the same session or account (as instructed on the Startup tab). This message notes the number of copies found running.
Unable to stop all instances of executable-name: reason. 206 Before starting your application, AlwaysUp will terminate all other copies of the application found running in the same session or account (as instructed on the Startup tab).

Unfortunately AlwaysUp failed to stop all copies of the application running on your computer.

Unable to set the application's priority: reason. It will run at Normal priority. 207 Even though you instructed AlwaysUp to adjust your application's priority on the General tab, AlwaysUp failed to do so.

The most common reason for this problem is a lack of permissions. Is the user specified on the Logon tab an administrator? If not, several operations might fail.

Unable to set the startup application's priority: reason. It will run at Normal priority. 207 Even though you instructed AlwaysUp to adjust your application's priority on the General tab, AlwaysUp failed to do so.

The most common reason for this problem is a lack of permissions. Is the user specified on the Logon tab an administrator? If not, several operations might fail.

Unable to capture output to file: reason. 208 Capturing the textual output from your application failed for some reason. Check your settings in that area on the Extras tab.

The most common reason for this problem is a lack of permissions. Is the user specified on the Logon tab an administrator? Does that account have permission to write to the file system?

The connection to capture output was terminated prematurely. No additional output will be captured. 208 AlwaysUp was interrupted by the operating system while capturing output from your application (as specified on the Extras tab). This can happen when the capture text file becomes inaccessible.
Unable to restrict the application to specific CPUs: reason. 209 AlwaysUp couldn't specify the CPUs on which to run the application (as configured on the Extras tab).
Unable to access the registry key to validate licensing. Please ensure that this user has access to registry-key. 210 The user configured to run your application (on the Logon tab) does not have full access to the registry key.

Please grant that user full rights to the key, as described in the AlwaysUp FAQ.

Unable to acquire access to the interactive desktop: reason. The application's windows (and any task-tray icons) may not be visible. 211 The user configured to run your application (on the Logon tab) does not have access to the interactive desktop.

Your application will run in the background in Session 0 and you will not see it.
Unable to ensure that networking components are running: reason. AlwaysUpService will pause for a few seconds and try again. 212 Even though you've instructed AlwaysUp to ensure that the Windows networking components have started (on the Startup tab), that operation failed.

The most common reason for this problem is a lack of permissions. Is the user specified on the Logon tab an administrator? That user may not be able to open the, LanmanWorkstation, Netman or RpcSs services.

This article discusses the problem — and couple ways to eliminate it.

Unable to automatically restore the following network drive: drive-letter. 213 AlwaysUp failed to automatically remap the drive. It may not be available to your application.
The application has failed to stop gracefully and may be forcibly terminated. The following processes may be terminated: executable-name(s). 214 AlwaysUp signaled your application to stop (using standard Windows functionality) but it did not comply.

AlwaysUp is about to forcibly stop your application and all the processes it launched.

Unable to locate the AutoIt program (AutoIt3.exe). Unable to run the AutoIt script. 215 This problem comes up when you've specified an AutoIt script (*.au3) on the Automate tab but AlwaysUp cannot determine where AutoIt is installed.

To eliminate the dependency on AutoIt and resolve this issue, please:

  1. Compile your AutoIt script to standalone executable;
  2. Specify that executable on the Automate tab (instead of your AutoIt script).
"Unable to generate an activity report: reason. 216 AlwaysUp failed to read the Windows Event Logs and create a HTML report of your application's activities.
Unable to suspend the computer: reason. 217 AlwaysUp failed to place the computer in a sleep/low power state until the next run of the application.
Trouble setting Dropbox environment variables: reason. 218 AlwaysUp failed to set the Dropbox-specific environment variables required for synchronizing files in the background.
Unable to start the application with restricted rights. 219 AlwaysUp failed to strip away all admin-level rights before starting the application. It will run with whatever rights are granted to the user specified on the Logon tab.
Failed to reset the idle timer to prevent the computer from going to sleep: reason. 220 AlwaysUp failed to inform the operating system that it's in use, thereby preventing the system from entering sleep or turning off the display while the application is running.
Unable to start advanced application monitoring: reason. 221 AlwaysUp features advanced support for many popular applications. This message indicates that AlwaysUp recognized that you're running a supported application, but there was a problem setting up the advanced features.
A message box entitled "title" was dismissed. The message box contained the following text: text. 222 AlwaysUp detected and dismissed a Windows error message box that may prevent your application from exiting after a crash, or a "debug" window that holds up your application. The title and text record the content of the message box.
Unable to dismiss a message box of type type: reason. 223 Despite using conventional Windows methods, AlwaysUp failed to close the message box described.
A fatal message box was dismissed. The application will be stopped. 224 AlwaysUp closed a fatal message box — a window that indicates that the application has failed.

You may see this warning when you've instructed AlwaysUp to stop your application when a serious message box is encountered. That option is available on the Extras tab.

For example, any message box titled "Microsoft Visual C++ Runtime Library" is considered fatal. "Run-time error" popups are classified as serious as well.

The sanity check was inconclusive. 225 AlwaysUp ran the sanity check configured to verify the state of your application. However, there was a problem running the check and no action was taken.
The application's memory usage of number1 MB exceeds the limit of number2 MB. It will be terminated. 226 The application is using too much memory (as specified on the Monitor tab).

AlwaysUp will stop the application and restart it if so configured.

The application has been using on average number% of the CPU(s) for longer than number minutes. 227 Your application has been using too much CPU (as configured on the Monitor tab).

AlwaysUp will stop the application and restart it if so configured.

The user has logged out of the current session and the application may have been closed by Windows. AlwaysUpService will restart it in Session 0. 228 This warning is reported when AlwaysUp is running your application in a user's session and that user logs off.

AlwaysUp will restart your application in Session 0.

Unable to react to the system resuming: reason. 229 This warning is reported if there's a problem when resuming from a sleep/hibernate/low-power consumption state.
Trouble starting in the autologon session: reason. 230 There was a problem finding the session created by Windows automatic logon. The most common cause is that automatic logon didn't work.

Please confirm that automatic logon configured properly — perhaps with the help of Microsoft's free Autologon utility.

Unable to start the application in Session number. It will be started in Session 0. 231 AlwaysUp was unable to start your application visibly on your desktop. Your application will run in Session 0, but it will not be visible.

This entry in the AlwaysUp FAQ goes over the gory details of Windows sessions.

Unable to find the interactive session for user name. The application will be started in Session 0. 231 AlwaysUp was unable to start your application visibly on your desktop. Your application will run in Session 0, but it will not be visible.

This entry in the AlwaysUp FAQ goes over the gory details of Windows sessions.

Failed to send a mail message to address: reason. 232 AlwaysUp was unable to send an email.

Please check your mail server and account settings.

The sanity check failed. The application will be stopped. 233 AlwaysUp ran the sanity check configured to verify the state of your application. It failed, so AlwaysUp intends to stop the application.
The sanity check command failed with code 1. The application will be terminated. 233 AlwaysUp ran the custom sanity check configured to verify the state of your application. It returned 1, which signaled AlwaysUp to stop (and restart) the application.
The sanity check command failed with code 10. The computer will be rebooted. 233 AlwaysUp ran the custom sanity check configured to verify the state of your application. It returned 10, which signaled AlwaysUp to restart the computer.
The sanity check command failed with code 100. The service will be stopped. 233 AlwaysUp ran the custom sanity check configured to verify the state of your application. It returned 100, which signaled AlwaysUp to stop the Windows Service managing your application.
The sanity check command failed with code code. Since this is not a fatal result, the application has not been terminated. 233 AlwaysUp ran the custom sanity check configured to verify the state of your application. It returned an unrecognized exit code and AlwaysUp took no action.
Dropbox has no network connections to the cloud. It may not be synchronizing your files. 200 While running Dropbox as a Windows Service, AlwaysUp detected that the software has no open network connections to its cloud servers.

Note that this may be a temporary situation and Dropbox may eventually reopen its network connections. However, your files will not be synchronized while Dropbox is in this "disconnected" state.

Dropbox is showing a prompt titled title. It may not be synchronizing your files. 200 While running Dropbox as a Windows Service, AlwaysUp detected that the software is showing a popup.

And it seems that Dropbox is stuck waiting for you to respond to the prompt. That can happen when Dropbox isn't set up properly — or after it's been auto-updated and needs some input from you.

Please stop Dropbox in AlwaysUp and start it normally on your desktop. Ensure that Dropbox is configured properly and synchronizes your files before restarting it under AlwaysUp.

OneDrive has no network connections to the cloud. It may not be synchronizing your files. 200 While running OneDrive as a Windows Service, AlwaysUp detected that the software has no open network connections to its cloud servers.

Note that this may be a temporary situation and OneDrive may eventually reopen its network connections. However, your files will not be synchronized while OneDrive is in this "disconnected" state.

OneDrive is showing a prompt titled title. It may not be synchronizing your files. 200 While running OneDrive as a Windows Service, AlwaysUp detected that the software is showing a popup.

And it seems that OneDrive is stuck waiting for you to respond to the prompt. That can happen when OneDrive isn't set up properly — or after it's been auto-updated and needs some input from you.

Please stop OneDrive in AlwaysUp and start it normally on your desktop. Ensure that OneDrive is configured properly and synchronizes your files before restarting it under AlwaysUp.


Event Log: Warning Messages Error messages (Event IDs 300-399)

These are important messages reporting serious issues that demand your attention.

Message

Event ID

Meaning
Unable to start: reason. 301 The AlwaysUp Windows Service managing your application failed to start. This can happen when the 30-day trial has expired, required files are missing, or when specific registry keys are inaccessible.
AlwaysUpService is unable to start because a required file is missing. Please re-install AlwaysUpService. 301 As recommended, please re-install the software.

If the problem persists, perhaps your antivirus package is blocking access to the files. Please investigate there.

Unable to reboot the computer: reason. 302 AlwaysUp failed to reboot the computer. That can happen when you've configured:
  1. A scheduled reboot on the Monitor tab; or
  2. A sanity check that instructed AlwaysUp to restart the computer.

The most common reason for this problem is a lack of permissions. Is the user specified on the Logon tab an administrator? Is that user allowed to restart the computer?

Unable to run the startup program: reason. 303 AlwaysUp failed to run the startup program prior to starting the main application.
After several attempts, AlwaysUpService failed to terminate the application. AlwaysUpService will keep trying for an additional 60 seconds. 304 This problem can occur when the application refuses all attempts to stop. As mentioned, the AlwaysUp Windows Service will keep trying for a while.
After all attempts, AlwaysUpService has failed to terminate the application. AlwaysUpService will now stop. 304 This problem can occur when the application refuses all attempts to stop. The AlwaysUp Windows Service will stop and leave the application running.
AlwaysUp was unable to start the application properly, failing at least number times in number minutes. 305 AlwaysUp tried repeatedly to start your application but it kept failing. AlwaysUp has given up and will no longer try to restart your application.

Please consult the AlwaysUp FAQ for help fixing this problem.

Note that the cap on the number of retries can be configured (or disabled entirely) on the Restart tab.

Unable to start the application: reason. 306 AlwaysUp tried to start your application but it failed to do so.

This entry in the AlwaysUp FAQ goes over potential remedies.

Unable to restart the application: reason. 306 AlwaysUp tried to restart your application but it failed to do so.

This entry in the AlwaysUp FAQ goes over potential remedies.

Unable to restart the application: application exited immediately after it was started. 306 AlwaysUp tried to restart your application but it failed to do so.

The application exited within a second or two of AlwaysUp starting it, which may indicate a missing resource or configuration problem.

This entry in the AlwaysUp FAQ goes over potential remedies.

Note that the cap on the number of retries can be configured (or disabled entirely) on the Restart tab.

Home  | Products  | Support  | Company  | Privacy Policy  | Site Map
Run Application as Windows Service  | Auto-restart Windows Services  | Srvany vs. AlwaysUp  | AlwaysUp FAQ
How to Run Popular Applications as Windows Services  | Windows Services FAQ

Copyright © 2004-2026 Core Technologies Consulting, LLC
7028-B Thornhill Drive, Oakland CA 94611, USA
Phone: +1 (510) 343-3565  |  FAX: +1 (208) 979-1109