Search Engine: Elastic

Article ID: 129202, created on Aug 2, 2016, last review on Aug 2, 2016

  • Applies to:
  • Operations Automation


Different OA tasks can fail with the following error:

Subdomain service #xxxxxx does not exist

Examples of the tasks:

APS application 'Application name', id 123, instance 123456 : providing direct access to the site application contents

Create Offline Address Book for domain service 

Register accepted domains (organization identifier: 7890)  

There is a successfully processed task to remove the same organization.

5981305 Complete removal of organization (ds_id=yyyy)   Nov-19-2013 11:12:53    Nov-19-2013 11:12:56    DomainService0000xxxx   1234567 Successful

The domain service mentioned in the output can be checked in OA database, it exists in l_domain_services, but does not exist in domain_services:

plesk=> select * from l_domain_services where ds_id=xxxx;

plesk=> select * from domain_services where ds_id=xxxx;


Domain service indeed does not exist as it has been already removed.


The reported failed tasks from the queue 'DomainService0000xxxx' are no longer needed and can be canceled.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF