All Collections
Knowledge Base
Enterprise Workloads
Troubleshooting - Enterprise Workloads
VMware backups fail with VMWARE VMOMI1 error and VSS error 8193
VMware backups fail with VMWARE VMOMI1 error and VSS error 8193
Updated over a week ago

Problem description

Snapshot of a virtual machine fails with quiescing with following errors:

  • Phoenix logs - Failed to quiesce the virtual machine

  • Event Viewer of the virtual machine – Vss - The security ID structure is invalid.

Restarting the virtual machine and VMotion is not helpful in this scenario.


Log location:

[2020-06-08 14:09:37,885] [ERROR] Error <class 'pyVmomi.VmomiSupport.vim.fault.ApplicationQuiesceFault'>:(vim.fault.ApplicationQuiesceFault)

value = 'msg.snapshot.error-QUIESCINGERROR'

message = 'An error occurred while saving the snapshot: Failed to quiesce the virtual machine.'

Event Viewer

Log Name: Application

Source: VSS

Date: 7/22/2020 6:38:34 AM

Event ID: 8193

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: <servername>


Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-2460280860-2823173241-3174630117-1075679.bak). hr = 0x80070539, The security ID structure is invalid.


Execution Context:

Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Name: Shadow Copy Optimization Writer

Writer Instance ID: {7e40559b-bc89-49a9-9316-e5dd42c39d62}


⚠️ Warning

Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Be cautious while making changes to a Windows registry. Registry modifications must be made by a person with experience and expertise in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation must be made before making any registry changes.

From VMware

Compare the snapshot failure error on the vCenter console for the VMware level troubleshooting (e.g Issues with Bus sharing, etc.).

From Windows

  1. The virtual machine's event viewer shows a stale user profile registry entry that was not resolved by the VSS Shadow Copy Optimization Writer.
    In this case, it is (S-1-5-21-2460280860-2823173241-3174630117-1075679.bak)

  2. The entry is listed under:
    ​HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

  3. Rename or remove the entry with the help of Windows admin.

πŸ“ Note
​This will require a reboot of the virtual machine. You can check for other entries as well under the same location.

  1. Perform another backup.

Did this answer your question?