(888) 881-CORE
Errors, Warnings and Information messages that AlwaysUp writes to the Windows Event Log
As is the convention with Windows Services, AlwaysUp reports information, warnings, and errors to the Windows Application Event Log.
That log is accessible through the Control Panel Event Viewer applet.
Each entry is logged on behalf of the related AlwaysUp application. For example, if you have an application called Dropbox, then the Event Log will have entries with Dropbox (managed by AlwaysUpService) as the designated source. The following tables present the various messages that can be logged, along with more detailed information for each situation.
|
Information
|
|
| The service has started. | The AlwaysUp service managing your application started. |
| The service has stopped. | The AlwaysUp service managing your application stopped. |
| The application has been started. | AlwaysUp started your application successfully. |
| The application has been restarted (run #number). | AlwaysUp restarted your application after a failure or a scheduled stop. number indicates how many times your application has been started by AlwaysUp. |
| A system shutdown has been initiated. AlwaysUp will now stop. | Windows notified the AlwaysUp service managing your application that the computer is being shut down. AlwaysUp will stop your application (if necessary) and exit. |
| Run Statistics: ... | This information is used internally by AlwaysUp to generate reports on your application. Please ignore it. |
| Run-Day Statistics: ... | This information is used internally by AlwaysUp to generate reports on your application. Please ignore it. |
| The application will be stopped as scheduled. | AlwaysUp is about to stop your application as specified on the Monitor tab. |
| The computer will be rebooted as scheduled. | AlwaysUp is about to reboot your computer as specified on the Monitor tab. |
| AlwaysUpService will restart the application at time. | The application has stopped and AlwaysUp is noting the time that it will restart the application. This happens when AlwaysUp is configured to restart your application after a delay (on the Restart tab). |
Warnings
|
|
| The application has been non-responsive for longer than number minutes. It will be terminated. | 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). |
| AlwaysUp has detected that the application has stopped. | Your application stopped but AlwaysUp doesn't know why. This message may be generated when application stops in an unpredictable fashion, outside of AlwaysUp. |
| A message box entitled "title" has been dismissed. The message box contained the following text: text. | 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. |
| The application has been using on average number% of the CPU(s) for longer than number minutes. It will be terminated. | Your application has been using too much CPU (as configured on the Monitor tab). AlwaysUp will immediately stop your application and restart it (if so configured). |
| Unable to start the application in session number: Unable to start an internal component in the desired session. It will be started in the console session/session zero. |
AlwaysUp was unable to start your application visibly on your desktop. Your application will run in Session 0, but it will not be visible to you.
This entry in the AlwaysUp FAQ goes over the gory details of Windows sessions. |
| Unable to run the startup program: reason. | AlwaysUp couldn't to run the startup program prior to starting the main application. |
| Unable to set the startup application's priority: reason. It will run at Normal priority. | This is usually due to insufficient permissions of the account specified on the Logon tab. |
| The connection to capture output was terminated prematurely. No additional output will be captured. | 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 capture output to file: reason | Capturing output failed for some reason. Check your settings in that area on the Extras tab. |
| Unable to restrict the application to certain CPUs: reason | 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. | 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. |
The user configured to run your application
(on the Logon tab)
does not have access to the interactive desktop.
Your application will run in Session 0 and you will not see it. |
| The application has failed to stop gracefully and may be forcibly terminated. The following processes may be terminated: executable-name | AlwaysUp signaled your application to stop (using standard Windows functionality) but it did not. AlwaysUp is about to forcibly stop your application and all its sub-applications. |
| The user has logged out of the current session. The application may be closed by Windows. | This warning come up when AlwaysUp is running your application outside of Session 0 and the session closes. AlwaysUp will restart your application in Session 0. |
| Found number instances of executable-name running. They will be terminated. | Before starting your application, AlwaysUp will terminate all other copies of the application (as per the setting on the Startup tab). This message indicates the number of copies found running. |
| Unable to stop all instances of executable-name. | Before starting your application, AlwaysUp will terminate all other copies of the application (as per the setting on the Startup tab). Unfortunetaly AlwaysUp wasn't able to stop all copies of the application running. |
| The application's memory usage of number1 MB exceeds the limit of number2 MB. It will be terminated. | The application is using too much memory (as specified on the Monitor tab). AlwaysUp will stop the application and restart it (if necessary). |
| The application has been using on average number1%% of a CPU for longer than number2 minutes. It will be terminated. | The application is using too much CPU (as specified on the Monitor tab). AlwaysUp will stop the application and restart it (if necessary). |
| The system has resumed from a sleep/hibernate/low-power consumption state. The application will be stopped. | As configured on the Monitor tab, AlwaysUp is stopping the application because the computer has resumed from sleep/hibernation. |
| Failed to send a mail message to address. | AlwaysUp was unable to send an email. Please check your mail server and account settings if this message persists. |
Errors
|
|
| Unable to restart the application: application exited immediately after it was started. | 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 DLL or other configuration problem.
This entry in the AlwaysUp FAQ goes over some potential remedies. Note that the cap on the number of retries can be configured (or disabled entirely) on the Restart tab. |
| AlwaysUp was unable to start the application properly, failing at least number times in number minutes. AlwaysUp will now stop. | 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 guidance in fixing this problem. Note that the cap on the number of retries can be configured (or disabled entirely) on the Restart tab. |