Vss error: 0x800423f4

Hyper-V specific discussions

Vss error: 0x800423f4

Veeam Logoby mb1811 » Thu May 08, 2014 11:56 am

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:
Code: Select all
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.

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

Code: Select all
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:
Code: Select all
PS C:\Windows\system32> 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:
Code: Select all
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 "\BCD\BCD" 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 "\BCD\BCD" 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 Server\Microsoft Information Store\LEMONQUEEN\87879ae5-c7d3-4f11-b9ed-b207b4e83588
   + Komponente wird hinzugefügt: \Microsoft Exchange Server\Microsoft Information Store\LEMONQUEEN\e9074ce1-63bd-47aa-b276-6bd3ee44f499
   + Komponente wird hinzugefügt: \Microsoft Exchange Server\Microsoft Information Store\LEMONQUEEN\1abbd199-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


Code: Select all
PS C:\Windows\system32> 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.


Code: Select all
PS C:\Windows\system32> 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
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby foggy » Sun May 11, 2014 9:14 pm

Matt, are there any related messages in the Windows Event Log? Please also review this existing thread for some hints.
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Mon May 12, 2014 6:23 am

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 :(
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby v.Eremin » Mon May 12, 2014 8:26 am

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.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Mon May 12, 2014 9:11 am

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?
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby v.Eremin » Mon May 12, 2014 9:13 am

All the ports required for AAIP are mentioned in the corresponding section of our online Help Center. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Tue May 13, 2014 8:54 am

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....
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby foggy » Wed May 14, 2014 10:38 am

Have you contacted Microsoft with that?
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Tue May 20, 2014 10:09 am

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 :(
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Tue May 20, 2014 10:15 am

EDIT: We had to recover that exchange virtual machine. He did write a new MachineID.
Could it be that this is the main cause? Is there any way to check the HDD ID's or to rearange them?
mb1811
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby v.Eremin » Tue May 20, 2014 10:17 am

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.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Vss error: 0x800423f4

Veeam Logoby mb1811 » Thu May 22, 2014 8:17 am 1 person likes this post

Hi Folks!

I think I got a solution for this case:

I deleted this registry key:
Code: Select all
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{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:
Code: Select all
C:\Windows\system32>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:
Code: Select all
C:\Windows\system32>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
Novice
 
Posts: 9
Liked: 1 time
Joined: Tue Apr 29, 2014 7:08 am
Full Name: MB1811

Re: Vss error: 0x800423f4

Veeam Logoby foggy » Fri May 23, 2014 2:34 pm

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.
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Vss error: 0x800423f4

Veeam Logoby jed-hyper » Mon Dec 08, 2014 3:14 am 2 people like this post

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.
Code: Select all
      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_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{74600e39-7dc5-4567-a03b-f091d6c7b092}
Restarted this service 'Hyper-V Volume Shadow Copy Requestor'
Then Veeam backup completed successfully.
jed-hyper
Enthusiast
 
Posts: 33
Liked: 4 times
Joined: Wed Feb 26, 2014 4:42 am
Full Name: Jed Parkes

Re: Vss error: 0x800423f4

Veeam Logoby Crofex » Wed Feb 04, 2015 9:38 am

Have you done this on the VM directly or on the Host? I´ve done it on the VM and the failure occured again... Looking for a Solution since month and Veeam-Support says the same: "Ask Microsoft"...
Crofex
Lurker
 
Posts: 1
Liked: never
Joined: Wed Feb 04, 2015 9:31 am

Next

Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 6 guests

cron