Search Engine: Elastic

Article ID: 114678, created on Aug 29, 2012, last review on Jul 25, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Business Automation 7.0


Office 365 tasks fail in POA with the error message Can not create DNS record for <domain.tld> of type TXT/CNAME. There is existing record, see the example below:

Task ID 208819
Queue name      aps_application_instance880
Task name       APS application 'Microsoft Office 365', id 101, instance 880 -> service 'customer', instance 1229: executing configuration script
 Task description        APS application 'Microsoft Office 365', id 101, instance 880 -> service 'customer', instance 1229: executing configuration script
Subscription ID 2206
Queue status    Failed   
Start not earlier than  07/18/2012 00:51
Method name     taskExecuteApplicationInstanceScript on OBJREF:APSManagerTasks:0:getAPSExternalTasks:0
Last execution output   Can not create DNS record for '' of type TXT. There is existing record with id 4471 and data '"v=spf1 ~all"'.


Cause 1. The APS service controller in POA does not support multiple DNS records of the same type in a domain zone - TXT or CNAME, in this case.

Cause 2. Customer manually added TXT, MX or CNAME records in their domain and then tried to provision APS application to the domain. If application being installed tries to add conflicting DNS records then the problem will arise.

Cause 3. Customer added domain to an APS application which automatically created DNS records, e.g. Hostopia. Then customer tried to add the same domain to another APS application which tries to create DNS records of the same type, e.g. Office 365. The latter action leads to failed APS task in POA.


Cause 1 - the problem is fixed in POA 5.4.8, upgrade POA to this or later version.

Cause 2 - remove manually added conflicting DNS record and re-run the failed task in POA.

Cause 3 - ask customer not to install two or more APS applications which require conflicting DNS records on the same domain.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 c0f836394088a28cc30dd0e5fe8b600e 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF