Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Cannot backup a PC due to VSS problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I just did a fresh install of WHS 2011 to replace the original WHS and when I re-installed the connectors on my PC’s (all of which have been happily backing up to WHS v1 for years), one of them would not back up and WHS claimed that there wasn’t enough disk space. Since that was an obvious lie (the server has hundreds of GB free), I tried digging into it and discovered that VSS had some kind of trouble with one volume. This volume matched a drive Q: (which I never heard of) and searching the registry for references to Q: it looked like it was used for some crazy “App-V” / “SoftGrid” thing which somehow snuck onto my PC and had something to do with Office. The Q: drive could not be looked at in the normal way, of course, but doing “net use * \\localhost\Q$” I was able to see that it had one root directory (which I could not see the contents of, though). Since this Q: stuff seemed related to Office 2010, I un-installed Office (I’m using 64-bit Office 2010, BTW, installed from DVD and the PC is running 64-bit Win7 Pro SP1). After that the Q: drive disappeared, but the same WHS problem remained – the computer would not back up, and the event viewer showed that VSS was the reason. Both the client PC and the new WHS box have all the patches and updates available, of course, and two of my other PC's backup just fine (one always thinks WHS is offline - I posted that as a separate question; so far, WHS 2011 works correctly on two out of four computers I've tried to connect).

     

    The event viewer shows the following for a failed WHS backup:

     

    Log Name: Application

    Source: VSS

    Date: 9/30/2011 4:40:40 PM

    Event ID: 8194

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: PVLR

    Description:

    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.

    . This is often caused by incorrect security settings in either the writer or requestor process.

     

    Operation:

    Gathering Writer Data

     

    Context:

    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

    Writer Name: System Writer

    Writer Instance ID: {8a250dd1-c5e4-49a5-8f4a-42772ec710c1}

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="VSS" />

    <EventID Qualifiers="0">8194</EventID>

    < Level>2</Level>

    < Task>0</Task>

    < Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2011-09-30T23:40:40.000000000Z" />

    < EventRecordID>29640</EventRecordID>

    < Channel>Application</Channel>

    < Computer>PVLR</Computer>

    <Security />

    </System>

    <EventData>

    < Data>0x80070005, Access is denied.

    </Data>

    <Data>

     

    Operation:

    Gathering Writer Data

     

    Context:

    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

    Writer Name: System Writer

    Writer Instance ID: {8a250dd1-c5e4-49a5-8f4a-42772ec710c1}</Data>

    < Binary>...(snip)...</Binary>

    </EventData>

    </Event>

     

    Some of the web sites that describe a similar VSS problem suggest running vssadmin, but no matter how I run the tool the result is always the same (useless) error:

     

    C:\>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2005 Microsoft Corp.

     

    Error: A Volume Shadow Copy Service component encountered an unexpected error.

    Check the Application event log for more information.

     

    C:\>vssadmin list shadowstorage

    vssadmin 1.1 -Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2005 Microsoft Corp.

     

    Error: A Volume Shadow Copy Service component encountered an unexpected error.

    Check the Application event log for more information.

     

    The following shows up in the event viewer for the failing “vssadmin” commands:

     

    Error,9/30/2011 3:47:12 PM,VSS,8193,None,"Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154, Class not registered. "

     

    Error,9/30/2011 3:47:12 PM,VSS,22,None,"Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened [sic] if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {0b5a2c52-3eb9-470a-96e2-6c6d4570e40f} and Name Coordinator is [0x80040154, Class not registered]. "

     

    Error,9/30/2011 3:47:12 PM,VSS,8193,None,"Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154, Class not registered.

    Operation: Instantiating VSS server"

     

    Error,9/30/2011 3:47:12 PM,VSS,22,None,"Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened [sic] if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered].

    Operation: Instantiating VSS server"

     

    I’ve re-installed Office 2010 / x64 again and I still don’t see any Q: drives, but the WHS problem remains (it’s possible that - before I installed Office from the DVD - I might have downloaded some kind of an online trial which is where the bizarre Q: thing came from; I just don’t remember anymore, it’s been too long). In any case, I have now spent an entire day trying to get WHS to back up my computer (which worked perfectly fine with the old WHS) and I’m at my wits’ end. I also tried deleting the computer from WHS, un-installing the connector from it (and deleting any “Home Server” keys in the registry it left behind), renaming the PC and starting over (so that the PC hopefully looked completely new to WHS, in case there was some turd left behind that was keeping the problem alive), and none of this made any difference.

     

    Any help would be greatly appreciated!

    Saturday, October 1, 2011 3:56 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    No GPT partitions, nothing useful in event viewer, etc. I should have posted that I'd found a "solution" - my apologies (I only posted this on the MS bug report I filed). I un-installed Office 2010, re-installed Office 2007 trial (which created the weird Q: drive that seemed to be the cause of this issue), immediately un-installed the trial, and now the PC backs up just fine. I suspect that the virtual app thing that the Office 2007 trial used left some turd behind which didn't get cleaned up (though that's just a guess - I know nothing about the softgrid / virtual app stuff). So I'm back in business now; thanks for all the replies and suggestions.

     

    Peterk

    • Marked as answer by Ken Warren Wednesday, November 2, 2011 11:14 AM
    Wednesday, November 2, 2011 1:50 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Something has corrupted Volume Shadowcopy Services on that client computer. Windows Home Server uses VSS during the client backup process, so when VSS doesn't work backup doesn't either, as you've seen.

    Below is a batch file which attempts to reset your VSS installation. It's not guaranteed to work, particularly if you've installed other software on your computer that uses VSS for anything, or that supports VSS for data integrity reasons.

     

    @echo off
REM
REM Batch file that attempts to reset the
REM Volume Shadow Copy (VSS) installation.
REM
echo This batch file must be run as an Administrator. If you are using Windows
echo Vista then run it by right-clicking on the batch file and selecting
echo "Run as administrator"

%SYSTEMDRIVE%
cd %SystemRoot%\System32
echo.
echo Ignore any messages saying a service is not started.
echo.
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll

echo eventcls.dll will fail to register on Windows Vista.
regsvr32 /i eventcls.dll

echo es.dll will fail to register on Windows Vista.
regsvr32 es.dll

regsvr32 stdprov.dll
echo.
echo vssui.dll only exists on Windows 2003. Ignore the error if not using Windows 2003.
regsvr32 vssui.dll

regsvr32 msxml.dll
regsvr32 msxml3.dll
echo.

echo msxml4.dll may not be installed and is optional. Ignore the error.
regsvr32 msxml4.dll
echo.
echo DONE!
echo.
echo IMPORTANT: Reboot your computer. After the reboot, open a command prompt
echo and run the following:
echo.
echo vssadmin list writers
echo.
echo Ensure that all your writers are displayed without errors.
echo.
echo vssadmin list providers
echo.
echo Ensure that all your providers are displayed without errors.
pause


     

    I'm not on the WHS team, I just post a lot. :)
    • Edited by Ken Warren Saturday, October 1, 2011 12:37 PM
    Saturday, October 1, 2011 12:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for trying to help out with this - I really appreciate it. I ran the batch file and the following errors popped up:

        -- the module swprv.dll was loaded but DLLregisterServer failed with 0x80070715
        -- the module eventcls.dll was loaded but DLLregisterServer failed with 0x80070715
        -- the module es.dll was loaded but the entry point DLLregisterServer was not found
        -- the module msxml.dll failed to load

    After rebooting, vssadmin started working again and the results are as follows:

        C:\>vssadmin list writers
        vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
        (C) Copyright 2001-2005 Microsoft Corp.

        Writer name: 'Task Scheduler Writer'
           Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
           Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
           State: [1] Stable
           Last error: No error

        Writer name: 'VSS Metadata Store Writer'
           Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
           Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
           State: [1] Stable
           Last error: No error

        Writer name: 'Performance Counters Writer'
           Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
           Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
           State: [1] Stable
           Last error: No error

        Writer name: 'System Writer'
           Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
           Writer Instance Id: {e39f74da-faa7-4c6a-b24c-1ec6190b0997}
           State: [1] Stable
           Last error: No error

        Writer name: 'ASR Writer'
           Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
           Writer Instance Id: {b930de5c-f21d-4686-8a80-fd5333199e21}
           State: [7] Failed
           Last error: Timed out

        Writer name: 'Shadow Copy Optimization Writer'
           Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
           Writer Instance Id: {35173c9b-b30c-4c8a-a051-50d51637e969}
           State: [7] Failed
           Last error: Timed out

        Writer name: 'Registry Writer'
           Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
           Writer Instance Id: {f4e283e5-bc22-4658-b87a-318ca2433cec}
           State: [7] Failed
           Last error: Timed out

        Writer name: 'WMI Writer'
           Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
           Writer Instance Id: {f92bdd98-9884-4bd8-9009-2a08de1774b2}
           State: [7] Failed
           Last error: Timed out

        Writer name: 'COM+ REGDB Writer'
           Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
           Writer Instance Id: {cef360da-ed46-44b5-afbb-a1bb0d1ab0e3}
           State: [7] Failed
           Last error: Timed out

        Writer name: 'BITS Writer'
           Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
           Writer Instance Id: {c9a576c8-7869-4f4e-9484-9e785cdb6a5d}
           State: [7] Failed
           Last error: Timed out


        C:\>vssadmin list providers
        vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
        (C) Copyright 2001-2005 Microsoft Corp.

        Provider name: 'Microsoft Software Shadow Copy provider 1.0'
           Provider type: System
           Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
           Version: 1.0.0.7


        C:\>vssadmin list shadowstorage
        vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
        (C) Copyright 2001-2005 Microsoft Corp.

        Shadow Copy Storage association
           For volume: (C:)\\?\Volume{2de57d47-e6cd-11de-8656-806e6f6e6963}\
           Shadow Copy Storage volume: (C:)\\?\Volume{2de57d47-e6cd-11de-8656-806e6f6e6963}\
           Used Shadow Copy Storage space: 0 B (0%)
           Allocated Shadow Copy Storage space: 0 B (0%)
           Maximum Shadow Copy Storage space: 1.414 GB (3%)

    Unfortunately, the backup still fails in the same way - there is one event recorded:

        Log Name:      Application
        Source:        VSS
        Date:          10/1/2011 7:26:22 AM
        Event ID:      8194
        Task Category: None
        Level:         Error
        Keywords:      Classic
        User:          N/A
        Computer:      PVLR
        Description:
        Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
        . This is often caused by incorrect security settings in either the writer or requestor process.

        Operation:
           Gathering Writer Data

        Context:
           Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
           Writer Name: System Writer
           Writer Instance ID: {e39f74da-faa7-4c6a-b24c-1ec6190b0997}
        Event Xml:
        <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
          <System>
            <Provider Name="VSS" />
            <EventID Qualifiers="0">8194</EventID>
            <Level>2</Level>
            <Task>0</Task>
            <Keywords>0x80000000000000</Keywords>
            <TimeCreated SystemTime="2011-10-01T14:26:22.000000000Z" />
            <EventRecordID>30283</EventRecordID>
            <Channel>Application</Channel>
            <Computer>PVLR</Computer>
            <Security />
          </System>
          <EventData>
            <Data>0x80070005, Access is denied.
        </Data>
            <Data>

        Operation:
           Gathering Writer Data

        Context:
           Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
           Writer Name: System Writer
           Writer Instance ID: {e39f74da-faa7-4c6a-b24c-1ec6190b0997}</Data>
            <Binary>...lotofhex...</Binary>
          </EventData>
        </Event>

    Any other ideas?

     

    Thanks

    PeterK

    Saturday, October 1, 2011 2:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am getting the same error as of Oct 30 2011 my cleint PC and whs 2011 are both up to date in updates and im getting on the client side the same VSS error

    At first i thought it must have been anit-virus or something like that that might be blocking the SRV ,anyways long story short i decided to re-install windows 7 64 on the clients PC since there was nothing on the C drive and right from the get go I installed the connector and VSS error same as you ,from there i know its somthing on the WHS 2011 thats casuing this ,i did a CHDSK on the client and on the server found nothing .IM not at home now but in the log's of your WHS look in the EVENT VIEWER ,WINDOWS LOGS ,SECURITY  (are there any ADIT FAILURES when you try to do a back up? and look at the same place in th cleint side)

    Tuesday, November 1, 2011 12:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi - I just upgraded to WHS2011 (long-time v1 user) and was dismayed that my Windows 7 64-bit PC was getting this same error!  The status hangs at 1% for a long time then I get the same error: Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.  It's important to note that Windows XP SP3 and Windows 7 23-bit backed up without issue!  I tried Ken's script and still no-go, though I should point out the the "vssadmin list writers" and "vssadmin list providers" returned no errors at all.  I have scoured the posts out there to no avail - also confirmed that WHS backup is NOT trying to back up the 100MB system volume that Win7 creates.

    Tuesday, November 1, 2011 5:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think there might have been some sort of  update for the WHS  that might be the casue not sure casue i got new updates on the 28th and the 29th i rebooted and from there on the whs never did any back-ups .

    W7 - 64bit

     

    vssadmin = no errors .

    • Proposed as answer by jimatjude2 Thursday, May 17, 2012 2:43 PM
    Tuesday, November 1, 2011 6:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you format your system drive with a GPT partition?  Device Manager, Disk Drive/Properties,Volumes.  See this post:

    http://social.microsoft.com/Forums/en-US/whs2011/thread/ddc80b0f-e2de-422c-80ea-6723b48f822b

     

    Wednesday, November 2, 2011 1:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No GPT partitions, nothing useful in event viewer, etc. I should have posted that I'd found a "solution" - my apologies (I only posted this on the MS bug report I filed). I un-installed Office 2010, re-installed Office 2007 trial (which created the weird Q: drive that seemed to be the cause of this issue), immediately un-installed the trial, and now the PC backs up just fine. I suspect that the virtual app thing that the Office 2007 trial used left some turd behind which didn't get cleaned up (though that's just a guess - I know nothing about the softgrid / virtual app stuff). So I'm back in business now; thanks for all the replies and suggestions.

     

    Peterk

    • Marked as answer by Ken Warren Wednesday, November 2, 2011 11:14 AM
    Wednesday, November 2, 2011 1:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Bardmaster :

    the pc and server have been running fine since april 22 2011 ,so non i didnt format anything

     

    Hoseduser :

    No office ,on the client its a freash install of windows sp1 and all updated and the whs is all updated

    to night im going to try a roll back on the server to when i know when it was working and see what happens,if that dosnt work then im reinstalling everthing and going to see if that works ,

    Wednesday, November 2, 2011 1:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same problem... WHS 2011 was backing up my systems until 10/25/11.  Since then, backups for my Win 7 32bit and Win 7 64bit systems failed everyday.  Log files show VSS errors. Tried chkdsk/f/r, re-register VSS, removed computer, then reconnect to WHS 2011, and changed backup job to backup one file, yet I still get "Unsuccessful" backup status. 

    I'm not sure how to roll back WHS 2011 since there is no way to connect a monitor (port does not exist) and I cannot press F8 to view startup options like "last known good config".

    Main purpose of my WHS 2011 is to backup my other systems... now, its dead in the water.  I'm stuck.

    Thursday, November 3, 2011 6:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am experiencing the same issue with one of four computers that I'm using WHS 2011 to backup:

     

    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.

    . This is often caused by incorrect security settings in either the writer or requestor process.

    Operation:

    Gathering Writer Data

    Context:

    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

    Writer Name: System Writer

    Writer Instance ID: {82fa37ca-26a2-4d21-a04a-2efd4bca407d}

     

    I am not using UEFI nor am I using GPT. I have two drives - an SSD for the system and a 500GB drive for data. Both show as MBR. All the other, working, computers have a single non-SSD drive.

    Has anyone came across a solution to this? Does anyone have any other ideas?

    TIA

    -Mike

    Sunday, November 27, 2011 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have same problem. Cannot get a successful backup on win7 64bit. Tried all above bat options, put in new drive and imaged, still nothing. Is this just bad code or what?

     

    - chris

    Chris R
    Saturday, December 3, 2011 7:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had much the same problem.  Looking around the 'Net, lots of people seem to be having the problem as well.  Mine was a two step fix.  First, I followed the instructions in the following link to correct what was causing the 8194 error on my computer:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/vss-error-showing-in-event-viewer/34b62c1b-93e6-4848-a9a0-59e3f4019ebb

    This got rid of the 8194 error, but the client backup's still wouldn't work.  The only indications were in the Home Server console referencing that a snapshot couldn't be taken, and then in both the Home Server's and the Window's 7's "Windows Server" event log there were events having to do with the backup failing/problem with the client VSS writer.

    After doing the steps in the link above, I made sure that I didn't have any disk errors by running the chkdsk /f on the drive.  After that, I tried using the local Windows Backup and Restore and tried to take an image backup of my local computer (I had a second drive I could point it to).  This failed, citing a problem with VSS on my computer.  Searching on the events generated by this action I came across the following article from Microsoft:

    http://support.microsoft.com/kb/968128

    After performing the steps in this article I could now do a local snapshop backup to a second hard drive.  I tried running the Home Server from the console and now it's working.  I'm still going through that initial backup (41% and counting), but I have every reason to believe it will complete normally.  Hope this helps you out.

    Rich

    Wednesday, December 14, 2011 12:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Glad you found success but not for me! 

    In the first place, when you attempt to add a key as suggested in the first link above,

    HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>VSS>VssAccessControl <--- ADD KEY

    MyDomain\MyUser = 1 <- ADD VALUE

    Doing so errors as Windows will not let you add a key with a backslash.

    I also tried the second method, adding a Network Service account to COM security.  Added the account fine but still the 8194 error.

    So, still unable to backup this one of 4 computers on my WHS 2011....

    I would suggest this thread is not closed.


    • Edited by Mentj Thursday, December 15, 2011 3:36 AM
    Thursday, December 15, 2011 3:35 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Sorry to say but I gave up on this. Too complex and no guarantee that it wouldn't recycle back to haunt me later. Just uninstalled WHS 2011 and reinstalled the original WHS code and system works perfectly and has been running flawlessly for 2 months now. Not sure who came up with the design on WHS 2011 but from my view it was a waste of my money and time.

    Chris

    Chris R

    Saturday, May 19, 2012 10:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is there an answer to this problem? (Win7 64 VSS hanging so no backup)

    Friday, January 2, 2015 11:56 PM