AMP failing to execute

Last Modified

Tue Mar 13 18:32 GMT 2018

Description

  • Automation Policy failing with: -- Task did not produce any output.

Environment

  • N-able N-central 10.0+
  • Automation Manger

Solution

Problem Source and Identification

One of the reasons this error comes up is a duplicate copy of the Automation Policy causing a conflict when the agent requests the most recent version of an AMP.  To identify the problem, you can look in AutomationManager.log found on the problem device in C:\Program Files (x86)\N-able Technologies\Windows Agent\log or simply in C:\Program Files\N-able Technologies\Windows Agent\log for 32-bit devices.  This log will have an entry that looks something like this: 
[73] 2017-07-03 16:03:05,262 INFO  NCentralAutomation AutomationPolicyExecutor:  Executing policy with ID: 7c016410-0eb6-448b-b842-b6b9737fc398, Params: <xml><Parameters><Parameter ParameterName="Program" Value="C:\program files\atlassian\JIRA\bin\shutdown.bat"/></Parameters></xml>, instance ID: 53e624de-a0eb-4614-b18c-a4dea22cc491
[73] 2017-07-03 16:03:05,262 INFO  NCentralAutomation AutomationPolicyExecutor:  Agent Version: 11.0.1.1043
[73] 2017-07-03 16:03:05,262 INFO  NCentralAutomation AutomationPolicyExecutor:  Automation Manager version: 2.2.0.116
[73] 2017-07-03 16:03:05,262 INFO  NCentralAutomation AutomationPolicyExecutor:  No credentials supplied
[73] 2017-07-03 16:03:05,262 INFO  NCentralAutomation CachedPolicyXmlProvider:  Policy 7c016410-0eb6-448b-b842-b6b9737fc398: local cache contains an oudated version of the policy. Downloading the latest one.
[73] 2017-07-03 16:03:05,449 ERROR NCentralAutomation AutomationPolicyExecutor:  Data provider GET returned: TimeOut

The key line will be the last one: Data provider GET returned: TimeOut
Sometimes this will also be presented as: Data provider GET returned: Failed

In either case this is caused by a duplicate copy of the AMP, likely at another SO or Customer/Site level.  Check the repository for other copies.

Solution and Prevention

If you can find the copy, simply delete one or all copies and upload at the SO level to allow you to use it at all customers.  If you cannot find the copy, the simplest solution is to force the AMP to get a new UUID as follows:
  1. Open the repository via Configuration > Scheduled Tasks > Script/Software Repository at the level where you know at least one version of the AMP exists,
  2. Click Clone on the right-hand side,
  3. Download the clone, delete the recently created clone version, and open the AMP in Automation Manager,
  4. Make any necessary changes, save, and upload from Automation Manager to the N-able N-central server.
This process will produce a new UUID and will allow you to have multiple copies of the same AMP with small differences should it be required.  If this is still not working please feel free to contact support.