Search Engine: Elastic

Article ID: 115437, created on Jan 22, 2013, last review on Jul 13, 2016

  • Applies to:
  • Operations Automation 5.4


OA cannot create Offline Address Book (OAB) for customer Exchange 2010 organization, the task Create Offline Address Book fails with the error message There is no such object on the server like in the example below:

Task ID           1446375
Queue name        DomainService00200717
Task name         Create Offline Address Book for domain service 200717
Task description  Create Offline Address Book for domain service 200717
Queue status      Failed   
Start not earlier than  Jan-17-2013 12:09
Method name     createOABHandler on OBJREF:Exchange:0:getDomainService:200717
Last execution output   Destination host_id #123 : Provisioning request failed. There is no such object on the server. [<response><errorContext description="There is no such object on the server." code="0x80072030" executeSeqNo="2"><errorSource namespace="Exchange2010ProviderEx" procedure="CreateOfflineAddressBook"/><errorSource namespace="SW Managed Exchange" procedure="CreateOfflineAddressList"/></errorContext></response>] 


Exchange2010OAB service is configured improperly in OA - the name of the Public Folder Store where OABs will be generated and stored is incorrect.


  1. Log into OA Provider Control Panel
  2. Find the server where the Exchange2010OAB service is installed at Top > System Director > Configuration Manager > Services
  3. Go to Top > Deployment Director > Server Manager > Hardware Nodes
  4. Click on the server found at the previous step
  5. Switch to the Applications tab
  6. Click on the Exchange2010OAB application
  7. Switch to the OAB Configuration tab
  8. Make sure that the OAB public folder store parameter contains correct value of the existing Public Folder Store

OA Control Panel does not allow to change the name of the Public Folder Store where OABs are being generated and stored, contact Support Team to correct it in case it is wrong.

Another possible solution is to create Public Folder Store configured in OA on Exchange servers instead of correcting the value in OA database.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF