After reactivating with a developer license, newly created instances are invalid

Technical Support
1

OS Name/Version:

Windows Server 2019

Product Name/Version:

AMP Release “Phobos” v2.6.4.2, built 10/12/2025 02:35

Problem Description:

after re-activating my ADS with a developer license so we could experiment with custom and community configurations, any newly created instances fail to start with the error An AMP Developer licence has been specified as the product key without a runtime licence. Please make sure you are activating AMP with a regular product key before adding a developer licence.

Steps to reproduce:

  • Activate ADS with an AMP runtime licence
  • Re-activate ADS with a developer licence
  • create a new instance

Actions taken to resolve so far:

re-activating ADS with the runtime licence fixes the problem, but I shouldn’t have to swap back and forth between licences just to start new instances, especially when ADS and all existing instances know they’re properly activated.

2

You need to change the default key back to a retail key in the configuration.

3

ok, so the correct instructions for applying a developer license are as follows, then:

  1. activate ADS with your retail license
  2. re-activate with developer license
  3. replace the license code in Configuration > Instance Deployment > Deployment Defaults > Licence Key with your retail license again

is that correct?

The link from the developer license email only points to the “Activate AMP with a new licence key” page, which contains no additional details or instructions for developer use-case, which would have been nice to know.