SERVER 2012: Update Error 8E5E03FA

Hello and welcome,

The error means there is a corruption due to a hardware failure. see here: Jet database errors and recovery steps - Windows Server

-1018 JET_errReadVerifyFailure / Checksum error on a database page​


Cause​


The DB is corrupted due to a hardware failure.


Resolution​

  • Evaluate the disk stack, including the motherboard/controller, firmware, connecting cables, and physical drives, and contact the relevant vendors for known issues. Compare your current configuration against the vendors' reference configurations.
  • Evaluate whether the problem can be resolved by the latest firmware updates or was triggered by a recent firmware update.
  • If some DCs are logging -1018s while other DCs in the same environment aren't, look for differences in hardware configurations.
  • Databases that log this error can't be recovered or repaired by integrity checks or semantic database analysis in NTDSUTIL or ESENTUTL.
  • Offline defrags may fix the problem in the unlikely case that the problem is due to an index consistency problem.
  • Try an offline defrag. Or, restore a system state backup that predates the corruption. Or force-demote, perform a full metadata cleanup, and repromote. If the -1018 error appears, repeat until the hardware root cause is resolved.

When Jet error -1018s occurs on virtualized DCs that are running on the same virtual host only on computers that are using an on-board raid controller, the error can occur because the uninterruptible power supply (UPS) lacked sufficient power for on-board raid controllers to commit changes to disk following loss of electrical power. The workaround is to configure UPS software to shut down virtualized guests upon loss of electrical power. Servers that have dedicated (not on-board) raid controllers with their own battery backups don't experience the -1018 JET error.

Make sure to have a backup first.
Next, remove following update.

Remove Update Manually
  1. Click on the Start button and in the search box, type Command Prompt.
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:5029312
  4. Let me know if it says it was successful or if there are any errors.
 
Hello PeterJ,

it is a virtual server (no DomainController). Other servers on this hardware host have no problems.
KB5029312 isnt installed - so i cant uninstall this update.
 
Please do following:

FRST Registry Search
  1. Click the Start button and in the search box, type CMD
  2. When you see cmd.exe on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, press enter afterwards.

    Code:
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

    Note: This loads your components hive which is what we want. Please keep the command prompt windows open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  4. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB5029312 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Restart the computer.
Check Windows Update again and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Did you try to install KB5029312 again ?
If so perform the instructions in message #4 again.

Are there other important Windows Updates available ?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top