Solution
Depending on a particular cause:
Please rename the database to a new name (without a space in it)
Grant the SQL VSS Writer service user a sysadmin role (Instructions in KB here:
https://www.veeam.com/kb1978)
Restart SQL VSS Writer service (Instructions in KB here herehttps://www.veeam.com/kb2041)
In the case of SBS machines that are also Domain Controllers, ensure that the SQL Writer is running as a domain administrator and not local system
Allow the SQL Writer service account access to the Volume Shadow Copy service via the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VSS\VssAccessControl
If the DWORD value “NT SERVICE\SQLWriter” is present in this key, it must be set to 1.
If the Volume Shadow Copy service is running, stop it after changing this registry value. Do not disable it.
To check if your database has a space in the name follow the instructions outlined here:
https://blogs.msdn.microsoft.com/bat...ommand-is-run/
