Article ID: 122472, created on Jul 25, 2014, last review on Jan 9, 2016

  • Applies to:
  • Operations Automation 5.5

Symptoms

Office 365 sync script fails:

Subscription 50010359: error by data comparison: Error during OpenAPI call: Instance of application service with id 768 does not exist.
Subscription 50010361: error by data comparison: Error during OpenAPI call: Instance of application service with id 771 does not exist.

Instances do exist while checking KB 120815

Cause

This is caused by APS-16351. A service was detached, parent service instance was removed but its children were not.

Resolution

  1. Update to POA 5.5.6 where APS-16351 was fixed to prevent this problem for happening,

  2. Verify the service instances are unprovided and refer to nonexistent instances by parent_id:

    psql> select parent_service_instance_id,unprovided from aps_service_instances where service_instance_id = 768;
     parent_service_instance_id | unprovided | app_instance_id  
    ----------------------------+------------+-----------------
                            770 | y          |             250
    
    psql> select service_instance_id from aps_service_instances where service_instance_id = (select parent_service_instance_id from aps_service_instances where service_instance_id = 768);
     service_instance_id
    ----------------------------
    (0 rows)
    
  3. Remove the orphaned records,

    plesk=> begin; delete from aps_service_instances where app_instance_id = 250 and service_id = 771; commit;
    

Search Words

http://kb.odin.com/en/122472

Instance of application service with id

script not working fine

skipped because of error: Error during OpenAPI call: Instance of application service with id 38515 does not exist.

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF