|Home > All Articles > Volume Shadow Copy Error 0x800423f4 - writer error: non retryable|
Volume Shadow Copy Error 0x800423f4 - writer error: non retryableLast modified on: 14th Aug 2015
[printer friendly page]
BA954 Volume Shadow Copy Error 0x800423f4 - writer error: non retryable
This error occurs when one of the VSS writers is not in a working state and causes the snapshot process to fail.
The error's known causes and resolutions are described below.
Known Cause 1 – Multiple backup solutions installed
Many backup solutions have their own proprietary snapshot manager which can cause conflicts with other backup solutions installed on the system.
If you have (or had) more than one backup program installed on your system, disable/uninstall all of the programs except for BackupAssist, and run the backup job again.
It is best practice to only have one backup solution installed at any one time.
You should also run a registry cleaner after the other backup solutions have been uninstalled: http://www.backupassist.com/blog/support/how-to-resolve-a-ba910-volume-shadow-copy-error-0x80004230/.
Known Cause 2 – Failing VSS writer
If the reason for the error is a failing VSS writer, it’s recommended to find which one is causing the issue.
To do this, open an elevated command prompt and run the following command: vssadmin list writers
This will provide an output of all VSS writers known to Windows on that machine. Look specifically for the Last error detail and anything that does not show No Error is most likely to be the cause of the error.
Known Cause 3 – Volume Shadow Copy errors within Event Viewer
VSS can write additional information to the event logs of your system which will provide information to help resolve the issue.
Open Event Viewer by clicking on Start > Run > Eventvwr to see if there are any specific VSS warnings or errors being generated from the system during the backup process. You will specifically want to look at the Application and System logs.
Known Cause 4 – The SQLAgent is not allowed to run
This is generated because the SQL writer has conflicts with the SharePoint VSS writer.
It is known that removing the GUID entry from the following registry key resolves this error:
Stopping the SQL VSS Writer Service can also resolve this error.
To do this, browse to Administrative Tools > Services and find SQL Server VSS Writer in the list. Once located, click on Stop to the left hand side of the Services screen.
Known Cause 5 – The Sqlvdi.dll file unregistered on the system
This error is generated if there is an issue with the file Sqlvdi.dll on the system.
Microsoft outline how to resolve this in their KB: https://support.microsoft.com/en-us/kb/830575.
BackupAssist v3 and later
Subscribe What is rss? Show details