no-start-no-domain-controller on Synchronization Service Management

Question

On my Azure Ad Connect, in the Synchonization Service Manager I get a no-start-no-domain-controller in the Export and Data Import processes while on the Delta Synchonization everything seems fine.

I have a 3-level forest and lately I have added a subdomain on the 3rd level. As you can see from the following image I get this error (on artemis.cperi.certh.gr domainm which is the added one) . I get this error on Export and Data Import

While on the Delta Synchonization I get success

What is going wrong?

Also, I found out that on all the other Domain controllers there is a user with a name MSOL_<something> with permissions "Replicating Directory Changes" and "Replicating Directory Changes All" while on the artemis subdomain there is no such user. Is there any procedure/command that I have to run in order this user (or any other objects) to be created on the new subdomain?

Any other ideas?

Answer 1

@George C. Milios ,

Thank you for posting you query on Microsoft Q&A. Based upon the research I would suggest to validate network connectivity problems between AAD Sync/connect server or DNS configuration in ADDS.

• Check the DNS configuration on the Synchronization Service Manager and the domain controller. Make sure that the DNS settings are correct and that the domain controller is properly registered in DNS.
• Check the status of the domain controller. Make sure that the domain controller is running and that all critical services, such as the Netlogon service, are running.
• Run the troubleshooting task in the wizard and let me know the results.

Please do let me know if you have any further queries in the comments section.

Thanks,

Akshay Kaushik

Please "Accept the answer", "Upvote" and share your feedback (Yes/No) if the suggestion works as per your business need. This will help us and others in the community as well.