We do not recommend using another backup software side-by-side with Veeam. Please remove this StorageCraft software (if any), or use this link to remove Provider manually - http://hyper-v-backup.backupchain.com/h ... -provider/ (please check that you're removing the correct Id).
Additionally, please run the following command:
vssadmin delete shadows /all
Also there are a lot of errors in Application log with access denied errors.
Then restart VSS service once again and try to run a backup.
SYSTEM has Full Control access so nothing to do. I have uninstalled Shadow Protect (old version, not used anyway) and rebooted. VEEAM Endpoint Backup is now running correctly.
I restarted the SQL Server and it still failed, then rebooted the machine and the whole machine became unresponsive, most likely losing USB keyboard and mouse. By the looks of it a file was installed to C:\ as "Program" and it caused all third party programs in "Program Files" to fail to start (including the Microsoft Keyboard and Mouse software!). I crashed the computer on restart three times and managed to get it to roll back to before the latest "Critical Update" (two days ago) and it went back to normal. I have renamed the random offending file to "Program1" and it seems to be fine now.
I have just uploaded it to Virus Total (https://www.virustotal.com/) to scan the file with all the major antivirus products. Only one said it was a threat (DrWeb called it "DLOADER.Trojan") but all the rest say it is ok. Virus Total gave it a 100 out of 100 for safety.
It says it is related to WRDATA, which is the folder that Webroot Antivirus uses to store its database and update files. By the looks of it Webroot has tried to update and failed, leaving a badly formed install
I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:\windows\system32\. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
mcrape wrote:I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:\windows\system32\. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
Thank you, any help is always appreciated It appears to be related to a program we use called ACT! Premium, that installs SQL Server. It seems to install it badly, and when ACT! Premium is uninstalled it leaves the SQL Server in place so removing ACT! Premium doesn't even fix the issue
I'm fighting with the same problem, which is also occuring on workstations which have Act installed and are to be backuped by Veeam Endpoint Backup.
What did you do to make the VSS errors go away? Or do you have any further information about what the Act installer does "badly" when installing the SQL server (express)?
I have about 15 machines with failing backups due to this error now :-/
I uninstalled ACT; I wish I were kidding but it was a constant headache. I didn't have the time or the inclination to figure it out, the trial period had expired and it couldn't do everything we wanted it to do in the trial period time, and ACT were unwilling to give us an extension to the trial time. I then turned off the Sql Server VSS Writer under Services. VEEAM seems to need it running (without ACT) or turned off (maybe it turns it back on using its own conditions?), no idea why this works. A simple reboot didn't seem to fix the error.
I also found that ACT blocked certain mapped drive folders from opening, giving me an eternal "Working on it...". Uninstalling ACT fixed that problem too.
Any update on this?
We are experiencing the same issue, however on our exchange server. ATM they are stating its a Microsoft error with the Hyper-V Vss writer.
I know this is a old post but I recently ran in to the same issue with ACT, I was able to find this simple fix at the ACT forum Thanks to Andyman49 https://community.act.com/t5/Act/Instal ... 748/page/2
The problem is with permission set for ACT SQL instance needs to be change to Local Service from Local System
Control Panel
Administrative Tools
Computer Management
Services and Applications
SQL Server Configuration Manager
SQL Server Services
SQL Server(ACT7)
Change Log On from Built-in account: Local System to Built-in account: Local Service
Thank you for posting this here! I was having this problem since we setup a new ACT server on our VMWare host. The old ACT server backed up fine, but the new one would error out with this error. Changing the service did the trick for us!
Hi Leif,
The solution from BellSys2756 seems to work fine. If not, you can always contact our support department. (In that case, post the case ID and follow-up here) as they have fixed these already a few times (see post of Dima)
The same thing just happened to me. I've been backing up my laptop with Veeam for years and today is the first time I've seen this error. As far as I know, nothing has changed on the laptop. A reboot didn't fix it, but stopping the SQL VSS writer service allows Veeam backup to run.
Hey group, I ran across this post and thought I would throw my 2 cents in.
I am running a development citrix server with its own database server installed. The problem began when a recent citrix upgrade had upgraded the SQL Express server from 2012 to 2014. After that, I was getting daily Veeam warnings as indicated by the original poster.
I tried the recommendation in this post of changing Network Service to Local Service but that didn't work, nothing changed. But when I changed the SQL Service logon to the top circle "Local System", that seemed to fix it. No more warnings from Veeam.
The machine was off over the weekend.
