Alternative ways….on How to convert a physical HDD to a vhd
March 23, 2011
VPN network problems on multigateway infrastructures
July 22, 2011
I came up to this error yesterday with a W2k3 SP2 DC/Exchange (also seen on W2k8).Volume shadow copy creation: Attempt 1. “COM+ REGDB Writer” has reported an error 0x800423f4. This is part of System State. The backup cannot continue.
Error returned while creating the volume shadow copy:800423f4
Aborting Backup.
———————-
The operation did not successfully complete.
This is actually a Microsoft VSS snapshot provider error (“Unexpected provider error”) causing the backup process to fail.
The resolution is quite simple if you are lucky and you don’t need to re-register COM+ objects.
Fire up dos prompt (Start>Run>Cmd) and give the following command:
C:\>vssadmin list writers
A list of the availiable writers will follow.
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: ‘System Writer’
Writer Id:…………………….
Writer Instance Id:……………..
State: [1] Stable
Last error: No error
Look carefully on this list. The writers with State: [1] Stable and Last error: No error are ok.
But if you see
State: [9] Failed
Last error: Retryable error
The writer having this is the problematic one.
In my case (with the backup failing) the following had a state of fail:
‘COM+ REGDB Writer’
If you are using BackupExec it is possible to find the following with error as well:
‘TermServLicensing’
‘WMI Writer’
‘FRS Writer’
This is resolved easily like this.
The VSS Provider needs to be removed. Delete the associated registry key for the Provider Id by using the following DOS command:
C:\>REG DELETE “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{xxxxxx}” /F
where xxxx is the provider id of the problematic vss provider/object.
Then simply restart the VSS service
C:\>net stop vss
The Volume Shadow Copy service is stopping.
The Volume Shadow Copy service was stopped successfully.
C:\>net start vss
The Volume Shadow Copy service is starting.
The Volume Shadow Copy service was started successfully
Remember that if you don’t try the windows backup the command “vssadmin list writers” will show as not in error. Try to start the backup again and check if it runs.
In another case I had to register the vss by using the following in a batch file.
cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
pause
Hope this helps some of us. 🙂
