Symptoms

Backup fails with the following message:

| error 0x10c469: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot. To troubleshoot VSS issues, download and run Acronis VSS Doctor available at https://www.acronis.com/en-us/personal/vss-diagnostic-free-tool/
| line: 0x3fec04e376b89db2
| file: d:\602\core\fdisk\win_snapshot.cpp:188
| function: `anonymous-namespace'::ObtainVSSFailReasonSuberror
| writerName: SqlServerWriter
| writerID: A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A
| $module: disk_bundle_vsa64_29439
|
| error 0xfff0
| line: 0xbd28fdbd64edb902
| file: d:\602\core\common\error.cpp:324
| function: Common::Error::AddHResult
| code: 0x800423f4
| $module: disk_bundle_vsa64_29439

 

Case #1

 

1. You have an SQL instance with a large number of databases.
2. You are backing up the instance (or the disk containing the instance).
3. Under Windows application event logs you see the following errors:

"Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: Write on ""{56EFEAC3-AC01-4E93-86B8-D24E27241B1D}33"" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)

 

"A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
   PrepareForSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: Microsoft SQL Server 2014:SQLWriter
   Writer Instance ID: {3a6cb2be-ba9b-4259-9a73-59d16eff7f93}
   Command Line: ""C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe""
   Process ID: 1980"

Solution #1

Increase the Max Worker Threads on your SQL Server. Select your version of SQL server and follow instructions of this MSDN article.

 

Case #2

1. You are using disk-level backup plan.
2. You have ACT7! SQL Server installed.
3. In Windows application event logs you see the following errors:

MS SQL Backup Fails with error: VSS error 0x800423f4
Description
MS SQL Backup Fails with error: VSS error 0x800423f4
Act7 Database
Errors in Event Logs:
SQLVDI - Loc=UserAccount::Init(name). Desc=LookupAccountName. ErrorCode=(1332)No mapping between account names and security IDs was done Instance=ACT7
SQLVDI - Loc=IdentifySQLServer. Desc=Initialize. ErrorCode=(1332)No mapping between account names and security IDs was done Instance=ACT7
SQLWRITER - Sqllib error: Failed to create VDS object. hr=0x80770005

Solution #2

Change SQL Server(ACT7) service user to Local Service:

1. Go to the Start menu.
2. Choose Computer Management.
3. Choose Services and Applications​.
4. Choose SQL Server Configuration Manager.
5. Locate SQL Server (ACT7).
6. Change the service logon from Local System to Local Service.
7. Restart the machine.

More information

Troubleshoot other VSS-related issues with the free Acronis VSS Doctor tool.