Ошибка 0x800423f4 как исправить

Hi Folks!

Support Case ID: # 00558655

Situation: Win2012 R2 Server with latest Veeam B&R backing up a Win2012R2 Standard Server with Exchange2013 SP1 running on a Win2012 R2 Hyper-V Core.

Problem: Backing up the Exchange Server with setting «Enable application-aware image processing» — the job fails with this Error:

08.05.2014 13:13:22 :: Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing). Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
Vss error: '0x800423f4'
--tr:Failed to verify writers state.
--tr:Failed to create VSS snapshot.
--tr:Failed to perform pre-backup tasks.

08.05.2014 13:14:34 :: Make sure VM does not have 'iSCSI Software Target Storage Provider' feature installed.

08.05.2014 13:14:49 :: Unable to allocate processing resources. Error: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
Vss error: '0x800423f4'
--tr:Failed to verify writers state.
--tr:Failed to create VSS snapshot.
--tr:Failed to perform pre-backup tasks.

If I unset «Enable application-aware image processing» or shut the VM down — it works!

For you to notice: We had to do a recover of the whole Exchange VM. From this point the Backup crashes.
My idea is that there’s something with the HDD ID’s wrong.. But I don’t have any clue how to check that!

My Writer Stati are all OK:

PS C:Windowssystem32> vssadmin list writers
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: {6e8b7f24-f8ea-430a-bfe8-73cd8a1887c3}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Microsoft Exchange Writer"
   Verfasserkennung: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Verfasserinstanzkennung: {8541fb44-4c29-41b5-9535-23c249fd7bc5}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"
   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Verfasserinstanzkennung: {d9f54d72-5d91-41a6-bd50-1a12962a0578}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"
   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Verfasserinstanzkennung: {b6cadea4-fb26-4e1f-838d-f2efdb91d809}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"
   Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Verfasserinstanzkennung: {4001043a-f435-4a2d-8587-186a25ff3650}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "MSMQ Writer (MSMQ)"
   Verfasserkennung: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Verfasserinstanzkennung: {cc31a2eb-9458-4a71-9632-ab7d44d6401e}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "IIS Config Writer"
   Verfasserkennung: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Verfasserinstanzkennung: {8417f542-4ac5-4fcf-968c-2ecf0bbbc8b1}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"
   Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Verfasserinstanzkennung: {377d9650-8850-41a9-8f16-9c6cdbeeda9d}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "IIS Metabase Writer"
   Verfasserkennung: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Verfasserinstanzkennung: {e245739e-5090-4d05-98c9-23061bd7c3fb}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"
   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Verfasserinstanzkennung: {acb54487-4d51-4ab4-8a43-852218be78e7}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Performing a Shadow Copy:

DISKSHADOW> set context persistent
DISKSHADOW> set verbose on
DISKSHADOW> begin backup
DISKSHADOW> add volume C: alias VolumeC
DISKSHADOW> add volume E: alias VolumeE
DISKSHADOW> add volume F: alias VolumeF
DISKSHADOW> add volume G: alias VolumeG
DISKSHADOW> createDer Verfasser "Shadow Copy Optimization Writer" wird ausgeschlossen, da alle Komponenten des Verfassers ausgeschlossen sind.
Die Komponente "BCDBCD" von Verfasser "ASR Writer" ist von der Sicherung ausgeschlossen, da
das erforderliche Volume "" nicht im Schattenkopiesatz vorhanden ist.
Der Verfasser "ASR Writer" ist jetzt vollständig von der Sicherung ausgeschlossen, da die nicht
auswählbare Komponente "BCDBCD" auf oberster Ebene ausgeschlossen ist.

* Verfasser "Task Scheduler Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: TasksStore

* Verfasser "VSS Metadata Store Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: WriterMetadataStore

* Verfasser "Performance Counters Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: PerformanceCounters

* Verfasser "System Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: System Files
	+ Komponente wird hinzugefügt: Win32 Services Files

* Verfasser "Microsoft Exchange Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: Microsoft Exchange ServerMicrosoft Information StoreLEMONQUEEN87879ae5-c7d3-4f11-b9ed-b207b4e83588
	+ Komponente wird hinzugefügt: Microsoft Exchange ServerMicrosoft Information StoreLEMONQUEENe9074ce1-63bd-47aa-b276-6bd3ee44f499
	+ Komponente wird hinzugefügt: Microsoft Exchange ServerMicrosoft Information StoreLEMONQUEEN1abbd199-b82e-4e6b-903b-61d4df555f55

