Search Engine: Elastic

Article ID: 3086, created on Nov 20, 2007, last review on Jul 19, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.4
  • Operations Automation 5.2
  • Business Automation 6.0


Task finally fails with error message:

Some of objects are still not replicated to all active domain controllers. AD replication may take up to several minutes. You have to troubleshoot AD replication only if this task has finally failed (all attempts have failed).


This task queries all registered in OA Domain Controllers in order to verify that an object (see task description for an object name) has been replicated and exists an all controllers. Failures of such tasks can be caused by Active Directory replication issues.


In case when task resubmission does not help, one should investigate Active Directory replication issues. It can be helpful to get an object name from the task description in order to have an instance which can not be replicated. For details on troubleshooting Active Directory replication, please check the following article on Microsoft TechNet: Troubleshooting Active Directory Replication Problems.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 198398b282069eaf2d94a6af87dcb3ff c2898cda1192c88ccc616ade5f670bd6 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF