{"id":8015,"date":"2019-09-16T13:00:12","date_gmt":"2019-09-16T20:00:12","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=8015"},"modified":"2019-12-16T09:14:29","modified_gmt":"2019-12-16T17:14:29","slug":"fix-service-logon-failure","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/fix-service-logon-failure\/","title":{"rendered":"Q&A: How do I Fix “The service did not start due to a logon failure”?"},"content":{"rendered":"
\"Q&A<\/div>\n
\n  I setup AlwaysUp to run JRiver Media Center<\/a> as a Windows Service but it’s simply not working. I reboot the server every week and every time AlwaysUp says it can’t log on. These errors come up, over and over:<\/p>\n
\"AlwaysUp<\/div>\n

Help!<\/p>\n

— Anonymous<\/p>\n<\/div>\n

Hi — sorry to hear that the service isn’t starting for you!<\/p>\n

From the logs you sent, the key error appears to be this one:<\/p>\n

The service did not start due to a logon failure<\/b><\/p><\/blockquote>\n

Windows is saying that it cannot authenticate your account (the one you specified on the Logon tab in AlwaysUp) so it cannot start the service.<\/p>\n

The failure is probably due to one of three problems. Answer the following questions to find a solution.<\/p>\n

Has your Windows password expired\/changed?<\/h2>\n

If you recently set a new password on your Windows account, the service may be stuck using the old one.<\/p>\n

To update the service’s password:<\/p>\n

    \n
  1. \n

    Edit your JRiver service in AlwaysUp<\/p>\n<\/li>\n

  2. \n

    Switch to the Logon tab<\/p>\n<\/li>\n

  3. \n

    Enter your new password:<\/p>\n

  4. \n

    Save your settings.<\/p>\n<\/li>\n<\/ol>\n

    Reboot your PC and see if JRiver starts automatically. If not, read on to keep troubleshooting.<\/p>\n

    Have you specified a domain account on the AlwaysUp Logon tab?<\/h2>\n

    If your service is running in a domain account, it’s possible that the service is starting too soon — before the primary domain controller<\/a> is ready to accept requests.<\/p>\n

    Indeed, this can easily happen when your computer is the slow-starting domain controller!<\/p>\n

    The fix is to delay the start of the JRiver service, to allow the domain controller enough time to launch and initialize. To do so:<\/p>\n

      \n
    1. \n

      Edit your JRiver service in AlwaysUp<\/p>\n<\/li>\n

    2. \n

      Set the Start the application<\/b> field to Automatically, but shortly after the computer boots<\/b>:<\/p>\n

    3. \n

      Save your settings.<\/p>\n<\/li>\n<\/ol>\n

      Reboot and see if that does the trick!<\/p>\n

      Is your Active Directory Group Policy overwriting the Local Policy setting for the “Log on as a service” right?<\/h2>\n

      This last scenario applies if your system uses Active Directory<\/a> and you have specified a domain account on the AlwaysUp Logon tab.<\/p>\n

      Your Windows account may be losing the right to run as a service when an incomplete group policy<\/a> overwrites the local policy. Basically, your account is “out of sync” with the Active Directory server.<\/p>\n

      The solution is to modify the domain group policy, as outlined in this blog post<\/a>.<\/p>\n

      Still experiencing “logon failure” errors?<\/h2>\n

      If you are still seeing the error, something strange is definitely going on with your setup.<\/p>\n

      Please get in touch<\/a> to schedule a remote session, where we can troubleshoot your misbehaving service. We’ll do our best to have you up and running soon!<\/p>\n