Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > Disk2vhd
  New Posts New Posts RSS Feed - error snapshotting volumes
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

error snapshotting volumes

 Post Reply Post Reply
Author
Message
s_cutter View Drop Down
Newbie
Newbie
Avatar

Joined: 22 March 2013
Location: GA, USA
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote s_cutter Quote  Post ReplyReply Direct Link To This Post Topic: error snapshotting volumes
    Posted: 22 March 2013 at 9:34pm
I am getting an "error snapshotting volumes" response when  attempting to create a VHD containing multiple partitions and my diagnosis has led me to believe this may be a bug with DISK2VHD.

Background:
* DISK2VHD V1.63 being used with Windows 7 Home Premium 64bit on a laptop with a 250Gb SSD and a 15Gb SSD (yeah i know its tiny but its not being used).
* The 250Gb disk has 3 partitions; A SYSTEM partition, an OS partitions (C:) and a RECOVERY PTN.
* Using DISK2VHD to create an image of the 250Gb disk.

Problem:
Attempting to create a single VHD containing all 3 partitions (from the 250Gb disk) fails with the above error and create the following entry in the application event log:
=====================================================
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: {2c87049c-4bd3-446b-b978-8c2c10ecac48}
=====================================================

Results:
There is no error and a VHD is successfully generated under all of the following conditions:
1. Creating a single VHD containing any one of the three partitions. 
2. Creating a single VHD containing the OS partition and the SYSTEM partition.
3. Creating a single VHD containing the OS partition and the RECOVERY partition.

The error is generated only when trying to create a single VHD containing both the SYSTEM & RECOVERY partitions regardless of whether the OS partition is included or not.
 

Does anyone have any similar experiences and if so have you been able to resolve them?
Back to Top
upgraders View Drop Down
Newbie
Newbie


Joined: 22 March 2013
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote upgraders Quote  Post ReplyReply Direct Link To This Post Posted: 22 March 2013 at 11:15pm
Just wanted to jump on you post as I was about to post the same.   I Just bought a new laptop today and wanted to virtualize my old one and I get the exact same error.  It also is using a 250GB SSD but running Windows 8.  I removed all my backup software as suggested in other forums and VSS service is running.  I also run the software as an administrator.
Back to Top
tksprague View Drop Down
Newbie
Newbie


Joined: 17 April 2013
Location: CA
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote tksprague Quote  Post ReplyReply Direct Link To This Post Posted: 17 April 2013 at 5:41pm
Reading your post (after trying dozens of other solutions I found online regarding problems with VSS), I went to try the same thing under Windows XP.  My laptop has two partitions on its HD, one without a label, one labelled "HP_RECOVERY".  When I had both checked, I got the same problem as above.  When I check only the C: drive, it works.
 
Then I wondered if it needed to have an assigned drive letter... so I assigned one (D:) to HP_RECOVERY, and now it works to snapshot both drives!
 
I'm going to go try the same solution on my Windows 7 machine, and will post back about that as well.
Back to Top
tksprague View Drop Down
Newbie
Newbie


Joined: 17 April 2013
Location: CA
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote tksprague Quote  Post ReplyReply Direct Link To This Post Posted: 17 April 2013 at 5:57pm
Update: tried this on my Windows 7 laptop, and get similar results: I can make a snapshot of C: alone, but if I try to snapshot any other partitions on that physical SSD drive (named SYSTEM, HP_RECOVERY, HP_TOOLS) then I get the dreaded "error snapshotting volumes". 
I tried assigning them all drive letters, and I tried icacls with all of them, and I tried taking ownership of them.  I tried doing each individually.  No dice.
 
'vssadmin list providers' showed some interesting information (unlisted ones said "no error"):
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {1286ff2f-e9af-4fb6-9020-a6263df4c2f1}
   State: [8] Failed
   Last error: Inconsistent shadow copy
Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {b231270e-fbe8-493a-8cc3-8c7354bde879}
   State: [10] Failed
   Last error: Timed out
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {738a9d77-6cf7-4f2f-ba58-d6c8b19141f2}
   State: [10] Failed
   Last error: Timed out
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {18348fbf-bb35-49a3-b61a-7c3673f14bed}
   State: [8] Failed
   Last error: Inconsistent shadow copy
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {7df7a35e-637b-4758-a206-f62814d5aa24}
   State: [8] Failed
   Last error: Inconsistent shadow copy
 
Now researching those errors...


Edited by tksprague - 17 April 2013 at 5:59pm
Back to Top
upgraders View Drop Down
Newbie
Newbie


Joined: 22 March 2013
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote upgraders Quote  Post ReplyReply Direct Link To This Post Posted: 23 April 2013 at 10:23pm
I was excited when you posted a solution, but it was only today that I was able to try and Still a no-go for me. Even if I selected just C Local it still errored.  Thanks for the post, perhaps it will help others..  
Back to Top
vjaffe100 View Drop Down
Newbie
Newbie


Joined: 22 April 2014
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote vjaffe100 Quote  Post ReplyReply Direct Link To This Post Posted: 22 April 2014 at 7:33pm

I had same error, and was able to do conversion after I put Shadow copies on for all drives and point copies to drive where was enough space. And after that (IMPORTANT) wait long enough until shadow copies were ready.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down