Search Engine: Elastic

Article ID: 127220, created on Oct 22, 2015, last review on Feb 22, 2016

  • Applies to:
  • Operations Automation
  • Business Automation 6.0


APS 2.0 resources propagation (such as Service Template synchronization, Subscription synchronization, creating new Subscription etc.) fails with following error:

    Parallels Operations Automation error #extype_id #1, module_id #Common, Internal error: Failed to get APS resource id. aps node is not found...
    Error Code: 0xb619b247.

Similar message appears in /var/log/poa.log:

SaaS::JsonUtils::getResourceNodeByName] {module_id="Common"; code="1"} Internal error: Failed to get APS resource id. aps node is not found.


There are duplicated domain records, that mistakenly considered as parents of each other, and APS application is looking for parent domain APS resource, when creates an APS resource of a domain.

Such behavior is confirmed as software-related issue #APS-29381. Same failure could also occur when order is provisioning for an account which have such duplicated domains.


Please contact Odin Technical Support regarding the case.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF