How to troubleshoot "AOFO: Initialization failure" errors for "Microsoft Volume Shadow Copy Service (VSS)" service during Backups/Restores.
Problem
How to troubleshoot "AOFO: Initialization failure" errors for "Microsoft Volume Shadow Copy Service (VSS)" service during Backups/Restores.
Error Message
Error 1:
Final error: 0x80042316 - 0x80042316 (2147754774)
Final error category: Other Errors
V-79-10000-11253 - Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure".
V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time. Try running the job later.
Error 2:
Final error: 0xe000fe7d - Access is denied.
To back up or restore System State, administrator privileges are required.
Final error category: Security Errors
V-79-57344-34110 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FE7D): Access is denied. To back up or restore System State, administrator privileges are required. Check the Windows Event Viewer for details.
or
V-79-57344-65266 - AOFO: Initialization failure on: "<db,file or folder name>". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Error 3:
AOFO: Snapshot error 0x8000ffff : Catastrophic Failure
Final error: 0x8000ffff - Catastrophic failure
Final error category: Other Errors
For additional information regarding this error refer to link V-79-32768-65535
V-79-57344-34110 - Note: Resource: "\\"SERVERNAME"\Microsoft Information Store\First Storage Group" is not snappable. Attempting to back up directly from the source volume.
- AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11253 - Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy.
Cause
VSS based backups/restores may fail with various AOFO initialization errors. Windows Application log on the affected server may report various VSS related errors/warnings like, Event ID 20 or Event ID 8193 for event source "VSS". Description for event ID 20 and Event ID 8193 is shown in section 1 and Section 2 respectively:
Section 1.
***************************************************************************************************************
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154]
***************************************************************************************************************
Section 2.
***************************************************************************************************************
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
***************************************************************************************************************
To confirm the status of VSS writers, on the affected server run vssadmin list writers from command prompt. It may not show some/any writers at the prompt.
If the writers are not listed follow the steps listed below in Section A and Section B.
Section 3.
The error mentioned above in 'Error 3', happens due to one or more of the following:
The backup to disk folder being used is selected for an Advanced Open File Option (AOFO) backup.
Volume Shadow Copy Service Provider (VSS) is not started on the target machine.
Remote Agent for Windows Servers (RAWS) is not installed on the target machine.
No Network Connectivity to the target machine.
Advanced Open File Option (AOFO) is not installed on the target machine.
Solution
Note: The list below includes configuration changes that have been provided by our customer base to resolve VSS related issues. It is advisable to consult Microsoft before making the changes below:
Section A:
To register / re-register Microsoft Shadow Copy Provider and Volume Shadow Copy Services DLLs
1. Open a command prompt (Start>Run>CMD).
2. Execute the following commands:
Net stop vss
Net stop swprv
3. Change directory to \windows\system32 (i.e.: cd C:\windows\system32)
4. Register the below mentioned .dll files by executing the following commands:
Note: To speed this proccess up copy the below commands in the current format into notepad and save as vss.bat, then execute the batch file. This will execute all of the commands.
regsvr32 ole32.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 msxml2.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
regsvr32 msxml6.dll
5. Execute the following commands:
Net Start vss
Net Start swprv
6. Re-run the command vssadmin list writers.
If VSS issue still persists refer to the following Microsoft KB article
https://support.microsoft.com/kb/940032
After following Section A if the issue still persists, follow Section B.
Section B:
1. Stop the Microsoft Shadow Copy Provider &Volume Shadow Copy Service.
2. Export the contents of the HKLM\Software\Microsoft\EventSystem key to a .regfile.
Warning:Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
3. Delete the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key. (Do not delete the EventClasses key).
4. Restart the server.
5. Run the"VSSADMIN LIST WRITERS" command.
This causes the VSS entries in the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key to be rebuilt when the writers initialize.
6. If an error is observed on "step 5" Install the Microsoft HotFix :- 940349 .
Section C:
- Verify VSS is started on the target machine
- Go to, Windows Services console (Start > Run > type Services.msc)
- Check for Volume Shadow Copy and Microsoft Software Shadow Copy Provider
Note: Both services should have start up type set to 'Manual'. When Backup Exec tries to backup the Shadow Copy Components, it attempts to start the service if its not already started.
- Verify RAWS is installed and started on the target machine.
- Go to, Windows Services console (Start > Run > type Services.msc)
- Check for Backup Exec Remote Agent for Windows Systems
Note: Make sure the service is 'Started' and is running under 'Local System Account'
- Verify AOFO is installed on the target machine
- Go to System Information (Start > Run > type msinfo32)
- Expand Software Environment - System Drivers - Locate 'vsp.sys'
- Verify the Backup to Disk folders being used are not selected for backup.
- Verify the Network Connectivity outside Backup Exec.
Applies To
Windows Server 2003
Windows Server 2003 R2
Note: DO NOT USE these steps if using Windows 2008 or newer operating systems - please review to the "Important" statement in the following Microsoft KB article for confirmation that VSS re-registation should not be performed in this way with newer operating systems
References
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.