Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

The DNS server has encountered a critical error from the Active Directory. and a number of other errors

$
0
0

Hi All,

I have setup a domain running windows server (2012) including the domain controllers.

The two DCs seem to be behaving strangely. I have had a number of DNS issues, which I have resolved. Now, I rebooted the server at roughly 5.40pm or before (GMT time; it's 9.33pm as I edit this), and on the server get these event logs:

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

The error code for the above is 4015 and the guidance just says restart the service, which I have done.

And then.....

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.

In the AD event logs, the DFS-R service is replicating and creating connections ok. 

But on the PDC-e DC, I get:

 

The DFS Replication service is stopping communication with partner DC-2 for replication group Domain System Volume due to an error. The service will retry the connection periodically. 

Additional Information: 
Error: 1723 (The RPC server is too busy to complete this operation.) 
Connection ID: 96DE0D90-3D16-4F8B-8D1B-B34C7CC71001 
Replication Group ID: 48617AF8-990C-4D50-B947-271427F95C29

And then straight  after:

The DFS Replication service successfully established an inbound connection with partner DC-2 for replication group Domain System Volume. 
 
Additional Information: 
Connection Address Used: DC-2.SHAREPOINTDEVEN.DEV 
Connection ID: 96DE0D90-3D16-4F8B-8D1B-B34C7CC71001 
Replication Group ID: 48617AF8-990C-4D50-B947-271427F95C29

Again, this is at  5.40. 

Since then, neither DC is recording anything to the event logs for DNS, DFS-R or Directory Service.

Both DCs point to themselves as the primary DNS and each other as secondary.

If required, I can post ipconfig /all.





Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>