Looking at the binary log see the following entries from the binary log and at the same time we see an entry from Shadow Copy Service Volume “: Error querying the IVssWriterCallback interface. hr = 0x80070005, Access Denied” in the event log of the BMR client we are backing up.
Binary log extract:
ERROR: Failed to collect MBR Meta-Data for backup . disk : 0
ERROR: Failed to backup partition table for device: Disk 0 (195,56 Gbytes. HP. LOGICAL VOLUME. XXXX-XXX-XXXX-XXXX)
ERROR: Failed to backup Meta-Data for device: Disk 0 (195,56 GBytes. HP. LOGICAL VOLUME. XXXX-XXX-XXXX-XXXX)
Event log extract:
Eliminating VSS Error 8194 from Event Log
Error Shadow Copy Service Volume: Error querying the IVssWriterCallback interface. hr = 0x80070005, Access Denied.
. This error is often caused by incorrect security settings in the process editor or applicant.
Operation:
Editor of the data being collected
Background:
Editor's Class ID: {e8132975-6f93-4464-A53E-1050253ae220}
Editor name: System Writer
Editor's instance ID: {9bacf81b-7a67-4c19-af96-be18a6be5e69}
Error code 8194 is an "Accessed Denied" error caused by the inability of one or more VSS system writers to communicate with the Remote Backup VSS requestor process via the "COM" calls exposed in the IVssWriterCallback interface (Microsoft programming interface to the Volume Shadow Service).
This is not a functional error in the Remote Backup program, but rather a security issue caused by select VSS writer(s) running as a service under the "Network Service" (or "Local Service") account(s) and not the Local System or Administrator account. By default, in order for a Windows service to perform a COM activation it must be running as Local System or as a member of the Administrators group.
In general, Remote Backup is not used to backup the files managed by these VSS system writers - so the errors have no impact on the success of the backup. However, Managed Service providers are typically concerned by these recurring error messages and often question whether the backups are actually running properly - since the event is listed as a serious error.
There are two ways to clear the problem.
The first is to locate the VSS writers (Start | Run | services.msc) that are erring out and change the account they are running under from Network Service to Local System. Then, restart the service process (or reboot the computer) and the VSS Writer will run with max privileges - thereby eliminating the IVssWriter callback errors.
The possible security issue with this method is that the service will be running with a higher level of access than Microsoft intended. Should the VSS Writer process be "hacked", this could be a security weakness. But, if you're not overly concerned about that, repeat this process for each VSS Writer that generates an 8194 error and you should not experience any more error events in normal operation.
The second (preferred) way to work around the issue is to make an adjustment to the default COM service activation permissions - allowing Network Service (and possibly Local Service) user account(s) to activate the IVssWriter callback interface. This method has the benefit of permanently fixing the issue in one place and allowing the VSS Writer service(s) to run at the privilege level that Microsoft intended. Any COM object accessed (by a process running as Network Service) still has the ability to enforce security restrictions it so chooses.
Make this fix by doing the follow: Start | Run | dcomcnfg. This brings up the Component Services application.
On the left pane navigate to Component Services | Computer | MyComputer.
Right click on MyComputer and select properties.
Select the COM Security tab and select the Edit Default button under Access Permissions.
Use the Add... button to add the "Network Service" account to the permission list.
Verify that ONLY the Local Access box is checked and click OK.
Close Component Services.
A reboot is then required to make the requested changes to COM Security.
See KB: http://help.remote-backup.com/index.php?/Knowledgebase/Article/View/327/5/eliminating-vss-error-8194-from-event-log
