locked
windows home server unable to create volume snapshot in auto mode. a vss problem ? RRS feed

  • Question

  • hi guys,

    the pc in question is a ghosted image with a different key and the hard ware is about 1-1.5 months older. same cpu, same hard drives and all from the same vender. i do have 4 pc's, 1 WHS, and 2 laptops on my network, all work but this one. 3 pc's ( including this one.) windows XP 32bit sp3. laptops running vista 32 ulmit. and 1 with xpsp2 64bit

    one has the problem and the other does not.

    the one that come up with the back up error. i can do a back up from the pc, and from the network ( ie. from a pc in the other room and from the server itself) a manual backup with out a problem.  but when the timer on the server comes on and says to the network time for a backup. get in line and get ready to start. it does not and says the " can not do a snapshot ".

     ok done chkdsk, done the reg hack, defrag, and even went and turned off the save power on the nic card, which WHS wants to turn on by default.
    a error showed up this morning in the event log on the pc. it was "can not do a shadow copy because of the free space."
     like i said 2 pc's and one work and this one does not.

    the drive in question is a 1tb drive. it has 685 gb free space.
    went and looked at the application events and about 30 min after the back up was ended by the server this showed up.

    Event Type:    Error
    Event Source:    HomeServer
    Event Category:    HomeBackup
    Event ID:    770
    Date:        6/6/2009
    Time:        4:21:52 AM
    User:        N/A
    Computer:    my-home-pc
    Description:
    Backup set 13 on my-home-pc failed: Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: Exception from HRESULT: 0x80042308 ---> System.Runtime.InteropServices.COMException (0x80042308): Exception from HRESULT: 0x80042308
       at Microsoft.HomeServer.Backup.VSS.IVssBackupComponents.GetSnapshotProperties(Guid SnapshotId)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       --- End of inner exception stack trace ---
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()
    got any ideas. i am out of them.
    thank you

     and yes i have done all the steps that i could find in the forums.

    vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.

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


    vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.

    Writer name: 'Microsoft Writer (Bootable State)'
    Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
    Writer Instance Id: {b4f6189b-536c-4f38-9a7b-cde489bb87d0}
    State: [1] Stable

    Writer name: 'Microsoft Writer (Service State)'
    Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
    Writer Instance Id: {6a860c74-3420-45b5-8ff0-39beef8553cf}
    State: [1] Stable

    Writer name: 'SqlServerWriter'
    Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
    Writer Instance Id: {e7ae7f55-06e9-44bb-b973-b20efc595e72}
    State: [1] Stable

    Writer name: 'MSDEWriter'
    Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
    Writer Instance Id: {86d88ddf-c175-45ba-bf4a-1271918c158d}
    State: [1] Stable

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {1438d40f-a470-40d9-a898-eec1006c6871}
    State: [1] Stable

    Sunday, June 7, 2009 6:25 PM

All replies

  • I don't know if you got this resolved but when one of my computers won't take a snapshot what works most of the time for me is to configure the computer again and it will complete the backup. Weird but it works.
    Monday, November 9, 2009 10:02 PM