VSS errors when imaging Windows Servers

User discussion and information resource forum for Image products.
Post Reply
timr
Posts: 1
Joined: Wed Jan 04, 2012 5:07 pm

VSS errors when imaging Windows Servers

Post by timr »

I am seeing event ID #8194 in several servers when I try to make an image using VSS. The image appears to complete successfully, however the error is logged in the Application Log

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Are there any known workarounds for this issue?
acarra
Posts: 1
Joined: Thu Jan 12, 2012 3:21 am

Re: VSS errors when imaging Windows Servers

Post by acarra »

I am getting exactly the same issue. Server is a fresh install of Windows 2008 R2 x64.
Any ideas?
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: VSS errors when imaging Windows Servers

Post by TeraByte Support »

Doesn't affect the use of IFW ... it has to do with VSS writers and
permissions....

From the Start Menu, select Run
The Run dialog opens.

In the Open field, input dcomcnfg and click OK.
The Component Services dialog opens.

Expand Component Services, Computers, and My Computer.
Right-click My Computer and click Properties on the pop-up menu.

The My Computer Properties dialog opens.

Click the COM Security tab.
Under Access Permission click Edit Default.

The Access Permissions dialog opens.

From the Access Permissions dialog, add the "Network Service" account with
Local Access allowed.
Close all open dialogs.
Restart the computer.




"timr" wrote in message news:1010@public.image...

I am seeing event ID #8194 in several servers when I try to make an image
using VSS. The image appears to complete successfully, however the error is
logged in the Application Log

Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005. This is often caused by
incorrect security settings in either the writer or requestor process.

Are there any known workarounds for this issue?

Post Reply