T The Triage ManualTechnical Guides for IT Emergencies
P1 · Network Infrastructure

DHCP Server Service Failure Due to Jet Engine Lease Database Corruption (dhcp.mdb) — Windows Server 2019/2022

The Windows Server DHCP service stops unexpectedly or ceases issuing IP addresses when the dhcp.mdb Jet engine lease database becomes corrupted. Corruption typically follows sudden storage outages, unclean OS shutdowns, or internal Jet engine errors, confirmed by Event IDs 1014/1016 and JET_errRecordNotFound in event logs. Resolution involves stopping the service, restoring the database from the auto-backup folder at C:\Windows\System32\dhcp\backup\Jet\new\, and restarting. If backup restoration fails, scopes must be recreated manually.

Indicators

Likely causes

Diagnostic steps

  1. Navigate to C:\Windows\System32\dhcp\ and verify presence and integrity of dhcp.mdb and associated files (dhcp.tmp, j50.log, j50.chk)
    Confirms whether lease database files are present and identifies obvious file-level corruption or missing files
  2. Open Event Viewer (eventvwr.msc) and review DHCP Server operational event log and System log. Filter for Event ID 1014 and Event ID 1016
    Confirms DHCP service failure is due to database state errors rather than network or authorization issues
  3. In the same event logs, search for Jet engine error code JET_errRecordNotFound to identify specific database engine failure details
    Pinpoints the exact Jet engine error causing database failure and confirms corruption of lease state tracking tables
  4. Verify auto-backup folder C:\Windows\System32\dhcp\backup\Jet\new\ exists and contains recent database snapshot — check file timestamps against last known good operation
    Determines whether a viable backup exists for restoration before proceeding with remediation

Resolution path

Prevention

Tools

References

DHCPWindows Server 2019Windows Server 2022Jet EngineDatabase Corruptiondhcp.mdbIP AddressNetwork ConnectivityEvent ID 1014Event ID 1016JET_errRecordNotFoundInfrastructureP1L2L3