* Verfasser "Registry Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: Registry

* Verfasser "COM+ REGDB Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: COM+ REGDB

* Verfasser "WMI Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: WMI

* Verfasser "IIS Config Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: IISCONFIG

* Verfasser "IIS Metabase Writer" wird eingeschlossen:
	+ Komponente wird hinzugefügt: IISMETABASE

* Verfasser "MSMQ Writer (MSMQ)" wird eingeschlossen:
	+ Komponente wird hinzugefügt: config
	+ Komponente wird hinzugefügt: storage

Fehler beim COM-Aufruf ""m_pVssBackup->AddToSnapshotSet"".

Fehler beim letzten Vorgang.
	- HRESULT (zurückgegeben): 8004230f
	- Fehlertext: VSS_E_UNEXPECTED_PROVIDER_ERROR

DISKSHADOW> exit

PS C:Windowssystem32> vssadmin list shadows
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

Es wurde keine Ergebnisse für die Abfrage gefunden.

PS C:Windowssystem32> vssadmin list providers
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

Anbietername: "Hyper-V IC Software Shadow Copy Provider"
   Anbietertyp: Software
   Anbieterkennung: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Version: 1.0.0.0

Anbietername: "Microsoft File Share Shadow Copy provider"
   Anbietertyp: Dateifreigabe
   Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Anbietername: "Microsoft Software Shadow Copy provider 1.0"
   Anbietertyp: System
   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Thanks!
Matt

Hey foggy!

I din’t really find WEL’s. Aktually I’m happy to get that ExchangeServer Backup running with unchecked «Enable application-aware image processing» — option!

The Veeam Support just said to me: Get your VSS stati running — otherwise get contact to Microsoft Support

Aktually I’m happy to get that ExchangeServer Backup running with unchecked «Enable application-aware image processing» — option!

Be aware that without AAIP processing option no additional preparation steps will be performed prior to taking snapshot. In other words, the machine will be in crash-consistent state — the same as it would be after a system failure or power outage. This might result in certain issues during restore.

The Veeam Support just said to me: Get your VSS stati running — otherwise get contact to Microsoft Support

Indeed, if VSS doesn’t work for some reasons, there is little we can do, as we solely rely on this technology.

Thanks.

Interesting think ’bout this is we moved Veeam to the final server after testing period were over. During that testing we already did backup the exchange 2013 server. After buying and movin the server manager to it’s final destination it stopped working…

One other thing that came to my mind is are there any ports needed when a Microsoft TMG 2010 is protecting that Network?

Hi Folks!

I moves our Veeam Server into the same subnet as the Exchange Server. So no firewall has to pass through!
And guess what? Same Errors

So we’re going back to find out why VSS is failing….

Not yet!

I can’t live with the point that’s not running from now on. I did app aware backups with the demo. From the day on I entered my VeeamLicence it stopped working!

So you guys are shure that this should run with the standard edition?

Another effect is that auto truncating seems to only work with app aware processing? Our Log HDD runs out of space

So you guys are shure that this should run with the standard edition?

Yep, all paid editions of VB&R has AAIP functionality.

Another effect is that auto truncating seems to only work with app aware processing?

Yes, in order to truncate logs you should enable AAIP. Otherwise, you can disable AAIP and control log truncation, using native MS tools.

Thanks.

Hi Folks!

I think I got a solution for this case:

I deleted this registry key:

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders{74600e39-7dc5-4567-a03b-f091d6c7b092}]
@="Hyper-V IC Software Shadow Copy Provider"
"Type"=dword:00000002
"Version"="1.0.0.0"
"VersionId"="{c797fff9-2c3e-453c-a3e9-cc7673a6c732}"

Then I got this output:

C:Windowssystem32>vssadmin list providers
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumesc

(C) Copyright 2001-2013 Microsoft Corp.

Anbietername: "Microsoft File Share Shadow Copy provider"
   Anbietertyp: Dateifreigabe
   Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Anbietername: "Microsoft Software Shadow Copy provider 1.0"
   Anbietertyp: System
   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Looks good. Restarted the VM.
Now i got this output:

C:Windowssystem32>vssadmin list providers
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumesc

(C) Copyright 2001-2013 Microsoft Corp.

