04-01-2017, 05:56 PM
The Problem
The following error occurred after converting a Server 2012 (Non R2) to a VM. The error was recorded on the host but in fact relates to the VM that has been converted and is now running as a Virtual Machine.
"The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. (0x800423F4)"
The host machine will either fail to backup or complete with warnings. The failed files will show which VM it is unable to backup. It is possible to complete a successful backup by shutting down the VM causing the problem and rerunning the backup process on the host. This is not ideal but will give a solid backup to return to and confirms which VM is at fault.
The Fix
The error logs and messages do no elude to the nature of the problem in any way. By searching the Internet and trail and error a VSS Writer failure on the newly converted host was occurring due to issues with an installation of a MSSQL database. The fix is fairly simple and involves manually installing SP2 for MSSQL 2012. It is available as a Hot Fix from Microsoft and is labeled 47386_intl_64.zip. Search for SQL Server 2012 SP2 Cumulative Update Hotfix. Once applied, and it takes a long time > 15 minutes restart the server and retry the backup on the Host.
The following error occurred after converting a Server 2012 (Non R2) to a VM. The error was recorded on the host but in fact relates to the VM that has been converted and is now running as a Virtual Machine.
"The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. (0x800423F4)"
The host machine will either fail to backup or complete with warnings. The failed files will show which VM it is unable to backup. It is possible to complete a successful backup by shutting down the VM causing the problem and rerunning the backup process on the host. This is not ideal but will give a solid backup to return to and confirms which VM is at fault.
The Fix
The error logs and messages do no elude to the nature of the problem in any way. By searching the Internet and trail and error a VSS Writer failure on the newly converted host was occurring due to issues with an installation of a MSSQL database. The fix is fairly simple and involves manually installing SP2 for MSSQL 2012. It is available as a Hot Fix from Microsoft and is labeled 47386_intl_64.zip. Search for SQL Server 2012 SP2 Cumulative Update Hotfix. Once applied, and it takes a long time > 15 minutes restart the server and retry the backup on the Host.