/vmfs/volumes/datastore/Affected_VM/vmware.log file, you see entries similar to: <YYYY-MM-DD>T<time>.453Z| vcpu-0| I120: Guest: [ debug] [vmvss:vmvss] CVmSnapshotRequestor::Start():865: failed call: m_snapResult = VDSHelper::ForEachVolume(std::vector<std::string>(), da), result = 0x80070422</time>
<YYYY-MM-DD>T<time> </time>.454Z| vcpu-0| I120: Guest: [ warning] [vmsvc:vmbackup] CVmVssRequestor::Initialize failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (0x80070422)
<YYYY-MM-DD>T<time> </time>.454Z| vcpu-0| I120: Guest: [ debug] [vmsvc:vmbackup] *** CVmVssRequestor::Finalize
<YYYY-MM-DD>T<time> </time>.455Z| vcpu-0| I120: Guest: [ debug] [vmvss:vmvss] CVmSnapshotRequestor::WaitForUnregistration():2590: enter
<YYYY-MM-DD>T<time> </time>.455Z| vcpu-0| I120: Guest: [ debug] [vmsvc:vmbackup] *** CVmVssRequestor::SendRequestorError
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120: Guest: [ debug] [vmsvc:vmbackup] *** VmBackup_SendEvent
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120: Guest: [ debug] [vmsvc:vmbackup] sending vmbackup event, vmbackup.eventSet req.error 3 The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120: Msg_Post: Warning
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120+ The error code was: 3
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120+ The error message was: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
<YYYY-MM-DD>T<time> </time>.456Z| vcpu-0| I120: ----------------------------------------
<YYYY-MM-DD>T<time> </time>.462Z| vcpu-0| I120: ToolsBackup: changing quiesce state: STARTED -> ERROR_WAIT
The issue affects Windows Server 2008 SP2. You see log entries similar to:
<YYYY-MM-DD>T<time> </time>.536Z| vcpu-1| I120: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
<YYYY-MM-DD>T<time> </time>.536Z| vcpu-1| I120+ The error code was: 3
<YYYY-MM-DD>T<time> </time>.536Z| vcpu-1| I120+ The error message was: Quiesce operation aborted
<YYYY-MM-DD>T<time> </time>.542Z| vcpu-1| I120: ToolsBackup: changing quiesce state: STARTED -> ERROR_WAIT
<YYYY-MM-DD>T<time> </time>.583Z| vcpu-1| I120: ToolsBackup: changing quiesce state: ERROR_WAIT -> IDLE
<YYYY-MM-DD>T<time> </time>.713Z| vcpu-1| I120: GuestMsg: Channel 2, Protocol error, state: 0
<YYYY-MM-DD>T<time> </time>.782Z| vcpu-0| I120: GuestMsg: Channel 0, Protocol error, state: 0vmx - [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
vmx - The error code was: 3
vmx - The error message was: Quiesce operation canceledNote: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware vSphere ESXi 8.0.X
VMware vCenter Server 8.0.X
services.msc, and press Enter.Restart the Windows Virtual Disk service if the vCenter Server reports the error
An error occurred while saving the snapshot: msg.snapshot.error-QUIESCING-ERRORTroubleshooting Volume Shadow Copy (VSS) quiesce related issues
How to disable VMware Snapshot provider in the Windows guest OS