Anbietername: "Microsoft File Share Shadow Copy provider"
   Anbietertyp: Dateifreigabe
   Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Anbietername: "Microsoft Software Shadow Copy provider 1.0"
   Anbietertyp: System
   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Anbietername: "Hyper-V IC Software Shadow Copy Provider"
   Anbietertyp: Software
   Anbieterkennung: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Version: 1.0.0.0

Seems to me he reinitialised that Hyper-V IC Shadow Copy Provider new?

SoI started an Active Full Backup with activated «application aware image processing».
It worked!

So my question is: why is that?
Could it be that this Hyper-V IC Shadow Provider got stucked when I had to restore that VM?

mb1811 wrote:So my question is: why is that?
Could it be that this Hyper-V IC Shadow Provider got stucked when I had to restore that VM?

This could be a consequence of the crash-consistent backup, from which the restore was performed. Glad you’re finally running fine though.

Thanks mb1811 your steps helped fix my problem.
I was getting these errors when Veeam was doing a backup.
Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing). Details: Writer ‘Microsoft Hyper-V VSS Writer’ is failed at ‘VSS_WS_FAILED_AT_PREPARE_SNAPSHOT’.
The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
Make sure VM does not have ‘iSCSI Software Target Storage Provider’ feature installed.
When running this cmd ‘vssadmin list providers’ only get the below 2x providers, no ‘Hyper-V IC Software Shadow Copy Provider’ listed.

		Provider name: 'Microsoft File Share Shadow Copy provider'
		   Provider type: Fileshare
		   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
		   Version: 1.0.0.1
		Provider name: 'Microsoft Software Shadow Copy provider 1.0'
		   Provider type: System
		   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
		   Version: 1.0.0.7

Deleted registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders{74600e39-7dc5-4567-a03b-f091d6c7b092}
Restarted this service ‘Hyper-V Volume Shadow Copy Requestor’
Then Veeam backup completed successfully.

2012 R2 host
1x 2012 R2 guest
2x 2008 R2 guests

After a reboot and try to run Veeam, it will fail on the 2x 2008 R2 guests every time.

8/24/2015 7:54:18 PM :: Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing). Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
The writer experienced a transient error.  If the backup process is retried,
the error may not reoccur.
--tr:Failed to verify writers state.
--tr:Failed to perform pre-backup tasks. 

8/24/2015 7:57:03 PM :: Retrying snapshot creation attempt (Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
The writer experienced a transient error.  If the backup process is retried,
the error may not reoccur.
--tr:Failed to verify writers state.
--tr:Failed to perform pre-backup tasks.) 

If I restart ‘Hyper-V Volume Shadow Copy Requestor’ on the guests, the retry goes perfect.

Any thoughts? Everything is patched. Veeam 8.0.0.2030.

Mark, please provide your support case ID, as it is required according to the rules of posting technical issues. Also, review the thread above, might be helpful.

Are there any related messages in the Windows Event Log? What about the ‘vssadmin list writers’ command output?

Hallo,

caseid: 01096218

I have the following problem. VSS Writer has a non-transient error 0x800423f4. This error probably appeared after upgrading one of the VMs from Windows 8.1 to Windows 10.
The Hyper-V is running on Windows Server 2012r2.

I already tried all kind of fixed but non of them worked.
— deleted old shadow copies
— restarted vmms.exe
— restarted service
— etc.

One writer is in this status after trying to backup:

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {6d8aa1bf-25b5-4080-aae1-29e8324796d6}
   State: [8] Failed
   Last error: Non-retryable error

Of course after restarting the vmms.exe bringts the writer back to normal state. However when I try to backup again the same error appears.

Any ideas?
Is this a general issue with windows 10?

Thank you
Josef

yes. I’m running Backup&Replication Version 8.0.0.2084

Host VM: Windows Server 2012 r2 (with all updates installed)
Guest VM: WIndows 10 Pro (with all updates installed).

The error appears when I try to backup the Guest VM. Not sure what the problem is.
vssadmin list writers etc. looks fine before backing up. Afterwards the Hyper-V writer has the state failed.

any ideas?

thanks
Josef

thanks!

I tried already some of the ideas. One said to delete this registiry key and restart the service:

Deleted registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders{74600e39-7dc5-4567-a03b-f091d6c7b092}
-> restart Hyper-V Volume Shadow Copy Requestor

However when I do this this provider (and the regestry key) are recreated after restarting the service (Hyper-V Requestor).

Maybe this would solve the issue, but the registry key is automatically added after restarting the service.

