Loading
3 pages 1 2 3
Tweaking.com - Registry Backup Online Help & FAQ
Posted by: Shane on: 05/30/2012 06:05 PM [ Print | 0 comment(s) ]
Tweaking.com - Registry Backup Troubleshooting
Backup failed, Volume Shadow Copy Failed.
The program relies on the Volume Shadow Copy service to backup the registry files. Below is a list of fixes that I have gathered that can help repair the Volume Shadow Copy.
If not of them work feel free to post in the forums and I can help you further.
If the volume shadow copy service fails it is best to try and fix it. But as of v1.2.0 of the program if for any reason VSS fails the program will use the old API backup method. :-)
Solution #1
I have built a volume shadow copy repair tool that registers the volume shadow copy files, once ran reboot the system.
Also run the repair wmi repair tool as well.
Repair Volume Shadow Copy Service
Repair WMI
Reboot. For some reason, systems that haven't been rebooted in a while cause VSS to malfunction. As all Microsoft veterans know, you need to reboot regularly as a preventive and cleanup measure for your system. Rebooting will eliminate VSS problems caused by transient VSS errors.
Solution #2
VSS error 8193 in Event Viewer
HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
Please open the registry editor (regedit) by clicking the Start orb then typing regedit and pressing Enter.
Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.
Please backup the registry key first, and then delete that entry with the extra ".bak"
Then reboot.
Solution #3
Error 1053
I have had similar problems with VSS on XP machines that turned out to be caused by the MS Software Shadow Copy Provider Service (SwPrv). You should be able to manually start and stop both VSS and SwPrv (net start vss) (net start SwPrv). If VSS manually starts OK, but you get an error when trying to start SwPrV, then you could have a permissions problem with it (account used to start it? should be system account), or a registry error with the services command line. I have run across several situations with XP machines where the command line for the SwPrv service is incorrect.
Possible Solution (these instructions are for XP)
Open Control Panel, Administrative Tools, COMPONENT Services
Inside the Console Root folder, goto COMPONENT Services -> Computers -> My Computer -> Com+ Applications.
On the top toolbar, click on View, Status (or click the Status button on the toolbar).
You will see all Com+ applications and their statuses including the Application ID and the PID (if currently running).
Make a note of the Application ID for the MS Software Shadow Copy Provider entry.
Next check the command line used for the SwPrv service. Navigate back to the top root folder. Inside the Console Root folder, goto Services (local). Note, you can also get here from Control Panel, Administrative Tools, Services.
Find the MS Software Shadow Copy Provider Service and double click on it. Notice the Path to Executable field. It will have an entry similar to the following:
C:\WINDOWS\System32\dllhost.exe /Processid:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Check to make sure that the GUID inside the curly brackets is the exact same as what you found in the Application ID in the first step. If it isn't, then this is what is preventing the service from starting.
To correct, open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SwPrv
Double click on the ImagePath value and make the necessary correction.
It is obviously a good idea to export a backup reg file of the above key in case you make a mistake or need to restore the original settings.
Solution #4
No VSS writers are listed when you run vssadmin list writers on Windows Server 2008
http://support.microsoft.com/kb/2009533
1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}
3. Locate the TypeLib registry value.
NOTE The registry type of TypeLib should be shown as REG_EXPAND_SZ. If that is not the case, you have to delete the key, and then you have to recreate the key. To do this, follow these two steps:
a. Select the TypeLib registry value, and then delete it.
b. Create a new Expandable String Value, and then name it TypeLib.
4. Double-click the TypeLib registry value. In the Value Data box, type %systemroot%\system32\EVENTCLS.DLL, and then click OK.
5. Close Regedit.
6. Click Start, type services.msc in the Start Search box, and hit Enter.
7. Right-click the following services one at a time and click Restart:
• COM+ Event System
• Volume Shadow Copy
8. Close the Services snap-in.
9. Open an elevated command prompt, type vssadmin list writers, and then hit ENTER.
10. Verify that the VSS writers are now listed.
Solution #5
Your computer may have a corrupt COM+ subscription information. Open the registry editor (regedit) and navigate to:
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}
Then delete the Subscriptions key and reboot the machine.
A subsequent call in the command prompt should show no more errors: vssadmin list writers
This VSS repair strategy appears to work well when the System Writer is reporting an error. The Event Viewer may be reporting this or a similar error:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {34162f4c-59ff-468e-848d-cb4b3d8dd7dc}
Solution #6
Open vssadmin from the command line (run cmd as administrator).
Enter vssadmin delete shadows /all to clean up any dead VSS snapshots. Some defect systems accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become unresponsive.
Enter vssadmin list writers and check for errors. If you receive any errors for one VSS writer, you may need to fix that particular VSS writer. It is common to receive writer errors caused by Microsoft's Virtual Server 2005 VSS writer.
If you see a VSS writer error, try the following:
Restart the services: COM+ System Application Service, Distributed Transaction Coordinator Service, and Volume Shadow Copy Service
and also restart the affected VSS writer service, for example Virtual Server 2005 VSS writer or Hyper-V VSS writer.
Check the Event Viewer for any additional error information logged by that VSS writer.
Solution #7
I have seen VSS writers of other backup software manufacturers cause system instability and errors.
Open the Registry Editor (regedit) as administrator and check the following branch: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers
Underneath that key you should only find Microsoft Software Shadow Copy Provider 1.0 and no other VSS writer. If you do find another, it may be a residue registry entry of a previous backup software installation. You can save the entry by exporting the entire registry to a file (right click and select Export) and then it's safe to delete the entire branch entry underneath HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Provider.
Then reboot and try again running vssadmin list writers to confirm the problem has been resolved.
Solution #8
On some systems, the command vssadmin delete shadows isn't available. In Windows XP that's okay because VSS snapshots can't be persistent on XP (a reboot will get rid off them); however, on Vista you need to delete old shadows using:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=300MB
300MB is usually the smallest amount you can specify and will effectively delete any existing VSS snapshots on your system.
If you don't get any VSS writer errors when using vssadmin list writers but the system isn't able to create a new VSS snapshot (and you have deleted all existing snapshots), then you may have to actually increase the max shadow storage size on your system. Use the previous command with a greater number, such as 10GB:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10GB
Note that it is also possible to allocate shadow copy storage space on a different drive, as along as it's local:
vssadmin Resize ShadowStorage /For=C: /On=X: /MaxSize=200GB
Solution #9
If the VSS error code 0x800423f3 is reported, the reason is a corrupt state of WMI (wmiutils.dll). This may happen if a registry cleaner was used or a third-party application was uninstalled incorrectly. What you need to do is re-register wmiutils.dll and then restart the WMI service.
In the command prompt, execute the following three lines (note that stopping the WMI service does NOT stop VMs, it only stops the management service):
net stop winmgmt
regsvr32 wmiutils.dll
net start winmgmt
Backup failed, Volume Shadow Copy Failed.
The program relies on the Volume Shadow Copy service to backup the registry files. Below is a list of fixes that I have gathered that can help repair the Volume Shadow Copy.
If not of them work feel free to post in the forums and I can help you further.
If the volume shadow copy service fails it is best to try and fix it. But as of v1.2.0 of the program if for any reason VSS fails the program will use the old API backup method. :-)
Solution #1
I have built a volume shadow copy repair tool that registers the volume shadow copy files, once ran reboot the system.
Also run the repair wmi repair tool as well.
Repair Volume Shadow Copy Service
Repair WMI
Reboot. For some reason, systems that haven't been rebooted in a while cause VSS to malfunction. As all Microsoft veterans know, you need to reboot regularly as a preventive and cleanup measure for your system. Rebooting will eliminate VSS problems caused by transient VSS errors.
Solution #2
VSS error 8193 in Event Viewer
HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
Please open the registry editor (regedit) by clicking the Start orb then typing regedit and pressing Enter.
Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.
Please backup the registry key first, and then delete that entry with the extra ".bak"
Then reboot.
Solution #3
Error 1053
I have had similar problems with VSS on XP machines that turned out to be caused by the MS Software Shadow Copy Provider Service (SwPrv). You should be able to manually start and stop both VSS and SwPrv (net start vss) (net start SwPrv). If VSS manually starts OK, but you get an error when trying to start SwPrV, then you could have a permissions problem with it (account used to start it? should be system account), or a registry error with the services command line. I have run across several situations with XP machines where the command line for the SwPrv service is incorrect.
Possible Solution (these instructions are for XP)
Open Control Panel, Administrative Tools, COMPONENT Services
Inside the Console Root folder, goto COMPONENT Services -> Computers -> My Computer -> Com+ Applications.
On the top toolbar, click on View, Status (or click the Status button on the toolbar).
You will see all Com+ applications and their statuses including the Application ID and the PID (if currently running).
Make a note of the Application ID for the MS Software Shadow Copy Provider entry.
Next check the command line used for the SwPrv service. Navigate back to the top root folder. Inside the Console Root folder, goto Services (local). Note, you can also get here from Control Panel, Administrative Tools, Services.
Find the MS Software Shadow Copy Provider Service and double click on it. Notice the Path to Executable field. It will have an entry similar to the following:
C:\WINDOWS\System32\dllhost.exe /Processid:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Check to make sure that the GUID inside the curly brackets is the exact same as what you found in the Application ID in the first step. If it isn't, then this is what is preventing the service from starting.
To correct, open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SwPrv
Double click on the ImagePath value and make the necessary correction.
It is obviously a good idea to export a backup reg file of the above key in case you make a mistake or need to restore the original settings.
Solution #4
No VSS writers are listed when you run vssadmin list writers on Windows Server 2008
http://support.microsoft.com/kb/2009533
1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}
3. Locate the TypeLib registry value.
NOTE The registry type of TypeLib should be shown as REG_EXPAND_SZ. If that is not the case, you have to delete the key, and then you have to recreate the key. To do this, follow these two steps:
a. Select the TypeLib registry value, and then delete it.
b. Create a new Expandable String Value, and then name it TypeLib.
4. Double-click the TypeLib registry value. In the Value Data box, type %systemroot%\system32\EVENTCLS.DLL, and then click OK.
5. Close Regedit.
6. Click Start, type services.msc in the Start Search box, and hit Enter.
7. Right-click the following services one at a time and click Restart:
• COM+ Event System
• Volume Shadow Copy
8. Close the Services snap-in.
9. Open an elevated command prompt, type vssadmin list writers, and then hit ENTER.
10. Verify that the VSS writers are now listed.
Solution #5
Your computer may have a corrupt COM+ subscription information. Open the registry editor (regedit) and navigate to:
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}
Then delete the Subscriptions key and reboot the machine.
A subsequent call in the command prompt should show no more errors: vssadmin list writers
This VSS repair strategy appears to work well when the System Writer is reporting an error. The Event Viewer may be reporting this or a similar error:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {34162f4c-59ff-468e-848d-cb4b3d8dd7dc}
Solution #6
Open vssadmin from the command line (run cmd as administrator).
Enter vssadmin delete shadows /all to clean up any dead VSS snapshots. Some defect systems accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become unresponsive.
Enter vssadmin list writers and check for errors. If you receive any errors for one VSS writer, you may need to fix that particular VSS writer. It is common to receive writer errors caused by Microsoft's Virtual Server 2005 VSS writer.
If you see a VSS writer error, try the following:
Restart the services: COM+ System Application Service, Distributed Transaction Coordinator Service, and Volume Shadow Copy Service
and also restart the affected VSS writer service, for example Virtual Server 2005 VSS writer or Hyper-V VSS writer.
Check the Event Viewer for any additional error information logged by that VSS writer.
Solution #7
I have seen VSS writers of other backup software manufacturers cause system instability and errors.
Open the Registry Editor (regedit) as administrator and check the following branch: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers
Underneath that key you should only find Microsoft Software Shadow Copy Provider 1.0 and no other VSS writer. If you do find another, it may be a residue registry entry of a previous backup software installation. You can save the entry by exporting the entire registry to a file (right click and select Export) and then it's safe to delete the entire branch entry underneath HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Provider.
Then reboot and try again running vssadmin list writers to confirm the problem has been resolved.
Solution #8
On some systems, the command vssadmin delete shadows isn't available. In Windows XP that's okay because VSS snapshots can't be persistent on XP (a reboot will get rid off them); however, on Vista you need to delete old shadows using:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=300MB
300MB is usually the smallest amount you can specify and will effectively delete any existing VSS snapshots on your system.
If you don't get any VSS writer errors when using vssadmin list writers but the system isn't able to create a new VSS snapshot (and you have deleted all existing snapshots), then you may have to actually increase the max shadow storage size on your system. Use the previous command with a greater number, such as 10GB:
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10GB
Note that it is also possible to allocate shadow copy storage space on a different drive, as along as it's local:
vssadmin Resize ShadowStorage /For=C: /On=X: /MaxSize=200GB
Solution #9
If the VSS error code 0x800423f3 is reported, the reason is a corrupt state of WMI (wmiutils.dll). This may happen if a registry cleaner was used or a third-party application was uninstalled incorrectly. What you need to do is re-register wmiutils.dll and then restart the WMI service.
In the command prompt, execute the following three lines (note that stopping the WMI service does NOT stop VMs, it only stops the management service):
net stop winmgmt
regsvr32 wmiutils.dll
net start winmgmt
3 pages 1 2 3