Search Engine: Elastic

Article ID: 128422, created on Feb 23, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


Task for provisioning a new add-on to WAP failed with the following error:

Last execution output   
Internal error:
403 Forbidden
[ApplicationUnknownError] [APS] {
"error": "APS::Util::AccessViolation",
"message": "Association with the resource '6054868b-9628-4be3-a245-3a7f314b0589' is not allowed."
Body: {
"error": "ApplicationUnknownError",
"message": "[APS] {\n \"error\": \"APS::Util::AccessViolation\",\n \"message\": \"Association with the resource '6054868b-9628-4be3-a245-3a7f314b0589' is not allowed.\"\n}\n"


In the past the following error could be found for the same subscription for some other provisioning task:

Internal error: SDK::Platform::blob Plesk::SaaS::SaaSManagerTasks_impl::taskExecuteWorkflow(const SDK::Platform::Properties&) : [APSC] [APS] Read timed out.

From /var/log/WAP/wap.log it's possible to find the description of the resource UUID, example:

        "title": "WAP 100GB Azure Pack Diskspace",
        "apsId": "6054868b-9628-4be3-a245-3a7f314b0589",
        "apsType": "",
        "id": 1004433,
        "usage": 2,
        "limit": 2,
        "unit": "unit"

The mentioned resource consumption in OA subscription is higher than the actual usage on WAP portal.


The issue is a consequence of product issue CCU-9081 fixed since WAP APS 1.0.4.


Contact Odin Technical Support to resolve the resource consumption mismatch.

To prevent future failures keep WAP APS instances up to date.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF