VSS SqlServerWriter Errors (4033424)

There may be instances in which the system reports a VSS SqlServerWriter error. These instances are listed below.

1. The VSS writer 'SqlServerWriter' failed during the 'DoSnapshotSet' phase with error WriterErrorNonRetryable.
2. When running VSSadmin list writers, the SqlServerWriter reports no information

Sample error:

One or more errors occurred. ---> Replay.Core.Contracts.Transfer.VssGeneralErrorException: There was a problem with the VSS subsystem on '(agent-machine)l'. ---> Replay.Agent.Contracts.ShadowCopy.ShadowCopyWriterFailedException: The VSS writer 'SqlServerWriter' failed during the 'DoSnapshotSet' phase with error WriterErrorNonRetryable. The VSS writer state is FailedAtPrepareSnapshot ---> Replay.Common.Contracts.ReplayException

In Application event logs on Agent Machine:

Event 8229

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.

Solution 1:

Ensure that the SQL Server instances have access to the Windows account, either explicitly or through group membership of BUILTIN\Administrators.

Once that granted, complete the following steps.

1. Restart the SQL Server Writer Service.
2. Run vssadmin list writers to ensure the SQL Server Writer is listed.
3. Refresh the agent metadata in the Core Console.
4. Force a snapshot of the agent.

Note: You may use any Windows account that must have an account created as a user with sysadmin level rights to the databases within the sql server. To be certain, login to the sql server using the Windows account to verify ability to access the sql server. 

Solution 2:

Restart the following services to reset the VSS writer status (in this specific order):

1. COM+ Event System.
2. COM+ System Application Service. This may not be started (if not, start it).
3. Distributed Transaction Coordinator Service.
4. Volume Shadow Copy Service.
5. SQL VSS Writer.

At an elevated command prompt, complete the following steps:

1. Run vssadmin list writers to check on the state of the SQL Server Writer.
2. Navigate to the path C:\Program Files\AppRecovery\Agent, and run vshadow .
   For example, vshadow d:

If the snapshot fails at:
Name: SqlServerWriter
State: VSS_WS_FAILED_AT_PREPARE_SNAPSHOT

Reboot the SQL Server.