The directory service on server01DC has not finished initializing. Not advertising as a global catalog

It has been over 12 hours and one of our 2012 R2 DCs is still getting an error that it is not finished synchronizing. I network connectivity is good. I am able to ping other servers. DNS is not resolving if I use that server as DNS. So, DNS on that server is definitely broken. See the DNS error that I also getting. I tried restarting DNS service and restarting computer and didn't resolve the issue. I forced replication and still get this error.

Issue: Warning: Not advertising as a global catalog
The directory service on server01DC has not finished initializing. In order for the directory service to consider itself synchronized, it must attempt an initial synchronization with at least one replica of this server's writeable domain

Event ID 4013 The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

I ran repadmin /showrepl servername /verbose /all /intersite

I received only  Warning: Not advertising as a global catalog

All partition replication attempts were listed as successful.

Please advise how to fix this issue and make sure this DC that is also a DNS will start advertising.
Who is Participating?
David Johnson, CD, MVPOwnerCommented:
perhaps something went wrong in the dcpromo. go to manage / remove... and uncheck Active Directory Domain Services, it will say you have to run dcpromo to remove this computer as a Domain controller, do so, reboot, Server manager will now want to promote this computer to a domain controller and do it again
Sudhir BidyeCommented:
How many dc's in your AD? check howz the replication and verify no replication failure or lingering dc's exists
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.