• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2010
  • Last Modified:

DNS, Event Log and a few other services not starting on DCs

Hi all,

We shut down all our servers today as we were going to do some updates to our VMware ESXi Hypervisor host servers but at the last moment we discovered some problems with documentation so we abandoned the upgrades and no changes were made.  Upon rebooting all our guest servers (all 2008R2) we noticed that none of our domain controllers (3 of them) were starting properly.  All had the same failing services (set to Automatic);

Active Directory Web Services
Application Experience
Diagnostic Policy Service
DNS Server
Microsoft DotNet v4.0.303.19_x64
Microsoft DotNet v4.0.303.19_x86
Windows Event Log
Windows Firewall
Windows Remote Management
WinHTTP Web Proxy Autodiscovery Service

Not all of those are services that we would necessarily use/need but for thoroughness I thought I would list them all.  Now, when we attempt to start some of these services we get the following errors;

DNS Server service
Windows could not start the DNS server service on the local computer.  Error 1717: The interface is unknown.

Windows Event Log service
Windows could not start the Windows Event Log service on the local computer. Error 0x800700E Not enough storage is available to complete this operation.

There is about 17gb free on the system drive of the primary DC so I'm not sure what the Event Log error is referring to.  We suspect that our problems are related to the Event Log not working but so far any attempts to get it going haven't worked.

Can anyone please assist?  Let me know if more information is required...
1 Solution
What DNS servers do you have configured on these servers' network adapters, and does nslookup allow you to query 'yourdomain.local' ?
SchikitarAuthor Commented:

Man, things were getting tense in the workplace with a completely non-functional network!  One of the guys stumbled across the problem though which was that the Default Domain Controller GPO was corrupt (not that you'd know by looking at it).  

We issued the following command from one of the non-functional domain controllers;
* dcgpofix /ignoreschema
* Press OK twice and run gpupdate /force
* Reboot

Now if only Windows Server was able to tell us this was the problem instead of leading us on a wild goose chase about unknown interfaces and storage issues!

Just a quick tip, if you have important settings in either the Default Domain Policy or the Default Domain Controllers Policy be sure to print them out BEFORE issuing the above command.

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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now