Run Any Program as a Service with AlwaysUp

AlwaysUp Frequently Asked Questions (FAQ) and Answers

Tips for running any application 24/7 as a Windows 8/2012/7/2008/Vista/2003/XP Service with AlwaysUp

FAQ CONTENTS

    General

  1. What is AlwaysUp?
  2. What are Windows Services?
  3. Will AlwaysUp be able to run "MyFavoriteApp.exe" as a Service?
  4. How do I set up my application with AlwaysUp?
  5. Why is AlwaysUp better than placing my program in the Startup Folder?
  6. Why should I use AlwaysUp instead of Srvany?
  7. Why should I use AlwaysUp instead of a Scheduled Task?
  8. How can I start or stop my application from the command line (or a batch file)?
  9. My application doesn't work when I start it from AlwaysUp (but it works fine when I run it normally without AlwaysUp)
  10. My service runs fine when I start it manually, but why doesn't AlwaysUp start it when my computer boots?

  11. How Do I Resolve The Following Errors?

  12. Unable to start the application: "MyApp.exe" exited immediately after it was started
  13. Unable to monitor the application to prevent it closing on log-off

  14. Showing / Hiding Windows

  15. Why don't my application's windows or task-tray icons show up?
  16. Why don't my application's windows show up on my Windows 7/Vista/Server 2008 PC?
  17. How can I prevent my application's windows (or the command prompt window) from showing up on the desktop?

  18. Dismissing Popup Windows

  19. Can I configure AlwaysUp to automatically dismiss popup windows?

  20. Remote Desktop / Terminal Services

  21. Does AlwaysUp work with Remote Desktop / Windows Terminal Services?

  22. Session 0 Isolation

  23. What is Session 0 Isolation?
  24. I hate Session 0 Isolation! How do I get AlwaysUp to automatically start my application in a "regular" user session when my PC boots?

  25. Network / Registry / Log on

  26. I am unable to run my application from a network drive / My application cannot access network drives.
  27. My application cannot access user-level registry settings.
  28. When running as a given user, I get the error "The service did not start due to a logon failure".
  29. Why doesn't AlwaysUp remember my Windows password?
  30. How come my application stops and is restarted when I logoff from the console/main desktop?
  31. How do I get my ODBC/database application to work?
  32. AlwaysUp has been registered but complains that it is not. How do I fix that?

  33. Applications

  34. How do I run my Java application as a Service?
  35. How do I run Outlook as a Service?

  36. Email / SMS / Text Messaging

  37. How do I configure AlwaysUp to send email using my google/gmail account?
  38. How can I get AlwaysUp to send me SMS/Text messages?

  39. Licensing / Upgrading

  40. I recently purchased AlwaysUp but have not received my registration information. What should I do?
  41. My free 30-day trial has expired. Can I have more time to test AlwaysUp?
  42. How is AlwaysUp licensed?
  43. How much does AlwaysUp cost?
  44. Can I buy AlwaysUp with a Purchase Order (PO)?
  45. Why is AlwaysUp so affordable ($49.99)? Some alternatives cost almost $80 per license!
  46. How many applications can AlwaysUp run as a service per machine? Does it cost more to run multiple applications?
  47. Is an OEM version available (so that I can distribute AlwaysUp with my own applications)?
  48. Is a Site license available (so that I can distribute AlwaysUp freely within my organization)?
  49. I would like to buy an OEM or Site license. Can I have a discount based on my previous purchases?
  50. When purchasing AlwaysUp, I am asked for the "10-digit serial number (XXXX-XXXXXX) from the registration window". Where do I find that?
  51. AlwaysUp says I am not registered even though I am. How can I resolve this?
  52. I see that you have a new version available. Do I have to pay to upgrade?
  53. How do I upgrade from a previous version?
  54. How do I move my registered copy of AlwaysUp to another computer?
  55. I re-installed Windows and my registration code is no longer accepted. What should I do?

  56. Compatibility

  57. Does AlwaysUp work with Windows 3.X, 9X or ME? Windows 2000 or NT?
  58. Does AlwaysUp work with Windows Vista?
  59. Does AlwaysUp work with Windows 7 / Windows Server 2008 R2?
  60. Does AlwaysUp work with Windows 8 / Windows Server 2012?
  61. Does AlwaysUp run on 64-bit versions of Windows?

  62. Web Service / Command Line Tools (CLT)

  63. What is AlwaysUp Web Service?
  64. What is AlwaysUp CLT?

  65. For Developers

  66. How can I prevent my application from closing when I logoff?
  67. When I log off & log on my task tray icon disappears. How can I avoid that?
  68. Is there a list of the messages that AlwaysUp may write to the Windows Application Event Log?
  69. Windows Task Manager says that AlwaysUpService.exe generates many page faults! Should I be worried?

  70. Miscellaneous

  71. Does AlwaysUp consume significant resources when monitoring my application?
  72. What is a "Sanity check utility", and why would I use one?
  73. I want my application to run only at scheduled times. How can I use AlwaysUp to do that?
  74. My application does not have enough time to close properly when the computer is being shut down. How can I give it more time?
  75. My virus scanner tells me that AlwaysUp contains the [Some Scary Virus]. Help!
  76. How do I export my application's settings?
  77. How do I move my AlwaysUp applications to another machine?
  78. What does it mean to start my application "Automatically, shortly after the computer boots"?
  79. Why am I automatically logged out of Session 0? How can I stop that?
  80. How do I allow a non-administrative user to start and stop the service created?
  81. Why is AlwaysUp better than starting my application with the Task Scheduler?
  82. How can I install AlwaysUp silently (without any prompts)?
  83. Where can I download old versions of AlwaysUp?

  84. Additional Help

  85. My question has not been answered here. Can you please help?


    AlwaysUp Windows Service: Overview

  1. What is AlwaysUp?

    AlwaysUp is a commercial Windows "Service Wrapper" program that runs your executable, batch file, or shortcut as a Windows Service, monitoring it constantly to ensure 100% uptime. It will automatically restart your application if it crashes, hangs, or uses too much memory, dismiss "Application error" dialogs, and run customized "sanity checks" to ensure that your application is available 24/7. Regular, detailed email from AlwaysUp will alert you of crashes, scheduled restarts and other relevant events.

    AlwaysUp leverages the Windows Services architecture to provide robust, low-level application control in a secure environment. As a Windows Service, your application can start automatically when the computer boots, survive user logons/logoffs, and run entirely in the background without user intervention.


  2. AlwaysUp Windows Service: Overview

  3. What are Windows Services?

    From the Microsoft Developer's Network (MSDN):

    "Microsoft Windows services, formerly known as NT services, enable you to create long-running executable applications that run in their own Windows sessions. These services can be automatically started when the computer boots, can be paused and restarted, and do not [necessarily] show any user interface. This makes services ideal for use on a server or whenever you need long-running functionality that does not interfere with other users who are working on the same computer. You can also run services in the security context of a specific user account that is different from the logged-on user or the default computer account."

    Windows Services were introduced as a part of the Windows NT operating system in the 1990's and are supported on all versions of Windows released after XP (2001).

    To find out more about Windows Services, consult the MSDN Services page or the in-depth technical article, Inside Win32 Services.


  4. AlwaysUp Windows Service: Overview

  5. Will AlwaysUp be able to run "MyFavoriteApp.exe" as a Service?

    Most Windows applications will operate flawlessly as a Windows Service with AlwaysUp. Hundreds of popular applications are supported, like Dropbox, Java, VirtualBox, and Google Drive, but there are some rare exceptions. The best thing to do is to try AlwaysUp for the free 30-day trial period and see if your application performs as expected. If you do encounter a problem please let us know and we will do our best to get you up and running. Furthermore, we are happy to provide explanations or advice, or to make improvements to AlwaysUp to ensure that your application performs as you desire.

    If you do encounter problems, please review this entry to troubleshoot.


  6. AlwaysUp Windows Service: Overview

  7. How do I set up my application with AlwaysUp?

    Setting up your application with AlwaysUp should be very straightforward. Please view our 1-minute video showing how to add the popular Windows Notepad application to see how easy it is!

    And check out our application tutorials showing how to configure popular applications with AlwaysUp, including:

    Dropbox · VirtualBox · Java Applications · Batch Files · MetaTrader · Alpha Five · MAPI
    Outlook 2007 · Tomcat · JBoss · TeamSpeak · VMware Player · Firefox · Python · Nginx
    FishEye · Cute FTP · Perl · Wireshark · HFS · Thunderbird · Ruby · Livedrive · Selenium · Plex
    Google Drive · Fiddler · Netcam · FitNesse · SugarSync · PDFCreator · Gbridge · VBScript
    PowerShell · SkyDrive · Google Chrome · Visual DataFlex · Growl · Tracd · Cubby
    Node.js · Audiogalaxy · SpiderOak · lighttpd · Adobe AIR · Internet Explorer · Kiosks
    iTunes · iCloud Control Panel · Apache Derby · SpeedFan · Play Framework
    Memcached · PuTTY · Sage ACT! Pro · Evernote · Microsoft Access 2007 · Jottacloud
    PHP · Buzof · Apache Solr · XBMC · Apple Safari · SyncToy · WinForms · Syncdocs
    Tonido · SkyDrive Pro · Box Sync · Dart · odrive · OpenOffice · Outlook 2010
    OneDrive · BoxCryptor · Aria2 · WD My Cloud · pyLoad · Excel 2013 · AutoIt Scripts
    Outlook 2013


  8. AlwaysUp Windows Service: Overview

  9. Why is AlwaysUp better than placing my program in the Startup Folder?

    Applications placed in a user's Startup folder are only run when that user logs on. If the user never logs on, the programs there are never started. Thus the Startup Folder is the ideal solution for interactive applications that should start when you log in, for example your webcam software, email client, to-do list, or any other desktop utilities.

    In contrast, AlwaysUp creates a Windows Service and will start your application immediately after your computer boots. No one needs to log on to run your program. This makes AlwaysUp the better choice for applications that must run 24x7 and quickly bounce back from power failures and other unexpected restarts of the PC.

    Furthermore, running your application with AlwaysUp offers a few other advantages:

    1. Crash protection / 100% uptime: If your application terminates for any reason, AlwaysUp will quickly start it again.

    2. Memory & CPU monitoring: AlwaysUp can restart your application if it hogs the CPU, uses too much memory, or hangs. You set the thresholds.

    3. Scheduled restarts: AlwaysUp can restart your application (or reboot your computer) at a "quiet" time to cure memory leaks, etc. and keep your application "fresh" to do its work.

    4. Email alerts: AlwaysUp will notify you by email when your program fails and has to be restarted.

    5. Reports: AlwaysUp will let you know how your application has been performing (CPU, memory, uptime).

    6. Remote access/Web service: Start/stop/manage your application from any web browser with our free add-on, AlwaysUp Web Service.


  10. AlwaysUp Windows Service: Overview

  11. Why should I use AlwaysUp instead of Srvany?

    Srvany is free and functional but it is unsupported and lacks some major features. Our page comparing AlwaysUp and Srvany reviews the details.


  12. AlwaysUp Windows Service: Overview

  13. Why should I use AlwaysUp instead of a Scheduled Task?

    A scheduled task is the perfect choice for running a maintenance script at specific times but it comes up short in 24/7, mission-critical situations better suited to Windows Services. Dig into the details on our page comparing AlwaysUp and Task Scheduler.


  14. AlwaysUp Windows Service: Overview

  15. How can I start or stop my application from the command line (or a batch file)?

    AlwaysUp creates a "true" Windows Service for each of your applications. Like other services, these show up in the Services Control Panel application and can be manipulated with the Windows Net Command.

    If your application is called "Spider" in AlwaysUp, this command will start the service and your application:

              NET START "Spider (managed by AlwaysUpService)"
    
    To stop the service and your application, use:
              NET STOP "Spider (managed by AlwaysUpService)"
    
    Be sure to replace Spider with the name of your application!

  16. AlwaysUp Windows Service: Overview

  17. My application doesn't work when I start it from AlwaysUp (but it works fine when I run it normally without AlwaysUp)

    This can be due to several reasons, the most common of which are:

    • Your application accesses files on one or more network drives. These drives are probably only available in the account that you have logged in to. This entry goes over the problem and solutions.
    • Your application accesses user-specific items from the registry. These items are usually put in place when a user installs a program, and may not be accessible to other users/accounts. This entry goes over the problem and the solution.
    • Your application needs specific environment variables to be set to work properly. These items are usually put in place when a user installs a program, and may not be accessible to other users/accounts. Please configure AlwaysUp (via the Logon tab) to run your application in a user account that has the proper environment variables set.


    A good way to troubleshoot the situation is to set up the Windows Command Prompt (CMD.exe) as a service with AlwaysUp and to try to run your application from the prompt. To do that:

    1. Follow these instructions to setup the Command Prompt with AlwaysUp.
    2. Start the Command Prompt by selecting "Start" from the Application menu (or "Start in this session" if using RDP or on Windows 7/Vista/2008). The Command Prompt window should come up in a second or two.
    3. At the prompt, type in the command line you specified to AlwaysUp to run your application. If your application fails to run, hopefully it will print an error message or give some other indication as to why it fails to operate properly.
    4. Once you are finished troubleshooting, feel free to remove the CMD application by selecting "Remove" from the Application menu.

    Please contact us if you are still having trouble and we will be happy to help.


  18. AlwaysUp Windows Service: Overview

  19. My service runs fine when I start it manually, but why doesn't AlwaysUp start it when my computer boots?

    First, please ensure that your application is set to run "Automatically, when the system boots" and NOT "Manually, from AlwaysUp". This setting is available on the General tab when creating/editing your application.

    As your computer boots, Windows will start your computer's services in sequence, one after another. Some of these are "core" services that provide basic functionality such as file sharing or printing. If your service requires, say, a network connection, then if it attempts to start before the "Workstation" service (which provides basic network connections and communications) it will fail to load.

    If your application depends on having access to the network, make sure that AlwaysUp is configured to start the Workstation service prior to running your application. This setting is available on the Startup tab when creating/editing your application. Other common services that may need to start before your application include Remote Procedure Call (RPC) (which provides the endpoint mapper and other miscellaneous RPC services) and Server (which provides RPC support and file, print,and named pipe sharing). See the Windows Services application (accessible from the Tools menu in AlwaysUp) for the complete list of services.

    If your application uses the network, you can check the "Ensure that the Windows networking components have started" box on the Startup tab instead of specifying the individual dependent services that control the network. Note that this setting is available in AlwaysUp version 6.5 (released in November 2007) and beyond.


  20. AlwaysUp Windows Service: Overview

  21. Unable to start the application: "MyApp.exe" exited immediately after it was started

    AlwaysUp is starting your application but it is exiting soon afterwards (within 1-2 seconds). This probably means that your application does not have access to something that it needs (for example, a network drive or access to the registry), and it closes quickly without doing anything.

    Please see this entry for some tips on how to resolve this problem.

    Also, if you are a developer and have access to the internals of your application then we suggest adding some "print"/debugging statements to the application to reveal why it is exiting early.

    Please contact us if you are still having trouble and we will be happy to help.


  22. AlwaysUp Windows Service: Overview

  23. Unable to monitor the application to prevent it closing on log-off

    This warning message comes up when the "Try to prevent the application from closing when you logoff" option is checked on the Extras tab, but AlwaysUp is unable fulfill that obligation. Non-windows applications, those without a top-level window, and other non-compatible programs will trigger this error. Be sure to test thoroughly and un-check the "Try to prevent..." option if you repeatedly get this error.

    Note that this message:
    • does not mean that your application will close at logoff, just that AlwaysUp was unable to "attach" itself to your application to prevent it if it happens.
    • is merely a warning and is not fatal to AlwaysUp, which will continue to operate normally.


  24. AlwaysUp Windows Service: Overview

  25. Why don't my application's windows or task-tray icons show up?

    This can be due to several reasons:

    1. Your application is not running. Please consult the Processes tab in the Windows Task Manager to ensure that your executable is listed there. (Be sure to check the "Show processes from all users" box on Windows 2008/7/Vista/2003!)

    2. You are using Remote Desktop Connection or Windows Terminal Services to connect to the computer running AlwaysUp. See "Does AlwaysUp work with Remote Desktop / Windows Terminal Services?" for details.

    3. You are running Windows 7, Vista or Windows Server 2008. Please see "Why don't my application's windows show up on my Windows 7/Vista/Server 2008 PC?" for details.

    4. When AlwaysUp has been configured to run as a specific user, your application is not set to be "interactive" (i.e. show task-tray icons and windows) by default. This is a restriction of the Windows Services architecture. AlwaysUp will try overcome these restrictions, but it is not always successful when the account running the application has limited permissions.

      Please ensure that the account specified to AlwaysUp has the following privileges (described in this Microsoft article):

      • Act as part of the Operating System
      • Replace a process level token
      • Adjust memory quotas for a process

      To set them, select "Local Security Settings" from the "Tools" menu in AlwaysUp. This will bring up a new window. Go to "Security Settings > Local Policies > User Right Assignments" on the left and ensure that the account has full rights to the items above.


    5. An administrator has restricted your system so that Windows Services can not show GUI components. This is set via the registry -- see this page on the NoInteractiveServices key for details.


  26. AlwaysUp Windows Service: Overview

  27. Why don't my application's windows show up on my Windows 7/Vista/Server 2008 PC?

    Windows Vista and Windows Server 2008 introduced several changes for Windows Service applications, described in this technical document from Microsoft.

    This video from Microsoft demonstrates how these changes impact Windows Service applications that show a user interface.

    To summarize, these versions of Windows will run all Service applications on an "isolated desktop" called "Session 0". Windows coming from a Service application will no longer normally be shown alongside other windows on your desktop. Whenever a Service application running in Session 0 needs to display a window, the Interactive services dialog detection window may be displayed (after flashing on the taskbar):

    Interactive Services Detection Dialog

    Clicking on the "Show me the message" button will switch you to the isolated Session 0 desktop where you can interact with the Service application. You will be able to switch back to your regular desktop when you are done.

    Applications run as a Service by AlwaysUp are bound by these restrictions. When your computer boots, only Session 0 is available and AlwaysUp will start your application there. Any windows your application needs to show will be displayed on Session 0. Fortunately, this is not the end of the story!

    How to Show Your Windows on Your Desktop

    After logging in, you can instruct AlwaysUp to run your application in the current session/desktop and make its windows and tray icons available to you by selecting "Start <app> in this session" (or "Restart <app> in this session") from the "Application" menu. Note that restarting will temporarily stop your application.

    AlwaysUp will continue to run your application on your desktop until you log out and the session closes, at which point your application is restarted and "returned" to Session 0.

    How to Show Your Application's Tray Icons in Session 0

    Unfortunately tray icons are not visible in Session 0 (there is no taskbar to show them!). Please review this tutorial showing how to run Explorer in Session 0 and show your tray icons.


  28. AlwaysUp Windows Service: Overview

  29. How can I prevent my application's windows (or the command prompt window) from showing up on the desktop?

    By default, AlwaysUp will try to display your application's windows on the desktop. To avoid that, please edit your application's settings and check the "When a user logs on, don't show the application's windows and tray icon (if any)" box on the Logon tab.


  30. AlwaysUp Windows Service: Overview

  31. Can I configure AlwaysUp to automatically dismiss popup windows?

    Yes. AlwaysUp version 6.5 (released in November 2007) can work with popular automation utilities to automatically:

    • dismiss popups/dialogs (such as the error messages unique to your application)
    • fill in forms (such as a prompt for login information),
    • click buttons (such as the common 'are you sure' prompts)
    • perform almost any interactive task that a user sitting at the keyboard would normally have to do.

    If all you need to do is to click a button to dismiss a popup window, then you may use our free ClickButton program. If your window is named "Confirm?" and you wish to click the "Yes" button, then you would specify this command line on the Automate tab when configuring AlwaysUp:
          ClickButton.exe "Confirm?" "Yes"

    For more sophisticated demands, we recommend using the free and powerful AutoIt. Find out about using AutoIt with AlwaysUp, and please contact us if you need help setting up this feature.


  32. AlwaysUp Windows Service: Overview

  33. Does AlwaysUp work with Windows Remote Desktop / Windows Terminal Services?

    Yes, absolutely. AlwaysUp will run your application, but your application's GUI components (e.g. icons and Windows) may not be displayed to users when they start a Remote Desktop / Terminal Services session. This is a function of Remote Desktop / Terminal Services, where each user is assigned her own session and is not by default granted access to the main, "console" session (the desktop that a user sitting before the physical machine will see).

    Windows 2003 (and XP) introduced the ability to access the console desktop when using Remote Desktop / Terminal Services via the mstsc command. See How to Connect to and Shadow the Console Session with Windows Server 2003 Terminal Services for the details. Basically, you should start Remote Desktop from a command prompt by typing "mstsc /console" (or "mstsc /admin" on XP SP3, 7, Vista, or Windows 2008 - Microsoft's explanation).

    Unfortunately, Windows 8/7/Vista and Server 2012/2008 include several "security enhancements" that disallow users from connecting to the "Session 0" desktop where all Windows Service applications are isolated and run by default.

    For technical information on Terminal Services and GUI applications see the Microsoft support article How To Design a Service to Interact with Multiple User Sessions.

    AlwaysUp will allow you to restart your application in your own Remote Desktop / Terminal Services session (so that you can access its windows and tray icon). This may be convenient when you don't have easy access to Session 0 (e.g. on Windows 8/7/Vista and Server 2012/2008).


  34. AlwaysUp Windows Service: Overview

  35. What is Session 0 Isolation?

    Session 0 Isolation (introduced in Windows Vista and present in Windows 8, 7 and Windows Server 2012, 2008) prevents a Windows Service from showing its GUI elements alongside other Windows on a user's desktop. Windows from a Service will only show up on the special, "isolated" Session 0 desktop.

    Whenever a Service application running in Session 0 needs to display a window, the Interactive services dialog detection window may be displayed (after flashing on the taskbar):

    Interactive Services Detection Dialog

    Clicking on the "Show me the message" button will switch you to the isolated Session 0 desktop where you can interact with the Service application. You will be able to switch back to your regular desktop when you are done.

    Fortunately, AlwaysUp is often able to get around the restrictions and run service applications outside of Session 0.


  36. AlwaysUp Windows Service: Overview

  37. I hate Session 0 Isolation! How do I get AlwaysUp to automatically start my application in a "regular" user session when my PC boots?

    When your PC boots, only Session 0 is available and AlwaysUp will run your application there. If you want to start your application in a regular interactive session instead, we suggest that you configure your PC to automatically log in to a designated user account (to create a viable user session) and then have AlwaysUp automatically start your application in that session. Your users can then connect to that session via RDP to see your application's GUI and interact with it normally.

    AlwaysUp 8.5 and later includes native support for automatically logging you in and starting your GUI applications when your PC boots. Simply select "Autologon..." from the "Tools" menu to bring up the Autologon window, enter the credentials of the user to be logged on and check the "Launch all auto-start applications..." checkbox:

    Autologon with AlwaysUp to avoid Session 0 Isolation

    In versions prior to 8.5, where Autologon is not an integrated option, it will take a bit more effort to set this up:

    1. Edit your application in AlwaysUp. On the General tab, change the Start the application setting to Manually, from AlwaysUp.

    2. Activate automatic logon with the free, easy to use Autologon tool from Microsoft. Run the executable and enter the username and password of the user that will be logged on automatically.
      (You can also follow these instructions, or for the more adventurous, manually edit the registry yourself.)

    3. Create a batch file containing the following command:
               "C:\Program Files\AlwaysUp\AlwaysUp.exe" "<Your-App-Name>" -restart-in-current-session
      
      where <Your-App-Name> is the name of your application in AlwaysUp. Be sure to modify the path to the AlwaysUp.exe file if it is installed in a different location!

    4. Instruct Windows to run the batch file when the user logs on. This can be achieved in one of two ways:
      Note that using the scheduled task may be the better choice if you have UAC enabled and running from the Startup folder triggers an elevation prompt that interrupts the action until you intervene.

    Once set up, your PC will boot, log you in, and AlwaysUp will immediately fire up your application in the interactive user session. RDP'ing to the computer as the auto-loogged-in user takes you to the already open session where your application's windows and tray icons are available as normal.


  38. AlwaysUp Windows Service: Overview

  39. I am unable to run my application from a network drive / My application cannot access network drives.

    By default, AlwaysUp runs your application under the LocalSystem account which has restricted network privileges. Indeed, when run under the LocalSystem account, "the service has no network credentials and can only access network resources using a null session" (i.e. a connection that requires no credentials). Furthermore, network shares that are mapped to drive letters for normal users won't usually be available to the LocalSystem account.

    There are a few options for accessing network resources from a service:

    1. Configure AlwaysUp to log in as a specific user that has access to the network and check the "Attempt to automatically reconnect all network drives" flag on the Startup tab. This will allow you to use automatically mapped drives and UNC paths (e.g. \\myserver\data) in your application, but may not allow you to use a mapped drive letter (e.g. N:\) that is not persistent.

      To use any drive letter, explicitly map the drive using the NET USE command before your application starts by specifying it on the Startup tab. For example, to map the N drive to \\myserver\data, create a batch file with the following command:

      		NET USE n: \\myserver\data
      
      and specify that batch file on the Startup tab. Note that you may have to specify a password to the NET command if your environment requires one.

    2. Grant the LocalSystem account access to your network resource, and use the full UNC path (e.g. \\myserver\share1) to the network share in all settings in AlwaysUp (and your application). This Microsoft Support article provides instructions for granting access to "null shares" (i.e. allowing access without credentials) from the machine hosting the share. You will need to have administrative access to the machine hosting the share (i.e. the server) in order to make the changes.
      Note: this is only recommended in secure environments.


  40. AlwaysUp Windows Service: Overview

  41. My application cannot access user-level registry settings.

    By default, AlwaysUp runs your application under the LocalSystem account. In that case, the registry key HKEY_CURRENT_USER is associated with the LocalSystem account -- not any user currently logged in normally/interactively. To access a specific user's profile, AlwaysUp should be configured to run your application as that specific user (by completing the Logon tab when setting up your application).


  42. AlwaysUp Windows Service: Overview

  43. When running as a given user, I get the error "The service did not start due to a logon failure".

    Please ensure that the user has "Log on as a Service" privileges in the "Control Panel > Administrative Tools > Local Security Settings" application:

    Local Security Settings

    By default, no user accounts have the privilege to log on as a service.

    Note that AlwaysUp will automatically try to grant this privilege at installation time, but it is not always successful when the user installing the service has limited permissions.


  44. AlwaysUp Windows Service: Overview

  45. Why doesn't AlwaysUp remember my Windows password?

    When you configure you application to run under a specific user account, your password must be entered each time that you edit the settings in AlwaysUp. This is an important security measure as AlwaysUp does not separately store your password and relies totally upon Windows to authenticate your login information each time you make changes. Rest assured that AlwaysUp has accepted and applied your login details, even though it will say "no password" the next time that you edit the settings.


  46. AlwaysUp Windows Service: Overview

  47. How come my application stops and is restarted when I logoff from the console/main desktop?

    On Windows XP and Server 2003, where Session 0 Isolation is not present, when a user logs off from the console all running applications are notified of the logoff event via the WM_QUERYENDSESSION and WM_ENDSESSION Windows messages. Some applications are written to actively process these notifications and will close all their windows and fully terminate. When that happens, AlwaysUp will detect the termination and may fire up the application again. Note that the Windows Event Logs will contain a record whenever AlwaysUp restarts your application.

    AlwaysUp has an option to prevent the application being managed from closing when a user logs off the computer. Activate it by checking the "Try to prevent the application from closing when you logoff" box on the Extras tab. Note that this feature is only relevant for Windows XP and Windows Server 2003.


  48. AlwaysUp Windows Service: Overview

  49. How do I get my ODBC/database application to work?

    A user-specific ODBC data source (a "user DSN") is only available to the user who created it. To have your application access a user DSN, AlwaysUp should be configured to run your application as the user who created the DSN by specifying his username and password on the Logon tab.


  50. AlwaysUp Windows Service: Overview

  51. AlwaysUp has been registered but complains that it is not. How do I fix that?

    This is most likely because the user set up to run your application (via the Logon tab) doesn't have full access to the AlwaysUp registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Core Technologies Consulting\AlwaysUp. Follow the instructions on this page to grant the user full access to the AlwaysUp registry key.

    Note: The registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Core Technologies Consulting\AlwaysUp on 64-bit versions of Windows as AlwaysUp is a 32-bit application.


  52. AlwaysUp Windows Service: Overview

  53. How do I run my Java application as a Service?

    Please review our tutorial showing how to run any Java executable/application as a Windows Service with AlwaysUp.


  54. AlwaysUp Windows Service: Overview

  55. How do I run Outlook as a Service?

    Please review our tutorial showing how to run Outlook 2007 as a Windows Service with AlwaysUp. The steps there work for Outlook 2003 and 2010 as well.


  56. AlwaysUp Windows Service: Overview

  57. How do I configure AlwaysUp to send email using my google/gmail account?

    To send email from using your gmail account, please specify the following settings (after clicking on the "Configure..." button on the Email tab):

    From Address: your-gmail-user-name@gmail.com
    From: Your name (or anything else you like)
    SMTP Server Name/IP: smtp.gmail.com
    Port: 465
    Check This server requires encryption and select SSL/TLS
    Check This server requires authentication and select "AUTH-LOGIN"
    Login: your-gmail-user-name@gmail.com
    Password: Your gmail password

    Gmail email configuration settings

    Please see this page in the gmail help center for more information on gmail SMTP.


  58. AlwaysUp Windows Service: Overview

  59. How can I get AlwaysUp to send me SMS/Text messages?

    We recommend using one of the many free email-to-SMS gateway services to send email from AlwaysUp directly to your cell phone. Here are a few that we have come across (google will turn up many others):

    1. How to Send Email to SMS Cell Phones, By Carrier
    2. ipipi.com: Signup for free email to SMS Forwarding

    Remember that many cell phone users are charged for incoming SMS messages, so please be polite!


  60. AlwaysUp Windows Service: Overview

  61. I recently purchased AlwaysUp but have not received my registration information. What should I do?

    When you purchase AlwaysUp from one of our payment partners, we are notified of your purchase shortly after your credit card has passed all the necessary checks (to protect you against fraud). This initial process usually takes a few minutes but can take up to 24 hours if the order must be handled manually.

    Once we receive your order, we will send an email to your address specified in the order within 48 hours, but typically within 2-6 hours. Unfortunately though, our message may occasionally fall victim to agressive SPAM filtering and never make to it to you!

    If you have not received the registration email in a timely manner, please feel free to email us (at support@CoreTechnologies.com) or give us a call at (888) 881-CORE/2673 (toll free in the USA) or +1 510 343-3565. Please provide us with an alternate email address if you have one, and a phone number where you can be reached.


  62. AlwaysUp Windows Service: Overview

  63. My free 30-day trial has expired. Can I have more time to test AlwaysUp?

    Sure. Please contact us to request an extension (for another 30 days).


  64. AlwaysUp Windows Service: Overview

  65. How is AlwaysUp licensed?

    AlwaysUp is licensed on a per-machine basis. When you purchase a license, you will send us the unique serial number for your machine and we will respond with the unique registration code that "unlocks" AlwaysUp for that machine. That registration code will not work on a different machine.

    Enterprise, Site and royalty-free OEM licensing, where serial numbers do not need to be managed for each machine, are also options.


  66. AlwaysUp Windows Service: Overview

  67. How much does AlwaysUp cost?

    AlwaysUp costs $49.99 USD for use on a single machine. In volumes of 2-9, the cost falls to $44.99 USD (a 10% discount), and additional discounts kick in if you purchase larger quantities.

    Please see the AlwaysUp licensing page for complete pricing details.

    Click here to Purchase AlwaysUp now!


  68. AlwaysUp Windows Service: Overview

  69. Can I buy AlwaysUp with a Purchase Order (PO)?

    Yes, we will happily accept a purchase order (Net-30 terms) and payment by check. Please contact us to let us know what you need and we will email you an official quote to get the ball rolling.


  70. AlwaysUp Windows Service: Overview

  71. Why is AlwaysUp so affordable ($49.99)? Some alternatives cost almost $80 per license!

    Our company took great pains to price AlwaysUp at a level that would appeal to both the casual/home customer and the business/professional client. $50 is just about right to serve both environments.

    Rest assured that while the price of AlwaysUp is on the low side when compared to competing products, the quality is not! Be sure to try it free for 30 days to find out why our customers tell us that AlwaysUp is more reliable that the rest.


  72. AlwaysUp Windows Service: Overview

  73. How many applications can AlwaysUp run as a service per machine? Does it cost more to run multiple applications?

    A single AlwaysUp installation can run as many applications as you like. There are no restrictions or additional costs to run multiple applications.


  74. AlwaysUp Windows Service: Overview

  75. Is an OEM version available (so that I can distribute AlwaysUp with my own applications)?

    Yes, the full GUI application and more discreet command-line components are all available for OEM use. We offer Limited and Unlimited licenses and distribution is royalty-free. Please consult the AlwaysUp Licensing page for additional details.

     Why purchase AlwaysUp OEM?


  76. AlwaysUp Windows Service: Overview

  77. Is a Site license available (so that I can distribute AlwaysUp freely within my organization)?

    Yes. Site licensing allows you to distribute an unlimited number of licenses of AlwaysUp throughout your organization. Furthermore, there is no need for you to track individual licenses/registration codes and send those to us. Please consult the AlwaysUp Licensing page for additional details.


  78. AlwaysUp Windows Service: Overview

  79. I would like to buy an OEM or Site license. Can I have a discount based on my previous purchases?

    Yes. The discount is based on your specific situation, so please contact us for details.


  80. AlwaysUp Windows Service: Overview

  81. When purchasing AlwaysUp, I am asked for the "10-digit serial number (XXXX-XXXXXX) from the registration window". Where do I find that?

    The registration window is the first window that comes up when you run AlwaysUp without having a license. It will look something like this:

    AlwaysUp Registration Dialog - Windows Service Setup

    From there, click on the "Register Now" button to reveal the 10-digit serial number that you will need to provide when making your purchase:

    AlwaysUp Registration Dialog - Serial Number


  82. AlwaysUp Windows Service: Overview

  83. AlwaysUp says I am not registered even though I am. How can I resolve this?

    If you have gone through the registration process and your code has been accepted, this is probably caused by a lack of rights when accessing the AlwaysUp registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Core Technologies Consulting\AlwaysUp, or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Core Technologies Consulting\AlwaysUp on 64-bit versions of Windows). Please use the "regedit" application to adjust permissions on that key.

    Using regedit:

    1. Navigate to the key on the left-hand side
    2. Right-click on the key and select "Permissions..." to bring up the permissions window
    3. Add the user(s) with full control if necessary

    Please ensure that all accounts using AlwaysUp (including the ones configured to run your application on the Logon tab) have full access to the above registry key.


  84. AlwaysUp Windows Service: Overview

  85. I see that you have a new version available. Do I have to pay to upgrade?

    When you purchase AlwaysUp, your license is valid for any version with the same major version number or the next. For example, if you purchased version 4.0.13.209, you are eligible to use (free of charge) any version 4 or version 5 release, but not a version 6 release.

    As always, those paying to upgrade from a previous version are eligible for a 50% discount. Please make upgrade purchases here.


  86. AlwaysUp Windows Service: Overview

  87. How do I upgrade from a previous version?

    We recommend that you upgrade from a previous version of AlwaysUp in one of two ways:

    1. Uninstall the previous version of AlwaysUp, then install the new. If you take this approach, any applications/services that you have specified in AlwaysUp will be forgotten and you will have to set them up again in the new version. You may also have to re-enter your registration code.

    2. Install the new version without uninstalling the previous, which will preserve all the applications/services that you have configured using AlwaysUp. If you choose this option, you must ensure that all your applications/services managed by AlwaysUp are stopped and that the Microsoft Event Viewer and Services applications are closed prior to installing or else the upgrade may fail. Also, be sure to install in the same directory as the previous installation (by default C:\Program Files\AlwaysUp). You should not have to re-enter your registration code.


  88. AlwaysUp Windows Service: Overview

  89. How do I move my registered copy of AlwaysUp to another computer?

    The registration code that was sent to you will only work on the computer on which you performed the registration process. If you wish to move AlwaysUp to another computer, please send an email to support@CoreTechnologies.com with:

    1. your order number/details
    2. the AlwaysUp-generated serial number of the old/original computer (optional)
    3. the AlwaysUp-generated serial number of the new computer

    We will respond with the new registration code.


  90. AlwaysUp Windows Service: Overview

  91. I re-installed Windows (or upgraded my hardware) and my registration code is no longer accepted. What should I do?

    If your serial number changes, please send an email to support@CoreTechnologies.com with:

    1. the old/original serial number (if available)
    2. the new serial number
    3. your order number/details

    We will respond with the new registration code.


  92. AlwaysUp Windows Service: Overview

  93. Does AlwaysUp work with Windows 3.X, 9X or ME? Windows 2000 or NT?

    AlwaysUp uses the Windows Service components which are only available on NT-based architectures (Windows 8, 7, Vista, XP, 2000, NT and Windows Server 2012 2008, 2003), so Windows 3.X, 9X and ME are not supported.

    Windows 2000 is no longer supported in AlwaysUp version 7 and beyond. The final 2000-compatible release (6.8.5.44) is still available for download and purchase.

    Windows NT is no longer supported in AlwaysUp version 5 and beyond. The final NT-compatible release (4.1.2.119) is still available for download and purchase.


  94. AlwaysUp Windows Service: Overview

  95. Does AlwaysUp work with Windows Vista?

    AlwaysUp Works with Vista

    Yes, AlwaysUp 6.0 (and later) is fully compatible with all editions of Windows Vista and has earned the "Works with Vista" logo from Microsoft. Versions prior to 6.0 are also fully Vista compatible but require AlwaysUp to be run as an administrator or for the User Access Control feature to be disabled to work properly.


  96. AlwaysUp Windows Service: Overview

  97. Does AlwaysUp work with Windows 7 / Windows Server 2008 R2?

    AlwaysUp has been extensively tested and is compatible with all versions of Windows 7       AlwaysUp is fully compatible with Windows Server 2008 R2

    Yes. AlwaysUp works flawlessly with all versions of Windows 7 and Windows Server 2008 R2 and has earned the Compatible with Windows 7 designation and the Works with Windows Server 2008 R2 logo from Microsoft.


  98. AlwaysUp Windows Service: Overview

  99. Does AlwaysUp work with Windows 8 / Windows Server 2012?

    Yes. Microsoft has officially certified AlwaysUp to be compatible with all editions of Windows 8 and Windows Server 2012 (32 & 64-bit):

    AlwaysUp is Windows Server 2012 Certified (32 & 64-bit)       AlwaysUp is Windows 8 Compatible (32 & 64-bit)


  100. AlwaysUp Windows Service: Overview

  101. Does AlwaysUp run on 64-bit versions of Windows?

    Yes. While AlwaysUp is itself a 32-bit application, it installs and works flawlessly on 64-bit versions of Windows 8/7/Vista/XP, and Server 2012/2008/2003. AlwaysUp has no trouble managing native 64-bit applications either.


  102. AlwaysUp Windows Service: Overview

  103. What is AlwaysUp Web Service?

    AlwaysUp Web Service is a free add-on program for AlwaysUp that enables you to control your AlwaysUp-deployed applications from your web browser. It allows you to manage your AlwaysUp applications without having to log on to the host machine.


  104. AlwaysUp Windows Service: Overview

  105. What is AlwaysUp CLT?

    The AlwaysUp Command Line Tools (CLT) package is designed for developers and application integrators looking to discreetly keep their applications available 24x7.

    It delivers the full power and sophistication of the AlwaysUp GUI product, but entirely from the Windows command line. It is most suitable for OEMs.


  106. AlwaysUp Windows Service: Overview

  107. How can I prevent my application from closing when I logoff?

    On Windows XP and Server 2003, when a user logs off from the console all running applications are notified of the logoff event via the WM_QUERYENDSESSION and WM_ENDSESSION Windows messages. By default, Windows will exit your application in response to WM_ENDSESSION events so you must change your code to override that behavior. Here is a sample in MFC/C++:

    BEGIN_MESSAGE_MAP(CMainFrame, CFrameWnd)

        ON_WM_ENDSESSION()

    END_MESSAGE_MAP()

     

    ...

     

    void CMainFrame::OnEndSession(BOOL bEnding)

    {

        // Figure out if logging off

        BOOL bIsLoggingOff = FALSE;

        {

            const MSG* pMsg = GetCurrentMessage();

            if ((pMsg->lParam & ENDSESSION_LOGOFF) != 0)

                bIsLoggingOff = TRUE;

        }

     

        if (bIsLoggingOff) {

            // Avoid the default behavior, which may close our application

            TRACE("Ignoring logoff.\n")

            return;

        }

     

        // Not logging off so proceed with the regular/default

        CFrameWnd::OnEndSession(bEnding);

    }

    Here is some code for C#:

    protected override void WndProc(ref Message m)

    {

            int WM_QUERYENDSESSION = 0x11;

            int WM_ENDSESSION = 0x16;

     

            if (m.Msg == WM_QUERYENDSESSION)

            {

                    m.Result = (IntPtr) 1; // It is ok for Windows to logoff/shutdown

            }

            else if (m.Msg == WM_ENDSESSION)

            {

                    if ((m.lParam & ENDSESSION_LOGOFF) != 0) { // Test if logging off

                            // Logging off

                            m.Result = (IntPtr) 0; // Indicate that we have processed this message

                            return; // Avoid calling base class functionality

                    }

            }

     

            // Process the message normally

            base.WndProc(ref m);

    }

    If this ignore-logoff behavior is not appropriate at all times, you may want to add a command line argument that activates this feature (and pass that argument when you run your application with AlwaysUp).


  108. AlwaysUp Windows Service: Overview

  109. When I logoff & logon my task tray icon disappears. How can I avoid that?

    Windows broadcasts a message to all applications whenever the taskbar is created. You should probably change your application to catch that message and install your tray icons then. This article shows how to do that in MFC/C++ (scroll down to the second question & answer).


  110. AlwaysUp Windows Service: Overview

  111. Is there a list of the messages that AlwaysUp may write to the Windows Application Event Log?

    Yes, the list of error messages logged by AlwaysUp is here.


  112. AlwaysUp Windows Service: Overview

  113. Windows Task Manager says that AlwaysUpService.exe generates many page faults! Should I be worried?

    No. To do its work, AlwaysUp must ask Windows for information on all the processes being run every few seconds. Unfortunately that operation generates a handful of page faults (for the processes not fully mapped into memory management unit), but those are the inexpensive soft page faults that don't hit the disk. So while you will see the number of page faults climbing steadily every few seconds, rest assured that these faults have zero performance impact on your system. They can be safely ignored.


  114. AlwaysUp Windows Service: Overview

  115. Does AlwaysUp consume significant resources when monitoring my application?

    No. The AlwaysUp components that manage and monitor your application are designed to be extremely frugal with machine resources. They almost always consume less than 1% of the CPU, less than 6 MB of RAM, and don't fall victim to the "Memory Growth" characteristic of many applications today.


  116. AlwaysUp Windows Service: Overview

  117. What is a "Sanity check utility", and why would I use one?

    AlwaysUp can periodically run your own custom program (a "Sanity check utility") to check if your application has failed and should be restarted. This capability allows you to extend the monitoring capabilities of AlwaysUp to cover your unique requirements.

    For example, let's say that you use AlwaysUp to ensure that your web server is always running. AlwaysUp will restart the web server when it crashes, but AlwaysUp will not be able to detect more subtle, application-specific failures, such as when the web server has not crashed, but stops serving pages due to some internal error or resource problem. To resolve that second problem, AlwaysUp allows you to "plug in" your own failure detection program; in this case that program would check on the web server and inform AlwaysUp if the server has stopped serving pages. Fundamentally, your code is free to define what failure means.

    As a part of the standard distribution, we provide full source code for a Sanity check utility that, given a host name and port number, detects if a socket could not be opened to that address. It can be used to check if a TCP/IP application is serving clients. The files can be found in the SanityCheck sub-folder where you installed AlwaysUp.

    Our free http-ping utility can also be used to ensure that your web server is available and serving pages when run with AlwaysUp. This batch file will access a given URL and signal AlwaysUp to restart your application when it fails to access the URL. To use the batch file:

    1. Download the http-ping executable and place it in your AlwaysUp installation directory
    2. Download the sanity check batch file and place it in your AlwaysUp installation directory
    3. Open the batch file in a text editor and:
      • specify the URL to your web server (instead of http://localhost:80)
      • if you have not installed AlwaysUp in the default directory (C:\Program Files\AlwaysUp), then modify the path to http-ping.exe accordingly
    4. In AlwaysUp, configure a sanity check on the Monitor tab to periodically check your application:
      • Run: the full path to the batch file (in your AlwaysUp installation directory)
      • Every: 5 minutes, or however often you like

    Additional details on the Sanity check utility are available in the AlwaysUp User Manual and the Sanity Check Plugins page.


  118. AlwaysUp Windows Service: Overview

  119. I want my application to run only at scheduled times. How can I use AlwaysUp to do that?

    AlwaysUp features basic scheduling on the Restart tab, where your application can be set to run every hour, every half-hour, or periodically at your choosing.

    To run your application in a specific time interval, use the built-in Windows Task Scheduler. For example, if your application named MyFavoriteApp in AlwaysUp should only run between 9 AM and 5 PM daily, you will need to set up two daily scheduled tasks -- one to start the service at 9 and another to stop it at 5. Each task should consist of a simple batch file.

    To start the AlwaysUp-created service (and your application), the batch file should contain this command:

              NET START "MyFavoriteApp (managed by AlwaysUpService)"
    
    To stop the service, the batch file should contain this command:
              NET STOP "MyFavoriteApp (managed by AlwaysUpService)"
    
    Be sure to replace MyFavoriteApp with the name of your application!

    This tutorial (with screenshots) and this article describe how to use the Windows Task Scheduler in Windows XP, 2000 and 2003. Consult this page for Windows 7 and later.

    Please let us know if you need help setting this up!


  120. AlwaysUp Windows Service: Overview

  121. My application does not have enough time to close properly when the computer is being shut down. How can I give it more time?

    When shutting down, Windows will wait a few seconds (usually 20) for all services and the applications managed by AlwaysUp to complete. If AlwaysUp is unable to close your application in that time window, then Windows will forcibly terminate AlwaysUp and your application. This may lead to undesirable results.

    Fortunately the wait-time can be increased by editing a setting in the registry. Microsoft's article "How to Increase Shutdown Time for Services to Close Properly" describes how to make the necessary changes.


  122. AlwaysUp Windows Service: Overview

  123. My virus scanner tells me that AlwaysUp contains the [Some Scary Virus]. Help!

    Download3K AntiVirus Report      Softpedia 100% Clean Award      Tested and found to be safe to install      Safe to install

    This is a false alarm. AlwaysUp does not contain any viruses or malware.

    Our software was thoroughly tested before release and has been certified free of all malware by several third parties afterwards. Please click the icons above to see some recent results.

    Please contact us with the details and we will work with the makers of your virus protection software to resolve the issue.


  124. AlwaysUp Windows Service: Overview

  125. How do I export my application's settings?

    To export your application's settings to an XML file, highlight your application in AlwaysUp and select "Export..." from the "Application" menu. You will be prompted to enter the file name in which to save the settings. Note that for security purposes, any passwords you have configured will not be saved in the file.

    You can later import the XML file (by choosing "Import" from the "Application" menu) to re-create your application's setup on any machine with AlwaysUp installed. Exporting and then importing is a good way to copy settings from one machine to another.


  126. AlwaysUp Windows Service: Overview

  127. How do I move my AlwaysUp applications to another machine?

    You can move one or more AlwaysUp applications between computers by first exporting each service to an XML file, then later importing the file on the destination machine.

    To export your application's settings to an XML file, highlight your application in AlwaysUp and select "Export..." from the "Application" menu. You will be prompted to enter the file name in which to save the settings. Note that for security purposes, any passwords you have configured will not be saved in the file.

    You can later import the XML file (by choosing "Import" from the "Application" menu) to re-create your application's setup on any machine with AlwaysUp installed.


  128. AlwaysUp Windows Service: Overview

  129. What does it mean to start my application "Automatically, shortly after the computer boots"?

    If that option is selected on the General tab, Windows will start AlwaysUp and your application after all the "regular" automatic services have been started. In practice, this means that your application will be started 1-2 minutes after the computer has started, while decreasing the initial "mad rush" for resources at boot time.

    This blog entry and this technical article from Microsoft delve into the details.

    Note that this option is only available on Windows 8, 7, Vista and Server 2012, 2008.


  130. AlwaysUp Windows Service: Overview

  131. Why am I automatically logged out of Session 0? How can I stop that?

    When viewing Session 0, Windows will automatically kick you out if you don't move the keyboard or mouse for 1 minute. Unfortunately there doesn't seem to be a way to disable that feature or to extend the period beyond a minute.

    One way to avoid the logoff is to use AlwaysUp to run a utility simulating keyboard or mouse activity in Session 0. We recommend using one of the following non-intrusive applications:

    • Caffeine: Simulates a keypress once every 59 seconds. Note: You must specify the -noicon argument for it to work
    • NoSleep: Prevents the PC from locking by subtlety moving the mouse every 30 seconds

    Be sure to run the utility in the system account by leaving the AlwaysUp Logon tab at the default setting.


  132. AlwaysUp Windows Service: Overview

  133. How do I allow a non-administrative user to start and stop the service created?

    By default, only Administrators will have the rights to manipulate the Windows Service created by AlwaysUp. To allow other users to start and stop the service:

    1. Ensure that your application is stopped in AlwaysUp
    2. Highlight your application in AlwaysUp and select Application > Advanced > Service Security Settings... to open the Service Security Settings window:

      AlwaysUp Service Security Settings Window

    3. Click the Add button and select the non-administrative account

    4. Check the permissions boxes as necessary.


  134. AlwaysUp Windows Service: Overview

  135. Why is AlwaysUp better than starting my application with the Task Scheduler?

    The Windows Task Scheduler is great for running occasional tasks but Windows Services are better suited for applications that must operate closer to 24/7.

    Running your application as a Windows Service with AlwaysUp offers a few distinct advantages:

    1. Control: AlwaysUp creates a regular Windows Service which can be conveniently stopped (or restarted) from the Services control panel applet or from the command line.

    2. Crash protection / 100% uptime: If your application terminates for any reason, AlwaysUp will quickly start it again. The Task Scheduler has some options to do so, but only when your application "fails", which is poorly defined. For example, stopping with a non-zero exit code is not defined as a failure...

    3. Memory & CPU monitoring: AlwaysUp can restart your application if it hogs the CPU, uses too much memory, or hangs. You set the thresholds.

    4. Visibility: Applications started with Task Scheduler may not be visible on any desktop. AlwaysUp gives you several options to interact with your application, even in the face of Session 0 Isolation

    5. Scheduled restarts: AlwaysUp can restart your application (or reboot your computer) at a "quiet" time to cure memory leaks, etc. and keep your application "fresh" to do its work.

    6. Email alerts: AlwaysUp will notify you by email when your program fails and has to be restarted.

    7. Reports: AlwaysUp will let you know how your application has been performing (CPU, memory, uptime).

    8. Remote access/Web service: Start/stop/manage your application from any web browser with our free add-on, AlwaysUp Web Service.


  136. AlwaysUp Windows Service: Overview

  137. How can I install AlwaysUp silently (without any prompts)?

    The AlwaysUp installer is built with the excellent InnoSetup, which supports "silent" or unattended installs via several command line switches.

    We recommend using either:

    AlwaysUp_installer.exe /silent /norestart
    or
    AlwaysUp_installer.exe /verysilent /norestart


  138. AlwaysUp Windows Service: Overview

  139. Where can I download old versions of AlwaysUp?

    While we only support releases with the current major version and the one before, we maintain the following older builds for your convenience:

    The AlwaysUp Version History documents what is new in each release.


  140. AlwaysUp Windows Service: Overview

  141. My question has not been answered here. Can you please help?

    Of course! Please contact us via email or phone or fill in our feedback form and we will get back to you ASAP, within one business day.