N-able N-central- AMP Fails - " The Automation Policy you wish to execute was created against an earlier version of Automation Manager and is no longer supported."

Last Modified

Wed Nov 13 19:08 GMT 2019

Description

  • "The Automation Policy you wish to execute was created against an earlier version of Automation Manager and is no longer supported." error.

Environment

  • N-able N-central

Solution

  • There are usually two scenarios where AMPs fail to run post upgrade:
  1. Agent is not on the same version of N-able N-central (ie. N-able N-central was upgraded but the agent was not).
    • What ends up happening is that you have a higher version on the Automation Manager script than what the agent can run, so the AMP errors out.
    • i.e. Version of AMP and Version of Automation Manager on N-able N-central is higher than the version of Automation Manager in the agent software.
    • To resolve this: Make sure the agent is on the same version of N-able N-central.
  2. N-able N-central was upgraded but the AMPs did not upgrade. What ends up happening is that N-able N-central tries to run an older version Automation Policy and errors out because N-able N-central has a newer version of Automation Manager built into the N-able N-central OS.
    • i.e. Version of AMP is lower than the Version of Automation Manager in N-able N-central and the N-able N-central agent.
    • To resolve this:
      1. Open the AMP in Automation Manager Designer.
      2. Make a change to the AMP.
      3. Undo that change to the AMP.
      4. Save the AMP.
      5. Upload the AMP to N-able N-central .