"Creating VSS snapshot Error" since September patch

[GoboFraggle]

Hi,

Case # 06307391

After installing KB5030211, KB5029923 and KB890830 Microsoft Windows 10 Patches and some software updats

I get an VSS error on all my workstation (4 pcs). Uninstalling of the patches didn't helped.

Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].
Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].

I tested other backup software (Arq and AOMEI Backup) to see if they have VSS problems too, but the have no problems with creating an vss snapshot. Even setting a Windows restorepoint is working well.

"DISM.exe /Online /Cleanup-image /Restorehealth" and "sfc /scannow" shows no errors.

Code: Select all

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.19041.844

Abbildversion: 10.0.19045.3448

[==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen.
Der Vorgang wurde erfolgreich beendet.

C:\WINDOWS\system32>sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 100 % abgeschlossen.

Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden.

Maybe someone has an idea what it could be.

Thx,
Alfred

[Mildur]

Hi Alfred

Welcome to the forum.
Thanks for the case number. Please wait for our support team to troubleshoot the issue, which we cannot do over a forum post.

Did you have checked the state of the VSS writers? Are they in a clean state?
- vssadmin list writers


Best,
Fabian

[GoboFraggle]

There are two "Timed out" errors

Code: Select all

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

Verfassername: "Task Scheduler Writer"
   Verfasserkennung: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Verfasserinstanzkennung: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "VSS Metadata Store Writer"
   Verfasserkennung: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Verfasserinstanzkennung: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Performance Counters Writer"
   Verfasserkennung: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Verfasserinstanzkennung: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "System Writer"
   Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}
   Verfasserinstanzkennung: {49422899-7c2f-4bb6-a1c0-5fbf2ee3b756}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"
   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Verfasserinstanzkennung: {0b8acd6d-f4ee-4a51-b241-f4122946fb7a}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"
   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Verfasserinstanzkennung: {a955967b-7d20-4ee3-af8c-c629e080559d}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "MSSearch Service Writer"
   Verfasserkennung: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Verfasserinstanzkennung: {40f61c99-e7df-47eb-a1c5-e273bd3fd35f}
   Status: [10] Fehler
   Letzter Fehler: Zeitberschreitung

Verfassername: "BITS Writer"
   Verfasserkennung: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Verfasserinstanzkennung: {d3c8140f-aa03-4d98-9c35-c0a697d36df0}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"
   Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Verfasserinstanzkennung: {f8271f58-3b9c-4470-a0e3-cbe4742e2f8e}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"
   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Verfasserinstanzkennung: {740b96b2-f088-43f7-bc49-30629b45760e}
   Status: [10] Fehler
   Letzter Fehler: Zeitberschreitung

Verfassername: "COM+ REGDB Writer"
   Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Verfasserinstanzkennung: {9a7a2078-7cdd-47f3-946a-b1426a2cd024}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "SqlServerWriter"
   Verfasserkennung: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Verfasserinstanzkennung: {429d95d3-6c31-48b8-8a0c-0745d9d34e95}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

[Matej.Sur]

Hi I have same situation after Windows Update.
Restart of SqlServerWriter does not resolve error and veeam agent backup fails again with "Creating VSS snapshot Error"
Do tou have any solution please?

Thanks in advance!

[GoboFraggle]

Hi,
no, I have not found a solution. Only using another backup software.
But I'm glad that I'm not the only user with this problem.

[Mildur]

@Matej.Sur
Please open a case with our customer support and share the case number with me.

Thank you
Fabian

[Matej.Sur]

unfortunately we are using free version with no support...
probably reregistering of vss writers can be helping - veeam-backup-replication-f2/sqlvsswrite ... 82249.html

[GoboFraggle]

You can create a case even with the free version.

[Matej.Sur]

Reregistering of vss writers did not help
@Mildur I have created support case # 06316529. Thanks in advance.

[Mildur]

Hi

So far I cannot see similar cases. I search for the three KB articles in our support system.
We need to wait till our support team will take over one of your cases (free edition gets support on best effort).

As a troubleshooting step, can you make sure that Anti Virus products to not interfere with the agent backup?
Disable Anti Virus for a test or configure the recommended exclusions:
https://www.veeam.com/kb2034

Best,
Fabian

[GoboFraggle]

Reregistering of vss writers did not help
@Mildur I have created support case # 06316529. Thanks in advance.

What anti virus software do you use?

[Matej.Sur]

there is no antivirus sofware

[Sloan]

I occasionally get a similar "VSS asynchronous operation is not completed" on all of my Windows 2012R2 physical servers, typically after patching reboots. I stop VSS and retry immediately and they run successfully. It's only once a month or less and they're set to be replaced or decomissioned withing 6 months so I haven't looked for an actual fix.

I use this powershell command to restart VSS to avoid logging into each of them.
get-service vss -computer computer_name | Stop-Service