Search Engine: Elastic

Article ID: 130918, created on Jun 3, 2017, last review on Jun 3, 2017

  • Applies to:
  • Operations Automation


An APS application provisioning task fails. An example of the failure:

Internal error: Plesk::SaaS::SaaSManagerTasks_impl::taskExecuteWorkflow : [APSC] Provisioning: resource 81ef1333-492b-43da-befc-4281d306dcd5 of type 'tenant' ( for APS application 'Acronis Backup Cloud-2.1-1884': Modification of 'eba0ac51-8dd9-4ce9-b772-21c992f62a22' requested by linking to '81ef1333-492b-43da-befc-4281d306dcd5' is not allowed..

Accessing the application endpoint URL directly gives a page with PHP code:

# curl -vv -k https://192.0.2./backupservice/globals/eba0ac51-8dd9-4ce9-b772-21c992f62a22/tenant

In /var/log/pa/core.log at the point of endpoint response:

Jun  1 16:46:56 THHS2PEMOSS01 : DBG [task:79672345:332786 1:10528:3f08 SAAS 1892894953]: [ HTTP] OUT  Response headers: 'Connection:close'  'Content-Type:text/html; charset=UTF-8'  'Date:Thu, 01 Jun 2017 15:46:56 GMT'  'Server:Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16'  'Transfer-Encoding:chunked'  'X-Powered-By:PHP/5.4.16'  
Jun  1 16:46:56 THHS2PEMOSS01 : INF [task:79672345:332786 1:10528:3f08 SAAS 1892894953]: [ HTTP] OUT  [1455] "POST /backupservice/globals/eba0ac51-8dd9-4ce9-b772-21c992f62a22/tenant HTTP/1.1"  [0] "200 OK"  78ms

the content type is Content-Type:text/html, while Content-Type:application/json is always expected.


The reason behind such a failure is an incorrect endpoint configuration. The response from application's tenant.php script is incorrect. One of the possible reasone: malformed opening php tag, e.g. <?php:, when semicolon is not expected


Validate the PHP scripts for syntax errors and resolve, if any. Make sure there are no Apache service errors in /var/log/httpd/error_log during provisioning attempts.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF