02 Failed to create a VSS snapshot
02 Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.
here are several Volume Shadow Service (VSS) issues that will generate the following error code:
Error Code 17:55
Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.
The JobManager.log file with have this type of entry:
Scheduler Set pending cause [Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.]::Client [server name] Application [FileScan] Message Id [285212727] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].
Scheduler Phase [Failed] message received from [server name] Module [FileScan] Token [37376:4:1] restartPhase [0]
JobSvr Obj Phase [4-Scan] for Backup Job Failed. Backup will continue with phase [Scan].
For these errors / issues there is always a matching OS Event Log entry with similar time stamp as the underlying errors are Windows OS VSS errors. Depending on the OS errors’ source the “Application” or “System” will have the entry.
For all the issues symptoms mentioned below see the “Cause” section for how to generate the VSS reports to confirm and resolve which root cause needs addressing.
Issue #1 (VSS unsupported partition type) (Refer to the “Cause” section to generate the reports to troubleshoot)
An active partition that is not NTFS formatted and contains System State components. VSS is required to backup System State Components.
Issue #2 (Writers in Bad State or required Writer missing) (Refer to the “Cause” section to generate the reports to troubleshoot)
There are VSS writer errors. The Windows OS Servers’ “Application” or “System” Event logs will have VSS or VolSnap errors logged. The writers on the box are showing some errors.
Writer name: ‘System Writer’
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {a9e9ad80-b17f-43fc-abde-693530722a5f}
State: [9] Failed
Last error: Timed out
Writer name: ‘WMI Writer’
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3ded1ea5-65c9-4e2b-bc0a-3064690a3eea}
State: [9] Failed
Last error: Timed out
Writer name: ‘Cluster Database’
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {448f854c-ed09-439e-aeae-0e35e952ddab}
State: [5] Waiting for completion
Last error: No error
The FileScan.log will have entries similar to this:
CsSnapRequestor::GatherWriterStatus() – Gathering writer status After DoSnapshotSet…
CsSnapRequestor::GatherWriterStatus() – 10 writers responded
STABLE status for writer ‘Task Scheduler Writer’. code S_OK
STABLE status for writer ‘VSS Metadata Store Writer’. code S_OK
STABLE status for writer ‘Performance Counters Writer’. code S_OK
FAILED_AT_FREEZE status for writer ‘ASR Writer’. code VSS_E_WRITERERROR_TIMEOUT
CsSnapRequestor::GatherWriterStatus() – Signaling bad state returned for writer [ASR Writer] engaged in backup.
FAILED_AT_FREEZE status for writer ‘System Writer’. code VSS_E_WRITERERROR_TIMEOUT
CsSnapRequestor::GatherWriterStatus() – Signaling bad state returned for writer [System Writer] engaged in backup.
FAILED_AT_FREEZE status for writer ‘Shadow Copy Optimization Writer’. codeVSS_E_WRITERERROR_TIMEOUT
FAILED_AT_FREEZE status for writer ‘COM+ REGDB Writer’. codeVSS_E_WRITERERROR_TIMEOUT
CsSnapRequestor::GatherWriterStatus() – Signaling bad state returned for writer [COM+ REGDB Writer] engaged in backup.
WAITING_FOR_BACKUP_COMPLETE status for writer ‘Registry Writer’. code S_OK
WAITING_FOR_BACKUP_COMPLETE status for writer ‘Cluster Database’. code S_OK
FAILED_AT_FREEZE status for writer ‘WMI Writer’. code VSS_E_WRITERERROR_TIMEOUT
CsSnapRequestor::GatherWriterStatus() – Signaling bad state returned for writer [WMI Writer] engaged in backup.
Call GatherWriterStatus(“After DoSnapshotSet”) [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Entering [CsSnapRequestor::DeleteFolderMetadata]
CsSnapRequestor::DeleteFolderMetadata() – Not attempting to delete folder metadata
Call DoShadowSet() [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Entering [CsSnapRequestor::BackupComplete]
Issue #3 (Diskshadow with malformed path) (Refer to the “Cause” section to generate the reports to troubleshoot)
There are Registry entries under the following HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services where the file path is malformed.
Examples:
– File List: Path = c:/progra~2/plixer~1\cgi-bin, Filespec = eventlogd.exe
– File List: Path = archivemanagerremoteinstaller, Filespec = remoteinstallerservice.exe
– File List: Path = c:/program files (x86)/ibm_ds/ibmstoragemanagerprofiler server\bin, Filespec = tomcat5.exe
– File List: Path = c:\windows\\systemroot\system32\drivers, Filespec = lsi_sas.sys
– File List: Path = \systemroot\c:\windows\system32, Filespec = svchost.exe
The FileScan.log will have entries similar to this:
CsSnapRequestor::StartSnapshotSet() – Created shadow set 8d7301ad-45d2-4b3f-aeb4-1af8b8612a70
Entering [CsSnapRequestor::AddVolumesToSnapshotSet]
Call m_vss->IsVolumeSupported(m_shadowProvider.GetProvider(), vol, &bSupported) [FAILED, throwing CV exception] – Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
Call AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] – Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
Entering [CsSnapRequestor::BackupComplete]
Entering [CsSnapRequestor::DeleteFolderMetadata]
Issue #4 (Space issue with the Volume Shadow Service) (Refer to the “Cause” section to generate the reports to troubleshoot)
From the Server OS System Event Log file:
TYPE] Error [TIME] 2011/09/23 09:03:04 [SOURCE] volsnap [COMPUTER] server name [DESCRIPTION] When preparing a new volume shadow copy for volume ?:, the shadow copy storage on volume ??: could not be located in non-critical space. Consider using a shadow copy storage volume that does not have any shadow copies.
The FileScan.log will have entries similar to this:
23924: [PID] [Thread] 09/23 09:03:05 [JobID] CsVssAsync::WaitUntilDone() – Async status returnedcode = 0x8004231f, Description = Unknown status.
23924: [PID] [Thread] 09/23 09:03:05 [JobID] CsSnapRequestor::DoShadowSet() – Call asyncShadow.WaitUntilDone() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
23925: [PID] [Thread] 09/23 09:03:05 [JobID] CsSnapRequestor::CreateSnapshotSet() – Call DoShadowSet() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
23926: [PID] [Thread] 09/23 09:03:05 [JobID] CsSnapRequestor::Snap() – Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
Issue # 5 (Multiple VSS Providers active on server) (Refer to the “Cause” section to generate the reports to troubleshoot)
The FileScan.log will have entries similar to this:
Call m_vss->IsVolumeSupported(m_shadowProvider.GetProvider(), vol, &bSupported) [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
Call AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
FindWorkThreadWrapper::w2kRecurse(4276): -Debug-: “C:\Users\addmtool\AppData\Local\History” is a junction point for “C:\Users\addmtool\AppData\Local\Microsoft\Windows\History”.
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
Issue #6 (Multiple VSS Snap Providers) (Refer to the “Cause” section to generate the reports to troubleshoot)
The FileScan.log will have entries similar to this:
Entering [CsSnapRequestor::DeleteFolderMetadata]
CsSnapRequestor::DeleteFolderMetadata() – Skipping delete of folder metadata.
Call DoShadowSet() [FAILED, throwing CV exception] – Code = 0x80042306, Description = VSS_E_PROVIDER_VETO
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80042306, Description = VSS_E_PROVIDER_VETO
Example of output showing multiple VSS providers from the Providers query command output text file.
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
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: ‘Data ONTAP VSS Hardware Provider’
Provider type: Hardware
Provider Id: {ddd3d232-a96f-4ac5-8f7b-250fd91fd102}
Version: 6. 3. 0. 4601
Cause:
To determine the cause of the VSS errors please run the following commands on the client from a cmd prompt with elevated privileges (Run as Administrator): (Windows 2008 and 2008 R2)
vssadmin list writers > c:\writers.txt
vssadmin list providers > c:\providers.txt
vssadmin list volumes > c:\volumes.txt
diskshadow /L c:\shadow.txt
list writers detailed
exit
For Windows 2003 please run these commands: (diskshadow does not exist on a 2003 server)
1) vssadmin list writers > c:\writers.txt
2) Mountvol > C:\moutvol.txt
3) VSSADMIN List SHADOWS > C:\Shadows.txt
4) VSSADMIN List SHADOWSTORAGE > C:\ShadowStorage.txt
5) vssadmin list providers > C:\providers.txt
See the “Additional Info” section for the links to the Microsoft® information on these commands.
From the Backup Job “Filescan.log” located on the Client Server for each of the following errors there is a matching error in the Windows OS Event log.
Related to Issue #1
=====================================================
CsSnapRequestor::AddVolumesToSnapshotSet() – Volume [\\?\VOLUME{4F1B4B6E-B1E6-11DF-990B-806E6F6E6963}\] not supported by provider
Call AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] – Code = 0x80320305, Description = Unknown error
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80320305, Description = Unknown error
Related to Issue #2
=====================================================
Call GatherWriterStatus(“After PrepareForBackup”) [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Call PrepareForBackup() [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80004005, Description = E_FAIL
Related to Issue #3
=====================================================
Entering [CsSnapRequestor::AddVolumesToSnapshotSet]
Call m_vss->IsVolumeSupported(m_shadowProvider.GetProvider(), vol, &bSupported) [FAILED, throwing CV exception] – Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
Related to Issue #4
=====================================================
CsVssAsync::WaitUntilDone() – Async status returned code = 0x8004231f, Description = Unknown status.
CsSnapRequestor::DoShadowSet() – Call asyncShadow.WaitUntilDone() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
CsSnapRequestor::CreateSnapshotSet() – Call DoShadowSet() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
CsSnapRequestor::Snap() – Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE
Related to Issue #5
=====================================================
Call asyncShadow.WaitUntilDone() [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
Entering [CsSnapRequestor::DeleteFolderMetadata]
CsSnapRequestor::DeleteFolderMetadata() – Skipping delete of folder metadata.
Call DoShadowSet() [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
Related to Issue #6
=====================================================
CsVssBackupComponents::SetBackupState() – Committing backup state: SelectComponents: [0], BootableSystemState: [0], BackupType: [5 – VSS_BT_COPY], PartialFileSuppport: [0]
CsVssBackupComponents::AddVolume() – Call p->AddToSnapshotSet((VSS_PWSZ)pwszVol, idProvider, &id) [FAILED, throwing CV exception] – Code=0x80042306, Description=VSS_E_PROVIDER_VETO
The errors below may be delivered for special cases of the Issues covered in this KB.
=====================================================
Entering [CsSnapRequestor::AddVolumesToSnapshotSet]
Call m_vss->IsVolumeSupported(m_shadowProvider.GetProvider(), vol, &bSupported) [FAILED, throwing CV exception] – Code = 0x80070057, Description = E_INVALIDARG
Call AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] – Code = 0x80070057, Description = E_INVALIDARG
Call CreateSnapshotSet() [FAILED, throwing CV exception] – Code = 0x80070057, Description = E_INVALIDARG
=====================================================
Call p->DoSnapshotSet(&asyncShadow) [SUCCESS] – Code=0x00000000, Description=S_OK
Entering [CsVssAsync::WaitUntilDone]
CsVssAsync::WaitUntilDone() – Async status returned code = 0x80042301, Description = Unknown status.
Call asyncShadow.WaitUntilDone() [FAILED, throwing CV exception] – Code=0x80042301, Description=VSS_E_BAD_STATE
Shadow Creation failed VSS_SoftwareSnap will not be used. Error -2147212543
=====================================================
Call p->IsVolumeSupported(idProvider, (VSS_PWSZ)pwszVol, &bSupported) [SUCCESS] – Code=0x00000000, Description=S_OK
Call p->AddToSnapshotSet((VSS_PWSZ)pwszVol, idProvider, &id) [FAILED, throwing CV exception] –Code=0x8004230c, Description=VSS_E_VOLUME_NOT_SUPPORTED
CVVIScan::VSSCreateSnap() – Shadow Creation failed, VSS_OpenFileManger will not be used, error=0x8004230C
CVVIScan::CreateVolumeSnap() – Failure during VSS Shadow creation
Resolution:
For Issue #1 please refer to the KB article link:
Backup Fails on Win2K8, Win2K8 R2 or Windows 7 where System State is Part of Backup
For Issue #2 use the “writers.txt file to determine which writer(s) are causing the problem.
In most cases with writer errors a reboot of the server will resolve the issues.
Also review the following KB to resolve missing writers that trigger the same Windows OS errors.
The System State Backup Job on Windows 2008 Servers Fail to Backup the System Protected Files
For Issue #3 use the shadow.txt file to examine the “File List: Path =” sections
Review the shadow.txt file and look for any File List: Path = statements that are not correct
The registry sections corresponding to the malformed paths will need to be corrected. Also make sure to contact the Vendors owning the file(s) affected as the Vendors’ installation process has created these malformed registry key path problems.
Example Registry Locations:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
Any path that has “/” instead of the normal backslash does not conform to the Windows LFS path standard. When the system writer sees any malformed path, it cannot quiesce the file system for the VSS provider to take the snapshot.
For Issue #4 please refer to the link and reference the “Vssadmin add shadowstorage” command.
http://technet.microsoft.com/en-us/library/cc788051(WS.10).aspx
For Issue #5
If the Commands in the “Cause” section return results similar to the following:
Volumes.txt
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: Unexpected failure: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Writers.txt
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
Providers.txt
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: Unexpected failure: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
DiskShadow.txt
DISKSHADOW> list writers detailed
COM call “(*vssObject)->InitializeForBackup” failed.
The last operation failed.
– Returned HRESULT: 80042302
– Error text: VSS_E_UNEXPECTED
DISKSHADOW> exit
writers detailed
These are indicating some issues with the Windows OS VSS services on the Server. The VSS services are not starting / running properly
The job is failing to take the VSS Snapshot on the server because the VSS service is not function properly. System State backup will leverage VSS to take a snapshot of the system state and VSS is failing here.
Here is some information on troubleshooting VSS:
1. Make sure that the following services are not disabled, and can be started:
a. Microsoft® Software Shadow Copy Provider
b. Remote Procedure Call (RPC)
c. Volume Shadow Copy)
2. Check the Application and System event logs for VOLSNAP / VSS errors.
3. Check what providers are installed, use this command: VSSADMIN LIST PROVIDERS
4. Check the writers and status, use this command: VSSADMIN LIST WRITERS
If the VSS issues persist then contact Microsoft® with respect to the VSS issue.
Volume Shadow Copy Service
Applies To: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista
technet.microsoft.com/en-us/library/ee923636(WS.10).aspx
Volume Shadow Copy Service Operations (1st link is 2008 R2, 2nd link is 2008)
technet.microsoft.com/en-us/library/dd364677(WS.10).aspx
technet.microsoft.com/en-us/library/cc734545(WS.10).aspx
Issue #6
The following Registry Key nUseVSSSoftwareProvider should be put in place on the Client machine with multiple VSS providers to force the use of the Microsoft VSS writers.
If the Client machine has more then one Agent iDA installed on it then the registry key will have to be ceated multiple times under the locations listed for those Agent types.
This is the starting root registry path for the Windows key: HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\instance
Use the Link provided to search on the key name nUseVSSSoftwareProvider to see current information and the exact subkey locations for the Key’s creation based on Agent type(s).
Version 9.0 Registry Keys and Parameters – search on – nUseVSSSoftwareProvider
Additional Info:
Vssadmin List
http://technet.microsoft.com/en-us/library/cc754968(WS.10).aspx
Diskshadow List
http://technet.microsoft.com/en-us/library/cc753848(WS.10).aspx
Vssadmin list writers
http://technet.microsoft.com/en-us/library/cc785468(WS.10).aspx
Vssadmin list volumes
http://technet.microsoft.com/en-us/library/cc788064(WS.10).aspx
Vssadmin list shadows
http://technet.microsoft.com/en-us/library/cc788116(WS.10).aspx
Vssadmin list providers
http://technet.microsoft.com/en-us/library/cc788108(WS.10).aspx
Volume Shadow Copy Service Operations
http://technet.microsoft.com/en-us/library/cc734545(WS.10).aspx
Volume Shadow Copy Service (1st link 2008, 2nd link 2008 R2)
http://technet.microsoft.com/en-us/library/cc734243(WS.10).aspx
http://technet.microsoft.com/en-us/library/dd364794(WS.10).aspx
Troubleshoot VSS issues which occur with Windows Server Backup (WBADMIN) on Windows Server 2008 and Server 2008 R2
http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
Volume Shadow Copy Service
InfoTech Fusion 