Checkpoint Operation Failed: Event IDs 489, 8229 and 2


Pat O'Brien


First of all, thank you for taking the time to address my question. I am having an issue creating a checkpoint on a Windows Server 2012 R2 DC that is hosted on Hyper-v 2016. The error states, "Checkpoint operation failed. 'Server-name' could not initiate a checkpoint operation."

The related errors and warning in Event Viewer are:


- Source = ESENT

- EVENT ID: 489

- General

  • lsass (596) An attempt to open the file "\\?\Volume{8637be43-c2c2-4df9-aff8-dc71ab9338c3}\Windows\NTDS\ntds.dit" for read only access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ". The open file operation will fail with error -1032 (0xfffffbf8).


- Source = VSS

- EVENT ID: 8229

  • A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

  • Operation:
    • PostSnapshot Event

  • Context:
    • Execution Context: Writer
    • Writer Class Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
    • Writer Name: NTDS
    • Writer Instance ID: {18cf3969-a35a-40cc-918b-be0206ef229b}
    • Command Line: C:\Windows\system32\lsass.exe
    • Process ID: 596


- Source = vmicvss

- EVENT ID = 2

  • The VSS writer NTDS failed with status 11 and writer specific failure code 0x800423F4.


I am able to work around the issue by restarting the COM+ Event System and Volume Shadow Copy services prior to initiating a checkpoint.


What is the recommended solution?

Continue reading...
Top Bottom