I'm using Veeam Endpoint Backup to backup the machine ACT! is installed on to a NAS.
This worked fine until about the end of 2015, at which point for unknown reasons this stopped working due to VSS errors.
(VSS is the volume shadow copy service that allows consistent backups of data while the machine is running)
Specifically in Event log ==> Windows Logs ==> Application I get errors from
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
This happened both on my existing installation of ACT! 17 with SQL Server 2008 as well as after removing this completely and installing ACT! 18 with SQL Server 2014.
I have then proceeded to test this using a fresh Windows 10 Professional in a VMware virtual machine that has never had ACT or Microsoft SQL installed before. I first installed Veeam Endpoint Backup Free (which comes with Microsoft SQL 2012 Express LocalDB) and successfully made a backup. Then I installed the ACT! 18 Trial from "actpro_1820x53_DE.de" (ACT! 18.2 German) and had a quick look inside the demo database, closed ACT! and restarted after the installation.
Then tried to make another backup with Veeam Endpoint Backup: It failed with "Creating VSS snapshot Error" just like on the existing machine. Event log on the virtual machine now has the same SQLWRITER and SQLVDI errors.
Why is ACT! destroying my ability to make backups? The installation seems to SERIOUSLY screw up the configuration of the Microsoft SQL Server that is bundled with it! How can I make the VSS (Volume Shadow Copy Service) work again? How do I fix this?