ADS instance not working

  • 99 Views
  • Last Post 07 March 2021
jrsrjrsr posted this 06 March 2021

OS Name/Version: Win 10, 2004 (19041.804)

Product Name/Version: AMP 2.1.0.12

Problem Description:
ADS instance, installed as service, does not appear to start correctly. ampinstmgr -l lists it as running, as does Windows Services tool. However, I cannot reach it via http://localhost:8080 and there is nothing in the logs to indicate that it restarted. The last log entry includes prior shutdown message that does not change after trying to restart the instance/service.

Steps to reproduce / Actions taken to resolve so far:

  • Tried rebooting
  • Tried restarting with ampinstmgr -r AMPInstance1-ADS
  • Tried restarting with Windows Services tool
  • Instance logs do not update, even after changing Monitoring.LogLevel=0
  • Changing Monitoring.ProduceStartupScripts=True in AMPConfig.conf does not create a startup batch file
  • netstat -an | find "LISTENING" does not list anything listening on 8080

Given the above, I feel strongly that it is a startup problem rather than something like a firewall problem. (Also, because things were working before I upgraded everything.)

Any idea how else to troubleshoot this? Is there an easy way to try starting from the command line, given that ProduceStartupScripts=True is not working?

Order By: Standard | Newest | Votes
jrsrjrsr posted this 06 March 2021

I just tried uninstalling as a service and starting manually from command line. This did not fix anything and I see the same behavior.

Mike posted this 06 March 2021

  • Stop the AMP service and configure it to be in "Manual" startup mode via the services control panel
    • Run the Installer in repair mode
    • Reboot the system
    • Run ampinstmgr --nocache upgradeall in a command prompt.
    • Run ampinstmgr startall
    • Re-configure the service to the the "Automatic, delayed start" startup mode.

jrsrjrsr posted this 07 March 2021

Thank you! That help me fixed things, but I had to modify the procedure slightly.

When running ampinstmgr startall as instructed, I received the following message:

[Error] You cannot start instances you do not own as a non-root user. You are jrsrjrsr and this instance belongs to NETWORK SERVICE.
[Error] Do not attempt to change the owner of an instance, this will damage your installation. Switch to the correct user and try again.
[Error] ADS is installed as a service, and as such only ADS may start/stop other instances.

To get the ADS instance kicked off properly, I needed to start the service from Window's Services tool run with administrator privileges. So the steps I needed to take were instead:

  • Stop the AMP service and configure it to be in "Manual" startup mode via the Services control panel
  • Run the Installer in repair mode
  • Reboot the system
  • Run ampinstmgr --nocache upgradeall in a command prompt.
  • Re-configure the service to the the "Automatic, delayed start" startup mode via the services control panel
  • Start the service via the Services control panel
  • Run ampinstmgr startall.

where the Services control panel in the steps above was run with administrator privileges.

Two remaining questions:

  1. Is there a way to do startall that does not produce the error message?
  2. I do not remember the service as being previously installed with "Automatic, delayed start", but rather with "Automatic". Does that matter?

Thank you again for your rapid response. It's great to be up and running again!

jrsrjrsr posted this 07 March 2021

One last thing that is likely important. I do not manage AMP using a separate AMP user as the install guide suggests. Instead I run the software under a normal user and elevate when necessary with Windows UAC using the credentials of an existing user with administrative privileges. (There are a number of reasons why I do not want to create a special AMP user).

I suspect this is the reason I get the error above, whereas others may not.

Close