Veeam Agent Creating VSS snapshot Error

Hi,

Since the failing writer is SqlServerWriter, I would focus the troubleshooting on the SQL Writer and any SQL-related component installed by Cabinet Vision.

I had a similar case recently where the SQL Writer was failing during the VSS freeze because Windows still had old SQL Server references pointing to database files that no longer existed. In that case, restarting the VSS services helped only temporarily, but the job failed again as soon as Veeam triggered the snapshot.

I would suggest checking: vssadmin list writers

Then look at the Windows Application Event Log for SQLWRITER events around the backup time or try to use proc mon to help. The key point is to see if SQL Writer is trying to access a database path, MDF/LDF file, or old application reference that no longer exists.

This blog may help because it describes a very similar behavior:

• https://community.veeam.com/blogs-and-podcasts-57/veeam-agent-for-windows-vss-error-caused-by-old-sql-server-references-13554

Also, if it has not been done yet, I would try a full reboot of the Windows 11 computer where the Veeam Agent is installed, then check the SQL Writer state again before starting the backup.

If the writer is healthy after reboot but fails again during the backup, that would reinforce the idea that something related to SQL/Cabinet Vision is being triggered during the VSS freeze.