No valid AMP licence was found

  • 159 Views
  • Last Post 09 July 2021
jeffreyrdubois posted this 07 July 2021

I understand this is not an uncommon issue and other people have already posted this but those solutions did not work. I have an isnatnce that will work for about a week and then suddenly not start anymore. The logs show the error

No valid AMP licence was found. Please run `ampinstmgr reactivate Hardpointe` to reactivate this instance

Number 1. Yes, the "New Server Settings" has the correct license key and this key was used when creating the instance.

Number 2. When I run the ampinstmgr reactivate Hardpointecommand I get an error saying I need to stop ADS to do this. I found a post from Mike stating to stop ADS I need to use "ampinstmgr stop ADS" Link to Post except... nope. That gives the error "No instance with name ADS", so.... not sure what happened there....

So with nothing else to do, now I, weekly, create new instances, copy my data over, and then sit around and wait for the license to break again.

Any idea why this is happening?

Order By: Standard | Newest | Votes
Mike posted this 09 July 2021

Having a VPN server on the same machine can cause similar problems. It changes the systems network configuration change.

I'm assuming AMP is running inside a VPS in Unraid because doing otherwise is unsupported.

jeffreyrdubois posted this 08 July 2021

Thanks Mike, I don't mean to make this more confusing but none of that applies to me. This software is running on an unraid server which hasn't turned off in 5 months. The networking remains the same, no VPN (there is a VPN Server but that doesn't touch AMP)

Mike posted this 08 July 2021

The instances deactivate if the hardware profile changes. Common things that cause this:

  • Using WiFi instead of a wired connection.
  • Having VPN software installed such as Tunnelbear, Hamachi, etc. Anything that works by creating a virtual network adapter.
  • Using a USB network adapter, especially if it's plugged into a hub.
  • Physically changing the hardware.

AbhorrentJoel posted this 07 July 2021

I found a post from Mike stating to stop ADS I need to use "ampinstmgr stop ADS" Link to Post except... nope. That gives the error "No instance with name ADS", so.... not sure what happened there....

You need to use the the exact name for the ADS instance. If you run ampinstmgr -l (or ampinstmgr -t for a table), it'll list all the instances. On Linux the ADS instance is called ADS01 by default, while on Windows it is AMPInstance1-ADS.

Close