any ideas?

josef

jhoefler — at the moment I can’t comment on the rest of the issue, but it’s normal for the requester service to recreate the provider key; the only situation in which I have found it useful to delete the key and let it be recreated was when the key was already corrupted, though corruption might not be obvious so it’s a reasonable general troubleshooting step.

The Hyper-V IC provider is how the host communicates to the guest when creating a shadow copy in AAIP mode or Child Partition mode; it’s not possible to run Veeam Hyper-V backups in those modes without the IC provider. This is sometimes confusing to people used to troubleshooting VSS issues on other platforms, where the default Microsoft Software provider is used, and the presence of third-party providers can cause problems.

@foggy:
all writers are fine before starting a veeam backup. after the backup failed the hyper v writer has the state failed. after restarting the vmms.exe the writers are back to normal. (restarting also resets them). However the error persists.

@alanbolte:
thanks for your input on the requester service. so it seems that this behavior is ok.

it is just the backup of one windows 10 guest machine that has this problem. for me it seems windows 10 related. are there any further steps needed on windows 10 to use vss?

thanks for your help.

The Microsoft support could solve the problem.
Basically the Hyper-V IC provider was somehow missing on the guest system.

I was not following all steps done by the MS support, but one important was to run a shadow copy via windows backup on the guest system. Afterwards the Hyper-V IC provider was correctly set up (you can see this in the registry) on the guest system.

Now the backup for the server is finally working again.

best, josef

I’ve the exact same issue at all of our 3 subsidiary networks (Case # 01705369). they are configured quite similar: 2012 R2 Hyper-V with 4 VMs: DC, Exchange 2013, Fileserver, WSUS/Application Server. All of them are 2012 R2 Servers.

Results from Last nightly Backup run:
Subsidiary 1: successflull
Subsidiary 2: failed on Exchange 2013
Subsidiary 3: failed on Exchange 2013

Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing). Details: Writer ‘Microsoft Hyper-V VSS Writer’ is failed at ‘VSS_WS_FAILED_AT_PREPARE_SNAPSHOT’. The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. —tr:Failed to verify writers state. —tr:Failed to perform pre-backup tasks.
Make sure VM does not have ‘iSCSI Software Target Storage Provider’ feature installed.
Retrying snapshot creation attempt (Writer ‘Microsoft Hyper-V VSS Writer’ is failed at ‘VSS_WS_FAILED_AT_PREPARE_SNAPSHOT’. The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. —tr:Failed to verify writers state. —tr:Failed to perform pre-backup tasks.)
Task has been rescheduled
Unable to allocate processing resources. Error: Writer ‘Microsoft Hyper-V VSS Writer’ is failed at ‘VSS_WS_FAILED_AT_PREPARE_SNAPSHOT’. The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. —tr:Failed to verify writers state. —tr:Failed to perform pre-backup tasks.

vss admin list writers output from Subsidiary 2:

C:Windowssystem32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Hyper-V IC Software Shadow Copy Provider'
   Provider type: Software
   Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Version: 1.0.0.0

creating manual shadow copy:

C:Windowssystem32>diskshadow
Microsoft DiskShadow version 1.0
Copyright (C) 2013 Microsoft Corporation
On computer:  VMSRVPA113,  26/2/16 3:25:36 a. m.

DISKSHADOW> set verbose on
DISKSHADOW> set context volatile
DISKSHADOW> add volume c:
DISKSHADOW> create

The last operation failed.
        - Returned HRESULT: 80042318
        - Error text: VSS_E_WRITER_INFRASTRUCTURE

vss admin list writers output from Subsidiary 3:

C:Windowssystem32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

C:Windowssystem32>diskshadow
Microsoft DiskShadow version 1.0
Copyright (C) 2013 Microsoft Corporation
On computer:  VMSRVLIVLI113,  26.02.2016 09:26:42

DISKSHADOW> set verbose on
DISKSHADOW> set context volatile
DISKSHADOW> add volume c:
DISKSHADOW> create

The last operation failed.
        - Returned HRESULT: 80042318
        - Error text: VSS_E_WRITER_INFRASTRUCTURE

As a temporary solution, stop the (running) volume shadow copy service, and in most cases the backup is successfully on next run.

@jhoefler, would you please provide me the steps from Microsoft?

Any other tips?

Thank you.

