- When VSS fails there is usually an indication in the image or backup log file which shows in the Macrium Reflect log:
- Alternatively, the main VSS log can be seen as an option under the log view:
- If required, and you are using the Macrium Reflect email component, you can send these logs via email. Right click the log entry.
- select Send backup logs via email.
- A common error is Failed to Create Volume Snapshot followed by a hex result code. The result code is an error code from VSS. Googling VSS + Result Code often comes up with a solution to the VSS problems
You may also see:
This may be associated with a 'VolSnap' error in your Windows logs.
VSS uses writer components to ensure that the file system is in a stable state when creating your disk image. For example, SQL database writers ensure that all transactions to databases are complete before allowing the shadow copy service to continue. Windows includes a VSS administration program that can list the status of all VSS Writers you have on your system.
Open a command prompt and type 'vssadmin list writers'. In Vista/7/8 and Servers 2008 and later, make sure you start the command prompt with elevated privileges. This will list all your VSS writers with their current state and last error. (Link to instructions on creating elevated command prompt at bottom of tutorial).
Writers with an error state or where the last error isn't 'No Error' are probably causing a problem.
Look for messages in your Windows logs.
When VSS fails you will always get a corresponding message in your Windows event log.
- Right click on 'My computer'
- Select 'Manage'
- Expand the 'Event Viewer' node
- Look in the 'Application' message node for error messages relating to 'VSS', 'Shadow Copy' or 'VolSnap'.
- If you find any messages then these with give you an 'Event ID' and sometimes a 'Result Code' or 'hr'. These two pieces of information can generally pin point the cause of your VSS failure. Try Googling the Event ID(s) and Result Code(s) for more information.
Make sure that the VSS service isn't disabled
Changing the startup type of the VSS service and rebooting can often resolve issues.
- Right click on 'My Computer'.
- Select 'Manage'.
- Select the 'Services' tree node.
- Right click on 'Volume Shadow Copy'
- Select Properties
- Change the startup type to 'Automatic'
Re-register the VSS components
Sometimes re-registering VSS core components can fix errors. Copy the following commands to Notepad and save the file with a '.bat' extension. Run the .bat file by opening a command prompt and entering the .bat file name.
We also provide a program which will recreate the correct registry setting and re-register all VSS components. Please download one of the below programs to fix your problem:
VSSfix 32bit - download
VSSfix 64bit - download
VSS error articles:
- Identifying, diagnosing and reporting VSS errors
- Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state
- 'SPSearch4 VSS Writer' is in failed state! (Result Code: 0x8000ffff)
- VSS Error: 0x8004230F
- VSS Error 0x80042318 - Failed to Create Volume Snapshot
- VSS Error: 0x80042317: Failed to Create Volume Snapshot
- VSS Error: 0x8004231f - Failed to Create Volume Snapshot 1
- VSS Error - Backup aborted! - Failed To Create Volume Snapshot. Result Code: 0x8004230c
- VSS Error - ERROR: Selected writer 'Dhcp Jet Writer' is in failed state
- VSS Error - ERROR: Selected writer 'NTDS' is in failed state!
- VSS errors occur and Windows Event 12293 is also present on Windows Server 2008 R2 without BitLocker
- VSS fails due to disks with a non-standard sector size
- VSS fails due to modification by 3rd party software
- VSS Error:0x8000ffff - Backup aborted! - Failed To Create Volume Snapshot.
- VSS Error: 0x800423f3 - Selected writer 'WMI Writer' is in failed state!
- VSS Error: 0x80042306 - Volume Shadow Copy Error
- VSS Error - Selected writer Registry Writer is in failed state
- VSS error: VSS_E_SNAPSHOT_SET_IN_PROGRESS
- VSS Error - 8193 Unexpected error calling routine ConvertStringSidToSid
It is very probable that others have had a similar problem to you, so use Google as much as you can to find potential solutions. If all else fails you should contact Microsoft support for a resolution.