{"id":1040,"date":"2014-12-01T06:00:27","date_gmt":"2014-12-01T14:00:27","guid":{"rendered":"http:\/\/www.coretechnologies.com\/blog\/?p=1040"},"modified":"2021-09-04T12:47:42","modified_gmt":"2021-09-04T19:47:42","slug":"troubleshoot-alwaysup-command-prompt","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/troubleshoot-alwaysup-command-prompt\/","title":{"rendered":"AlwaysUp not Starting your Application? Troubleshoot with the Command Prompt"},"content":{"rendered":"

\nIf you find that your application is starting and then quickly stopping when you run it with AlwaysUp, your application may be trying to report an error message that you simply cannot see. In this situation, we recommend starting your application from a command prompt running as a service, to find out if something useful is being written to the console.\n<\/p>\n

How to start CMD.EXE as a service on your desktop<\/b><\/h2>\n
    \n
  1. \n

    \nHighlight your troublesome application in AlwaysUp and select Add Copy…<\/b> from the Application<\/b> menu.\n<\/p>\n

    \n(In this guide, our “StartServer” batch file is failing for some unknown reason so we’ll work with that entry…)\n<\/p>\n

    \"Add<\/a><\/p>\n

    \n<\/li>\n

  2. \n

    \nIn the Add Application<\/b> window that comes up:\n<\/p>\n

      \n
    1. \n

      \nIn the Application<\/b> field, enter the full path to the windows command prompt. This is:<\/p>\n

      C:\\Windows\\System32\\cmd.exe<\/b><\/p><\/blockquote>\n<\/li>\n

    2. \n

      \nIf there is anything in the Arguments<\/b> field brought over from the application you copied, please remove it.\n<\/p>\n<\/li>\n

    3. \n

      \nChange the Name<\/b> field to something meaningful. We have entered “CMD Testing” in this guide.\n<\/p>\n<\/li>\n

    4. \n

      \nSet the Start the application<\/b> field to Manually, from AlwaysUp<\/b>. We don’t want this command prompt service to start automatically at boot.\n<\/p>\n<\/li>\n<\/ol>\n

      \"Command<\/a><\/p>\n

      \n<\/li>\n

    5. \n

      \nIf you have specified a user on the Logon<\/b> tab, switch over there and re-enter the password (a security measure).\n<\/p>\n

      \"Command<\/a><\/p>\n

      \n<\/li>\n

    6. \n

      \nThose are all the changes we need to make so click the Save >><\/b> button to record your new service. It will show up on the AlwaysUp console soon.\n<\/p>\n

      \"Command<\/a><\/p>\n

      \n<\/li>\n

    7. \n

      \nNext, start the new CMD service on your desktop by selecting Application > Start “CMD Testing” in this session<\/b>:\n<\/p>\n

      \"Start<\/a><\/p>\n

      \nIn a few seconds, the familiar black box will pop up on your desktop:\n<\/p>\n

      \"Command<\/a><\/p>\n

      \n<\/li>\n

      <\/a>
      \n      <\/a><\/p>\n

    8. \n

      \nAnd finally, in the command box, type in the full command line you gave to AlwaysUp — application & arguments<\/u><\/b>. Be sure to specify the exact values that you had supplied to your AlwaysUp service! Please cut & paste to ensure accuracy.\n<\/p>\n

      Hit Enter to run your application and pay special attention to what is written to the command prompt.<\/p>\n<\/li>\n

      \nHopefully at this point your application will tell us what is wrong! In our case (pictured below), the batch file can’t find the JAR file it is expecting…\n<\/p>\n

      \"Command<\/a><\/p>\n

      Resolving the problem<\/b><\/h2>\n

      Common errors include:<\/p>\n