《ESX4和ESX3.5调试安装带图指导,不信调不好-convert+error.pdf》由会员分享，可在线阅读，更多相关《ESX4和ESX3.5调试安装带图指导,不信调不好-convert+error.pdf（7页珍藏版）》请在三一文库上搜索。
1、Generated by Clearspace on 2009-05-13-07:00 1 More on ERROR: Failed to take snapshot . drbking 7 posts since Feb 28, 2009 I have seen previous posts on this and have tried to follow all of the suggestions but nothing is helping. I am running XP and have two hard drives, both NTFS and both have plent
2、y of room. My destination is an external hard drive, FAT32, also with plenty of room. I am getting the message *ERROR: Failed to take snapshot of a source volume. P*ossible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space.
3、 I installed the converter as an administrator, I have rebooted multiple times, I ran checkdsk /f on both hard drives and the external drives, I have turned off all of the services that I am comfortable turning off, but I just keep getting this message. Ive attached the log file. Thanks for any help
4、. Attachments: vmware-converter-7.log (149.4 K) ryan.gallagher 37 posts since Jul 2, 2006 Reply 1. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 1, 2009 6:11 PM Is the volume shadow copy service (vss) enabled and started? Does vssadmin list shadows produce anything? What does vs
5、sadmin list volumes output? Any chance you could try Converter 4.0 instead of 3.0.3? Youll probably have the same issue, but the logs may be more informative. Thanks, -Ryan drbking 7 posts since Feb 28, 2009 Reply 2. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 2, 2009 5:39 AM
6、in response to: ryan.gallagher Thanks very much for your reply. The volume shadow copy service was enabled and started before I ran the program. Now that the program has failed (more on that in a minute), it shows that it isnt started. I assume vssadmin list shadows is something to run at a DOS prom
7、pt? It returns Error: 0 x8000ffff. I tried running 4.0 as you suggested. The first three times it failed, just as 3.0 had failed. Each time I removed the history of the failed attempted, rebooted, and tried again. On the fourth try it ran for about 12 hours and then failed at 94% with a new message
8、FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147549183 (0 x8000FFFF). Ive included a screen shot of the task progress, another of the summary, and a zip file it created when I told it to export logs. Thanks very much for you help. Attachments: More on ERROR: Failed t
9、o take snapshot . Generated by Clearspace on 2009-05-13-07:00 2 vmware summary screenshot.jpg (122.4 K) vmware screenshot.jpg (121.2 K) ConverterDiagnostics20090302081455.zip (424.0 K) ryan.gallagher 37 posts since Jul 2, 2006 Reply 3. Re: More on ERROR: Failed to take snapshot of a source volume. M
10、ar 2, 2009 10:06 AM in response to: drbking drbking wrote: I assume vssadmin list shadows is something to run at a DOS prompt? It returns Error: 0 x8000ffff.Interesting. After you run this command do the Windows Application Event logs have anything in them? (Control Panel Administrative Tools Event
11、Viewer) Reboot your system again, then please also try vssadmin list writers and vssadmin list providers, checking the event logs after each. My understanding is that 0 x8000ffff is a generic error that can be caused my many issues. For example, if vssadmin list writers isnt working then it may be c
12、overed by the following kb article: I dont know that this is your issue though, perhaps the event logs have more information. Do you have any backup utilities installed on this machine? What other software is running on this machine (database, etc)? drbking 7 posts since Feb 28, 2009 Reply 4. Re: Mo
13、re on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 4:44 PM in response to: ryan.gallagher I tried yesterday to run the whole thing again, after first double-checking that the volume shadow copy service was running. I hoped I might get lucky, but instead I got the exact same result.
14、 Ive attached the zipped error logs again. The following is what the event viewer showed at a point during the attempt: Event Type: Error Event Source: VSS Event Category: None Event ID: 8193 Date: 03/02/2009 Time: 11:25:45 PM User: N/A Computer: PN1011394 Description: Volume Shadow Copy Service err
15、or: Unexpected error calling routine CoCreateInstance. hr = 0 x80004002. More on ERROR: Failed to take snapshot . Generated by Clearspace on 2009-05-13-07:00 3 For more information, see Help and Support Center at Data: 0000: 42 55 45 43 58 4d 4c 43 BUECXMLC 0008: 31 36 38 33 00 00 00 00 1683. 0010:
16、42 55 45 43 58 4d 4c 43 BUECXMLC 0018: 33 34 39 34 00 00 00 00 3494. And at the point where it bombed out, it showed this: Event Type: Error Event Source: AutoEnrollment Event Category: None Event ID: 15 Date: 03/03/2009 Time: 3:18:02 AM User: N/A Computer: PN1011394 Description: Automatic certifica
17、te enrollment for local system failed to contact the active directory (0 x8007054b). The specified domain either does not exist or could not be contacted. Enrollment will not be performed. For more information, see Help and Support Center at Back to your questions, if I run vssadmin list shadows, I
18、get the error message in DOS, and the event viewer shows: Event Type: Error Event Source: VSS Event Category: None Event ID: 12292 Date: 03/03/2009 Time: 7:33:22 PM User: N/A Computer: PN1011394 Description: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLS
19、ID 65ee1dba-8ff4-4a58-ac1c-3470ee2f376a 0 x80040154. For more information, see Help and Support Center at Data: 0000: 43 4f 52 53 4f 46 54 43 CORSOFTC 0008: 37 30 00 00 00 00 00 00 70. 0010: 43 4f 52 53 4f 46 54 43 CORSOFTC 0018: 36 30 00 00 00 00 00 00 60. More on ERROR: Failed to take snapshot . G
20、enerated by Clearspace on 2009-05-13-07:00 4 vssadmin list writers gives me the same DOS error and this: Event Type: Error Event Source: VSS Event Category: None Event ID: 8193 Date: 03/03/2009 Time: 7:34:27 PM User: N/A Computer: PN1011394 Description: Volume Shadow Copy Service error: Unexpected e
21、rror calling routine CoCreateInstance. hr = 0 x80040154. For more information, see Help and Support Center at Data: 0000: 42 55 45 43 58 4d 4c 43 BUECXMLC 0008: 31 36 38 33 00 00 00 00 1683. 0010: 42 55 45 43 58 4d 4c 43 BUECXMLC 0018: 33 34 39 34 00 00 00 00 3494. vssadmin list providers gave me th
22、e results shown in the attached jpg and did not produce any error in the event viewer. I do not have any backup utilities running on the machine. The only thing active while I try the program are McAfee (which Ive disabled the scan) and Fiberlink, a VPN to the office, but it is only sitting in the b
23、ackground, not active. Im going to try what the microsoft link you sent said. In the meantime, thank you for any further help you can provide. Attachments: vmware screenshot DOS.jpg (19.4 K) ConverterDiagnostics20090303191028.zip (727.6 K) vmnewbee9 3 posts since Mar 3, 2009 Reply 5. Re: More on ERR
24、OR: Failed to take snapshot of a source volume. Mar 3, 2009 6:21 PM hello.Im having the same error see attached word docs.i have never used VM ware before and have been trying to conver abt 40gig hrad drive with xp pro to ext 140 gig via usb. Pretty frustrating limited and disappointing support from
25、 VM. Attachments: vm2.doc (48.0 K) screen vmware.doc (53.5 K) drbking 7 posts since Feb 28, 2009 Reply 6. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 6:38 PM More on ERROR: Failed to take snapshot . Generated by Clearspace on 2009-05-13-07:00 5 in response to: vmnewbee
26、9 This is my first time with VM too. Following the advice I got, I ran the advice I got if vssadmin list writers isnt working then it may be covered by the following kb article: | vmnewbee9 3 posts since Mar 3, 2009 Reply 7. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009
27、6:48 PM in response to: drbking thanks Im there now. ryan.gallagher 37 posts since Jul 2, 2006 Reply 8. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 6:49 PM in response to: drbking Thanks for all the info drbking; this looks like a good place to start in figuring out th
28、e issue with vss on your system. Ill try to research it a bit and see if theres anything else we can try. Let me know how your attempt at following that KB goes; just be careful with any registry modifications, -Ryan drbking 7 posts since Feb 28, 2009 Reply 9. Re: More on ERROR: Failed to take snaps
29、hot of a source volume. Mar 3, 2009 6:51 PM in response to: ryan.gallagher I found that I was missing vssui.dll on the PC. Downloaded it and then vssadmin list writers worked. So Im running the converter again now. Wont know till morning if it works. Thanks for all the help. ryan.gallagher 37 posts
30、since Jul 2, 2006 Reply 10. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 6:53 PM in response to: vmnewbee9 bmnewbee9, Can you follow the same diagnostics steps of running vssadmin and checking event logs, etc. given earlier in this thread. Also attaching the diagnostic
31、bundle for this task would be helpful. (Based upon the screen shot you may have a different vss issue than drbking.) Thanks, -Ryan drbking 7 posts since More on ERROR: Failed to take snapshot . Generated by Clearspace on 2009-05-13-07:00 6 Feb 28, 2009 Reply 11. Re: More on ERROR: Failed to take sna
32、pshot of a source volume. Mar 3, 2009 6:53 PM in response to: vmnewbee9 I see that a small part of my reply was missing - running the microsoft thing, I found that I was missing vssui.dll. Downloaded it, ran the microsoft thing, and now am running converter again. Will know in the morning if it work
33、s (takes about 9 hours). ryan.gallagher 37 posts since Jul 2, 2006 Reply 12. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 6:54 PM in response to: drbking Thats good news. Let us know how it goes. Ill be back online in a couple hours. Hope the conversion goes well for yo
34、u, -Ryan vmnewbee9 3 posts since Mar 3, 2009 Reply 13. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 8:08 PM in response to: ryan.gallagher ok Ive gone through the steps except for the last part, question are my VSS writers are now listed should i see all of the listing
35、of the last step and if not should I carry on with the manual entries? Check the attached.in any case I tried once i got to this step and no joy same error.so i guess i have to start from the top? Thanks Jacques Attachments: vssadmin screen .doc (49.5 K) ATT00002.htm (1.5 K) ryan.gallagher 37 posts
36、since Jul 2, 2006 Reply 14. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 3, 2009 11:53 PM in response to: vmnewbee9 Hi Jacques, vmnewbee9 wrote: ok Ive gone through the steps except for the last part, question are my VSS writers are now listed should i see all of the listing of
37、 the last step and if not should I carry on with the manual entries? Was vssadmin list writers failing before you ran through the KB steps? Im not really sure that this was your problem given the error code in the screenshot you gave. Check the attached.in any case I tried once i got to this step an
38、d no joy same error.so i guess i have to start from the top? This screenshot looks like what you want. So vss should at least be able to communicate with the writers. More on ERROR: Failed to take snapshot . Generated by Clearspace on 2009-05-13-07:00 7 Can you attached the Converter task logs? (Rig
39、ht click on the failed task and choose Export Logs.) Also can you run through the other vssadmin list commands as drbking had done, attaching the Windows Event log entries for any that fail. Thanks, -Ryan ryan.gallagher 37 posts since Jul 2, 2006 Reply 15. Re: More on ERROR: Failed to take snapshot
40、of a source volume. Mar 4, 2009 12:39 PM in response to: drbking drbking wrote: I see that a small part of my reply was missing - running the microsoft thing, I found that I was missing vssui.dll. Downloaded it, ran the microsoft thing, and now am running converter again. Will know in the morning if
41、 it works (takes about 9 hours). Hows the conversion going? -Ryan drbking 7 posts since Feb 28, 2009 Reply 16. Re: More on ERROR: Failed to take snapshot of a source volume. Mar 4, 2009 5:28 PM in response to: ryan.gallagher Sorry to take so long to get back to you with an answer. When I left for wo
42、rk this morning it was still running, so I had to wait until I got home to find out if it worked. Great news! It worked! Thank you so much, I am really grateful for the help. For anyone looking at this thread, heres a summary of what I did: I ran vssadmin list writers from a DOS prompt. When that returned an error, I followed the instructions in the following kb article: It turned out that I was missing a file - vssui.dll. I googled the file, downloaded it to my WINNT directory, rebooted, and the Conversion program worked.