Support Case ID: # 01754440
Situation: Hyper-V on Server2012 R2 Std in domain. All updates installed. Two servers.
Veeam B&R 8.0 update 3.
VMs 2008R2 and 2012R2.
Problem: Backing up the VMs with setting «Enable application-aware image processing» — the job fails with this Error:

05.04.2016 18:13:44 :: Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing). Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
Vss error: '0x800423f4'
--tr:Failed to verify writers state.
--tr:Failed to perform pre-backup tasks. 
05.04.2016 18:13:55 :: Make sure VM does not have 'iSCSI Software Target Storage Provider' feature installed. 
05.04.2016 18:14:00 :: Retrying snapshot creation attempt (Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
Vss error: '0x800423f4'
--tr:Failed to verify writers state.
--tr:Failed to perform pre-backup tasks.) 
05.04.2016 18:15:03 :: Unable to allocate processing resources. Error: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.
Vss error: '0x800423f4'
--tr:Failed to verify writers state.
--tr:Failed to perform pre-backup tasks. 

restart of VMMS and VSS services dont work.
Only after restart the Hyper-V hosts i can make one backup before error return.

On host:

Имя компонента записи: "Microsoft Hyper-V VSS Writer"
   Id компонента записи: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Id экземпляра компонента записи: {deb6ab9d-d438-4723-aae2-a660c7401b46}
   Состояние: [8] Неисправен
   Последняя ошибка: Неповторяемая ошибка

Its production VMS! Please help!

26 июня 2016
chum Написать комментарий
К комментариям

Событие отклонено модулем записи VSS с ошибкой 0x800423f4 такую ошибку можно встретить когда выполняется бэкап hyper-v.

У меня получилось решить проблему в лоб отключив у виртуальной машин в разделе «Службы интеграции» — «Архивация (контрольная точка). После этого проблема решена, как решить проблему с включением этой опции для меня остается загадкой…

Categories: Windows Tags: 0x800423f4, hyper-v, vss, windows 2012 r2

Комментарии (0)
Уведомления (0)
Написать комментарий
Уведомление

1. Пока что нет комментариев.

1. Пока что нет уведомлений.

Имя (обязательно)

E-mail (не публикуется) (обязательно)

Вебсайт

Подписаться на комментарии по RSS

RSS

• Google
• Youdao
• Xian Guo
• Zhua Xia
• My Yahoo!
• newsgator
• Bloglines
• iNezha

Рекомендуем

Видеохостинг/Вебинары

Свежие комментарии

• Alex к записи Не удалось подключиться к домену, либо потому что контроллер ….
• Николай к записи Простой способ выгрузки таблицы в excel из PHP
• Николка к записи Мониторинг raid контроллера Smart Array P410i
• Ильфат к записи Pandion кастомизация для корпоративной сети
• k0fe к записи Mikrotik несколько ip адресов на одном wan интерфейсе

Присоединяйтесь к нам

Полезные заметки

• На контроллере домена нет общих ресурсов Sysvol и Netlogon
• Принудительный захват ролей умершего мастера операций

Полезные сервисы

• Декодер
• Онлайн конвертор
• Файловый хостинг backnet.ru

Архивы

• Сентябрь 2020
• Август 2020
• Март 2020
• Февраль 2020
• Февраль 2019
• Январь 2019
• Декабрь 2018
• Октябрь 2018
• Сентябрь 2018
• Август 2018
• Июль 2018
• Февраль 2018
• Январь 2018
• Июль 2017
• Апрель 2017
• Март 2017
• Январь 2017
• Декабрь 2016
• Ноябрь 2016
• Октябрь 2016
• Август 2016
• Июль 2016
• Июнь 2016
• Май 2016
• Февраль 2016
• Декабрь 2015
• Ноябрь 2015
• Октябрь 2015
• Сентябрь 2015
• Август 2015
• Июль 2015
• Июнь 2015
• Май 2015
• Ноябрь 2014
• Август 2014
• Июнь 2014
• Май 2014
• Апрель 2014
• Декабрь 2013
• Октябрь 2013
• Сентябрь 2013
• Август 2013
• Июль 2013
• Май 2013
• Март 2013
• Февраль 2013
• Декабрь 2012
• Ноябрь 2012
• Октябрь 2012
• Сентябрь 2012
• Август 2012
• Июль 2012
• Июнь 2012
• Май 2012
• Апрель 2012
• Март 2012
• Февраль 2012
• Январь 2012
• Декабрь 2011
• Ноябрь 2011