Windows could not start the DHCP Server service on Local Computer

Hi all,
While trying to delete some scopes from my DHCP server (Windows Server 2012 R2), my dhcp server service suddenly stopped.
Tried to restart the service and received error:
Windows could not start the DHCP Server service on Local Computer.
 Error 4312: The object identifier does not represent a valid object.

Tried to reboot the server and the issue is still persists. How to resolve this??
Who is Participating?
SuzenJConnect With a Mentor Author Commented:
Hi guys,
Thanks for the suggestions and assistance on this matter.
I've fixed the issue by deleting all the files inside the DHCP folder and able to start the service after that.
Tried to restore from the backup earlier, but the the backup files was corrupted too.
To recover the scopes, I exported the scopes from server 2 and imported them to the server 1.
Still feeling weird, how could a deleted scope led to corruption of DHCP server service.
I've delete hundred of scopes in server 2008 but never encountered this issue.
Christopher Jay WolffWiggle My Legs, OwnerCommented:
It sounds like you deleted an object.  Are you familiar with DHCP backup and restore?  You should have the benefit of automated backups.  This article from TechNet describes it in a pretty succinct way for 2008, anyone know if this works for 2012?

Maybe you were using powershell to clean up your scopes, but if not, here is a description of using powershell and shows a "whatif" switch that should allow you to see what will happen before you actually delete a scope.  Hope this helps.
Christopher Jay WolffWiggle My Legs, OwnerCommented:
Hi again.

Have to go, but wanted to share this excerpt below from Microsoft Server 2012 Pocket Consultant.  (650 pages in your pocket?  Really?)

Although you can enable and configure logging separately for IPv4 and IPv6, the two protocols use the same log files by default. The default location for DHCP logs is %SystemRoot%\System32\DHCP. In this directory, you’ll find a different log file for each day of the week. The log file for Monday is named DhcpSrvLog-Mon.log, the log file for Tuesday is named DhcpSrvLog-Tue.log, and so on.

Also lots of stuff on DHCP that may be useful for you until someone comes along here.  I haven't yet found out if the backups overwrite or create additional backups, since overwriting would wipe out your good backup with your current failing situation.  Also, the missing object the service needs, may not be in the backup related to DHCP service.
Seth SimmonsSr. Systems AdministratorCommented:
i would try removing everything in dhcp (outside business hours) and creating again
if that doesn't work, i would remove that and the dhcp role; add dhcp role again and create scopes
SuzenJAuthor Commented:
I've tested the solution and it was proven working.
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.