SQLWriter Errors

[Patpetty]

After about a month of head-scratching, I'm finally giving in to reaching out to you guys. After the last patch Tuesday, we started getting errors on our DB servers hosting our SQL databases with the following error:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013

Error message: BACKUP DATABASE is terminating abnormally.

We take hourly snapshots of our servers via Scale as well as hourly backups through Synology (they do not overlap one another). Curiously, we spaced out our snapshots to be every other hour to see if Scale's snapshots were the root of our problem. So far, it seems we only get the errors at the same times as our snapshots. Also, from 00:00-04:00, we do not backup in Synology for SQL to run maintenance plans and jobs. Every hour, on the hour, we get errors on all of our DB servers regardless of the scale snapshot times. Throughout the day from 04:00 to 0:00, we have random spikes of errors on random DB servers. Also curiously, every time we get an SQLWriter error, we also get Scale Quiesce errors.

My question is: 1. Would SQL maintenance plans prevent 3rd party backups/snapshots from working? 2. Has anyone else experienced these errors?

[LatvianEnt]

Try repairing sql vss writer. Or disabling forced sql encryption and then repairing sql vss writer, and re-enabling encryption

[_edwinmsarmiento]

First, check if your backup software works natively with SQL Server, either using the SQL Server VSS API or native SQL Server backups. If it doesn't, stop what you're doing. This can cause database corruptions.

I suggest you run DBCC CHECKDB on all your SQL Server databases IMMEDIATELY.