Performing Quiescing snapshot fails with error 'VssSyncStart' operation failed'

Products

• VMware vSphere ESXi 7.0
• VMware vSphere ESXi 8.0
• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

• Creating Quiescing snapshot fails with error : 

  The guest OS has reported an error during quiescing. The error code was: 5 The error message was: 'VssSyncStart' operation failed: IDispatch error #8449 (0x80042301)

   

• The error message in the location : /vmfs/volumes/Datastore_name/VM_name/vmware.log

  YYYY-MM-DDTHH:MM:SS In(05) vmx - Msg_Post: Warning
  YYYY-MM-DDTHH:MM:SS In(05) vmx - [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
  YYYY-MM-DDTHH:MM:SS In(05)+ vmx - The error code was: 5
  YYYY-MM-DDTHH:MM:SS In(05)+ vmx - The error message was: 'VssSyncStart' operation failed: IDispatch error #8449 (0x80042301)
  YYYY-MM-DDTHH:MM:SS In(05) vmx - ----------------------------------------
  YYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransportProcessClientPayload: opID=m6xkfbc8-######-auto-2odq6-h5:######-5b-01-##-####seq=26####4:
  Receiving

  
  
  The following error is reported in the eventviewer.log in the guest OS.

         

• A VSS writer has rejected an event with error 0x800423f4,

  Operation:
     PrepareForBackup event
  
  Context:
     Execution Context: Writer
     Writer Class Id: {########-####-####-####-############}
     Writer Name: Oracle VSS Writer - IMPEX
     Writer Instance Name: IMPEX
     Process ID: ####

   
   

Environment

VMware vSphere ESXi 
VMware vCenter Server

Cause

This issue typically arises due to conflicts or problems with the application hosting the VSS writer, or misconfigurations within the writer’s environment. A failure to interact with critical components of the writer may prevent the proper creation or consistency of the snapshot, leading to the rejection of the event.

Resolution

Engage the vendor of the VSS writer for further investigation. The writer vendor can provide in-depth analysis and troubleshooting specific to the application's interaction with VSS, as well as help resolve any underlying issues related to the writer’s functionality.