Run any application as a Windows Service

AlwaysUp Event Log Messages

The list of Errors, Warnings and Information messages that AlwaysUp can write 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 "MyServer", then the Event Log will have entries with "MyServer (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.

Event Log: Information Messages Information

Message

Details

The service has started. AlwaysUp has started
The service has stopped. AlwaysUp has stopped.
The application has been started. AlwaysUp has started your application
The application has been restarted (run #number). AlwaysUp has restarted your application after a failure or a scheduled stop. number indicates how many times your application has been restarted by AlwaysUp.
A system shutdown has been initiated. AlwaysUp will now stop. AlwaysUp has detected that the computer is being shut down. AlwaysUp will stop your application (if necessary) and itself shut down.
Run Statistics: ... This information is used internally by AlwaysUp to generate reports on your application.
Run-Day Statistics: ... This information is used internally by AlwaysUp to generate reports on your application.
The application will be stopped as scheduled. AlwaysUp is stopping your application as specified on the Monitor tab.
The computer will be rebooted as scheduled. AlwaysUp is rebooting your computer as specified on the Monitor tab.
AlwaysUpService will restart the application at time. AlwaysUp has been configured not to restart your immediately (on the Restart tab) and it is noting the next start time.



Event Log: Warning Messages Warnings

Message

Details

Unable to monitor the application to prevent it closing on log-off: Access is denied. Even though you have configured AlwaysUp to prevent your application from closing when you log off (on the Extras tab), AlwaysUp was unable to "attach" itself to your application to alter its logoff behavior.

AlwaysUp will continue to monitor your application in all other respects but your application may exit when you logoff. If this does happen, don't worry — AlwaysUp will restart it (if so configured).

Unable to monitor the application to prevent it closing on log-off: The application did not permit this functionality. Even though you have configured AlwaysUp to prevent your application from closing when you log off (on the Extras tab), your application will not allow itself to be monitored for log-off. Many applications (especially DOS and older Windows programs) do not permit this functionality.

AlwaysUp will continue to monitor your application in all other respects but your application may exit when you logoff. If this does happen, don't worry — AlwaysUp will restart it (if so configured).

The application has been non-responsive for longer than number minutes. It will be terminated. AlwaysUp has 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 has stopped and AlwaysUp doesn't know why. This message may be generated when you manually close your application (by clicking on the X button), or when your application stops in an unpredictable fashion.
A message box entitled "title" has been dismissed. The message box contained the following text: text. AlwaysUp has 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 show what was presented in 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 and make it visible on your "screen". Your application will run, but it may not be visible to you.

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

Note that this message will only be logged on systems that support multiple sessions (i.e. Vista, Windows 2008/2003, and XP with fast user switching).

Unable to run the startup program: reason. AlwaysUp was unable 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 for the log-on account configured in AlwaysUp.
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. This can happen when the capture text file becomes inaccessible.
Unable to capture output to file: reason Capturing output failed for some reason.
Unable to restrict the application to certain CPUs: reason AlwaysUp was unable to 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 (as specified on the LogOn tab) does not have full access to the registry key. Please grant that user full rights.
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 (as specified on the LogOn tab) does not have access to the interactive desktop, where a different user is probably logged on.

Your application will run but it will be hidden.

The application has failed to stop gracefully and may be forcibly terminated. The following processes may be terminated: executable-name AlwaysUp has signalled 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 whenever a user closes the session where your application is running. AlwaysUp will try to keep your application alive if so configured on the Extras tab.



Event Log: Error Messages Errors

Message

Details

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 will no longer try to restart your application.

Please consult the AlwaysUp FAQ for guidance in fixing this problem.