Vss код ошибки 12292

title description ms.date author ms.author manager audience ms.topic ms.prod localization_priority ms.reviewer ms.custom ms.technology

Backup fails with VSS event ID 12292 and 11

Fixes an issue in which backup operation using Windows Server Backup or a third-party backup application fails.

9/24/2021

Deland-Han

delhan

dcscontentpm

itpro

troubleshooting

windows-server

medium

kaushika

sap:volume-shadow-copy-service-vss, csstroubleshoot

windows-server-backup-and-storage

Backup fails with VSS event ID 12292 and 11 on Windows Server

This article discusses an issue where backup operation using Windows Server Backup or a third-party backup application fails.

Applies to:   Windows Server 2012 R2
Original KB number:   2009513

Symptoms

A backup operation using Windows Server Backup or a third-party backup application fails on Windows Server.

In the System event log, the following event is logged:

Log Name: System
Source: Service Control Manager
Event ID: 7023
Level: Error
Description:
The Microsoft Software Shadow Copy Provider service terminated with the following error:
The system cannot find the file specified.

In the Application event log, the following events are logged:

Log Name: Application
Source: VSS
Event ID: 12292
Level: Error
Description:
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} [0x80080005].
Operation:
Obtain a callable interface for this provider
Obtaining provider management interface
Context:
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: -1
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Log Name: Application
Source: VSS
Event ID: 11
Level: Error
Description:
Volume Shadow Copy Service information: The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. Most likely the CPU is under heavy load. [0x80080005]
Operation:
Obtain a callable interface for this provider
Obtaining provider management interface
Context:
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: -1
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

On Windows Server 2008, if Windows Server Backup was used to perform the backup, the backup operation fails with one of the following errors:

Failed to create the shadow copy on the storage location.
ERROR — Volume Shadow Copy Service operation error (0x8004230f)
The shadow copy provider had an unexpected error while trying to process the specified operation.

Or

The creation of the shadow copy on the backup destination failed.
The volume shadow copy operation failed with error 0x8004230F.
View the event log for more information.

On Windows Server 2008 R2, if Windows Server Backup was used to perform the backup, the backup operation fails with one of the following errors:

Windows Backup failed to create the shadow copy on the storage location.

Or

The creation of the shadow copy on the backup storage destination failed.

Cause

This issue can occur if the ServiceDll registry value for Swprv is missing or incorrect.

Resolution

To resolve this issue, perform the following steps:

  1. Click Start, type regedit in the Start Search box, and hit Enter.

  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesswprvParameters

    [!Note]
    If the Parameters registry key is missing, perform the following steps:
    Right-click the swprv registry key, select New, select Key, type Parameters and hit Enter.

  3. Once the Parameters registry key is selected, verify that the ServiceDll registry value has the following value:

    %Systemroot%System32swprv.dll

    [!Note]
    If the ServiceDll registry value is missing, perform the following steps:

    1. Right-click the Parameters registry key, select New, and then select Expandable String Value.
    2. For the value name, type ServiceDll and hit Enter.
    3. Double-click the ServiceDll registry value.
    4. In the Value Data box, type %Systemroot%System32swprv.dll, and then click OK.
  4. Perform a backup operation to verify that the issue is resolved.

05.12.201617:0805.12.2016 17:08:12

Такие ошибки при запуске бэкапа могут возникать по причине наличия остатков в реестре от VSS-провайдеров, которые ранее были удалены из системы.
В моем случае ошибки появлялись на хостовой машине Hyper-V на Windows Server 2008 R2 при запуске резервного копирования.
Запустив команду vssadmin list providers я увидел, какие VSS-провайдеры зарегистрированы у меня в системе, и сравнил их с PID-ами тех, которые были в ошибках. Выяснилось, что ошибки возникали в отношении провайдеров, которые мне были не нужны и которых я ранее удалил из системы.
Далее я удалил записи в реестре от этих провайдеров следующим образом:

1) Находим в реестре ключ  [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesVSSProviders]
2) На всякий случай создаем резервную копию этого ключа
3) Удаляем ключи с соответствующим PID
4) Перезапускаем службу «Microsoft Software Shadow Copy Provider»
5) Запускаем бэкап и смотрим на наличие ошибок. Если ошибки появились вновь, перезагружаем систему.

Все, после этого ошибки должны исчезнуть.

Also read in:

use Google Translate

Столкнулся тут с проблемой архивации одного из серверов, никак не проходил бэкап с использованием службы VSS. На сервере в логах были ошибки 22 и 12292

а Veeam backup рапортовал » Failed to prepare guest for hot backup. Error: VSSControl: -2147212529 Backup job failed. Discovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [?Volume{09ce62de-7e04-11df-b22e-806e6f6e6963}]. Cannot add volume to the set of volumes that should be shadowed. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f
Error: VSSControl: -2147212529 Backup job failed. Discovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [?Volume{09ce62de-7e04-11df-b22e-806e6f6e6963}]. Cannot add volume to the set of volumes that should be shadowed. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f »

Виной всему стал старый Provider от пробной версии Acronis, который после удаления не почистил за собой реестр. Придется сделать это за него… Заходим в реестр по следующему пути: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders и смотрим что там есть. На чистой системе должен быть один провайдер от microsoft

У меня тут рядышком висел провайдер от acronis, удалив который, VSS заработал без ошибок и косяков!

Since we had change the SAN switch for one of our Exchange 2010 DAG nodes, Its started to fetch the event ID 12292 and VSS backup stoped working for this node.

Used below cmdlet to make sure exchange replication  writer and providers are working fine.

Vssadmin list writers

Vssadmin list providers

Started looking the registry value of VSS provider and matching the registry value with other DAG nodes which is working normally. During match, I found the “Start” Dword value is showing data value “0x00000004”.

In other DAG nodes this value was ““0x00000002” under “KLMCCSSYSTEMSERVICESSWPRV” .

If you falling under same kind of issue, I would suggest you to verify the registry value with working server for below Key’s.

1. On Exchange server, please run regedit, go to verify the following two registry keys. Make sure they are the same with another working server:

HKLMCCSSYSTEMSERVICESVSSPROVIDERS

KLMCCSSYSTEMSERVICESSWPRV

2. Please Reboot Exchange server in Off-Business hours.

3. After reboot, please try to backup Exchange using Windows Server Backup tool.  Check if it is successful.

If still you are not bale to managed this working, As a Last resort you can try Re registering the Vss dlls

Re-registering Vss Dlls

cd /d %windir%system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

It does help in getting the Vss service to function properly

  • Vss mobile ошибка при проверке устройства
  • Vsphere ha virtual machine failover failed ошибка
  • Vsphere distributed switch vlan trunked status ошибка
  • Vsphere client базовое соединение закрыто непредвиденная ошибка при передаче
  • Vsm 2 ошибка сигнала