Article ID: 116356, created on Jun 28, 2013, last review on Nov 17, 2014

  • Applies to:
  • Operations Automation

How to classify a problem as an APS package's

The most common APS-related problems are listed below.

Problem 1 - failed task of an APS application in Parallels Operations Automation (POA) Task Manager.

Several things are true:

  1. The task 'executing configuration script' fails because of a non-zero exit code of an APS application configuration script.

  2. All settings' environment variables of the service instance are filled properly in the task's parameters:

    • Visible settings are the same as in the POA interface

    • Hidden settings are filled
  3. The interpreter of a configuration script (usually PHP):

    • Is the same as defined in the APS package in the 'script-language' element in the APP-META.xml file in an application

    • Satisfies the version of the language defined in the requirements

    • Satisfies the set of modules defined in the requirements
  4. If an application has the 'External system' Provisioning Type and external host(s) defined in the global settings of the application resource type in POA are accessible from Internet, the host(s) are accessible from the application's Provisioning Gateway too.

  5. If an application has the 'External system' Provisioning Type it should have a deployment guide. Make sure the application is configured according to the deployment guide.

If all the above statements are true - the problem has to be addressed to the application packager.

Problem 2 - clicking on the login link of an APS application in POA Control Panel does not log into the application web interface.

The following are true:

  1. The destination URL of the link is built according to the entry points, with the correct values of settings (if defined in the APS package).

  2. If the host in the URL is accessible over HTTP/HTTPS, variables of entry points are:

    1. Sent as POST/GET request

    2. Have proper values from the settings (if defined in the APS package)

If all the above statements are true - the problem has to be addressed to the application packager.

Problem 3 - error in periodic (resource collection) POA task of the APS application.

The following things are true:

  1. Environment variables of the resource script are filled according to the APS specification (the same as for the configuration script).

  2. The output of the resource script (see the POA logs) is not valid.

If all the above statements are true - the problem has to be addressed to the application packager.

Problem 4 - error in POA Control Panel when trying to install/configure the application.

The following things are true:

  1. There is a non-formatted error in the Customer Control Panel (contains error stack).

  2. The error cannot be interpreted clearly (it is hard to understand what exactly is wrong).

If all the above statements are true - the problem has to be addressed to the application packager.

If any statement in a section is false, please contact Parallels Support for further investigation.

Problem 5 - there are no errors in POA, but the APS backend does not receive provisioning changes

The following things are true:

  1. APS has a backend, to which the provisioning scripts communicate
  2. The POA logs contain information that it has executed the necessary scripts and they returned no errors.

If all the above statements are true - the problem has to be addressed to the application packager.

Note: According to APS2.0 specifications, 202 "Accepted" is a valid response to a REST request, so, for example, following line:

[APSC] REST Error: POST /aps/2//resources/f96d46e2-d5e9-4a02-8d87-a7554ebbbe66/user/ code=202: Provisioning is being executed by the application

in poa.debug.log indicates that APS backend has accepted the query and started the provisioning. In such case it may be necessary to wait for a while for changes to appear.

Search Words

APS application

Provisioning Failed - Error while calling pem.activateSubscription

configuration script

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF