vCenter

 View Only
Expand all | Collapse all

VMWare Converter Fails to take Snapshot of Source Volume

  • 1.  VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 08, 2007 05:30 PM

    I am having trouble with VMware converter when I am hot cloning a machine. I receive

    "ERROR: Failed to take snapshot of a source volume. Possible Causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space".[/i]

    I have plenty of disk space they are SAS drives in a raid 5, I am hosting the converter on a 2003 server std edition x64 and trying to convert a xp sp2 box.

    On the agent log file i receive

    \[i]'App" 564 warning] Failed to create console writer[/i]

    On the Client log file I receive

    \[task,295] Task failed: P2VError SNAPSHOT_FAILURE(-1)[/i]

    Any ideas on how to fix this?



  • 2.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 08, 2007 09:08 PM

    I had the same issue. A re-install of the agent on the server I was convreting sorted the issue out. You will need to install it manually and not through the converter tool.

    Only had this when I updated to the latest version, although may not be related at all.



  • 3.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 09, 2007 12:29 PM

    Well I uninstalled the agents and then reinstalled it using the Converter.exe and still came up with the same error message. I am running symantec anti-virus. Could that have anything to do with it being denied to take snapshot of a source volume?



  • 4.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 09, 2007 01:39 PM

    Currently the converter is going from 1% to 2% then stays there a while and then will jump to 11% and then fails. When I check the size of the file it is creating it jumps to 2Mb then again to between either 4Mb or 9Mb then shortly there after fails. If I click on properties of the .vmdk that is being created it will show smaller that what it shows on the screen then I click OK or Cancel and the size will go up but if I leave it sit it will jump to 11% and then fail.



  • 5.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 09, 2007 05:43 PM

    Well I decided to run the conversion on a spare server that is running our wsus and the conversion worked like a charm. Only took 12 minutes. I installed the agent locally then did the conversion and didn't have any problems. Granted the box was running server 2003 where as the box I was originally trying to convert is running windows xp sp2. One thing that I thought may have played a factor in but haven't tested is that I was remoted into the computer that is doing the conversion with the computer I was trying to convert. So not sure if that could have made it fail but for now it is converting the computers that I originally wanted to be converted.



  • 6.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 09, 2007 05:44 PM

    Shadow Copy is still not working on my XP box but conversions for 2003 server works with no problem.



  • 7.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 10, 2007 01:52 PM

    Hi,

    i have the same problem with XP Clients, NT and 2000/2003 Server is ok.

    What have i done:

    Manuall install of the Agent on the source XP machine -> no sucess

    Version is 3.01 Enterprise

    Any ideas?

    Greetings dietzke

    Message was edited by:

    dietzke



  • 8.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 14, 2007 01:44 PM

    A machine I'm P2V-ing gave me the same error, I fixed it by running a chkdisk on the partition. Details of the machine:

    win 2000 server

    dynamic disk (broken mirror) with util partition (I think)

    P2V options used:

    -resize partion

    -hot cloning

    -remote agent install



  • 9.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 18, 2007 08:38 AM

    Hi,

    in my case, there are two scenarios.

    One of my server doesn't have Volume Shadow Copy and Microsoft software Shadow Copy Provider services running. Start those two services and VMware converter continue ok.

    Other servers have VERITAS installed and I stop the VERITAS services, I got 11% error. VERITAS replaces Disk Manager and changes MS Shawdow Copy Provider and Volume Shawdow Copy services to Manual start. So, if you have VERITAS running on your server, don't stop these serivces and you will be fine. To be exact, it is the VERITAS VSS Provider service that you can not stop.

    I hope this will help.

    Cheers,



  • 10.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 21, 2007 08:12 AM

    Hi,

    i've got this hints and i've done it this order with success. Seems that the Reboots are important...

    1. Uninstall Vmware Converter agent from the machine.

    2. Reboot the machine.

    3. Install Vmware Converter agent back on the machine.

    4. Reboot the machine. (Somehow rebooting is very important)

    5. Make sure Vmware Converter Agent Service is running.

    6. Make sure you have atleast 200 mb of space available on the Volume being cloned.

    7. Make sure the Workstation, Server, Netbios and VSS (Volume Shadow Copy – XP default service) Services are running on the XP machine.

    8. Restart the VMWare Converter Service on the VMware Converter Manager server.

    9. Remove any previous task and create a new task.

    10. Try conversion.

    Greets



  • 11.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted May 29, 2007 12:03 AM

    we solve this problem with a CHKDSK.

    a disk sector was endomaged



  • 12.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jun 01, 2007 07:53 PM

    Was this chkdsk on the VMWare Server or on the XP machine you were attempting to clone?



  • 13.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jul 06, 2007 06:07 AM

    on xp machine



  • 14.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jul 13, 2008 02:52 PM

    I had the same exact error and it looks like the conversion is now progressing much farther than before:

    My Volume Shadow Copy service was disabled. I set it to Manual, started the service, then restarted the conversion. Bam, it is now going past the 11% bomb.

    Windows XP Pro, SP2



  • 15.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jun 07, 2007 04:47 PM

    I had identical Problems, as the MS Software Shadow Copy Provider Service was not working.

    The link below helped me to solve the issue so i could start both shadow copy services VSS and SwPrv

    http://www.computing.net/windows2003/wwwboard/forum/5105.html

    and the cloning works.



  • 16.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 02, 2007 03:55 AM

    Me 2 - getting failure

    "ERROR: Failed to take snapshot of a source volume. Possible Causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space".

    HP Laptop nw9440 4GBRAM, 100GB Int Disk w/ 64GB free, 160GB Ext Disk w/ 80GB Free, WinXPSP2

    Converter Setup

    >Physical Machine

    >This local machine

    >Select volume c:93GBTotal/29GB Used and set "New Disk Space" to 40GB

    >Left checkbox checked for ignore page file and hib file

    >Destination set to VMware standalone virtual machine

    >VM Name = Test, VM Location = F:\VMware\test

    >Type VM to Create: default WS5.x

    >VM Options: Have tried both Allow VDF to Grow & Allocate DskSpc now

    In first case, goes to 11% than gets error,

    In second case, builds test.vmdk file up to ~41GB then errors out.

    Have tried converter with target set to 40GB fixes and 40GB

    Still ends with error

    I have done the CHKDSK - no success

    I have checked to see that Volume Shadow Copy and Microsoft Software Shadow Copy Provide services are running - no success

    I have done the Uninstall/Reboot/Install/Reboot and that the VM Converter Service is running - no success

    I have removed any previous task and started converter over - no success

    Ok ... so now what ... I think I have tried all the ideas posted so far ...

    \- - - This is a company evaluation activity to determine whether to buy into the VMware approach ... hmmm



  • 17.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 07, 2007 09:08 AM

    Had the same Problem, sloved as follows:

    1. look for enough free HDD Space

    2. CHKDSK

    3. Start any Services that are stopped ... :smileywink:

    - Volume Shadow Copy Service

    - Server

    - MS Software Shadoy Copy Provider

    - Restart the VMware Converter Service

    That fits for me :smileyhappy:



  • 18.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jul 15, 2008 05:27 PM

    I also was getting this error. I was trying to convert a 2003 Winders server with a 100 GB drive, of which only 30 GB was being used, to a VM with 50 GB. After doing a reboot after the convertor installs, defragging the harddrive, running checkdisk, using the current version and the previous version, I was still getting the error.

    So I tried doing the conversion WITHOUT changing the size of my harddrive and at long last I have got past the dreaded 11% failure point and gotten up to 20% and it looks like it is going to convert. I will address shrinking the harddrive requirements later.

    Russ...



  • 19.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 06, 2008 07:26 PM

    Well I'm still working on this but sometimes the simple answer is right in front of us the XP machine's disk was in FAT32 so I am currently converting it to NTFS which I believe is a requirement. I'll try to provide an update.



  • 20.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 06, 2008 08:17 PM

    To everyone here, and to compliment everyone who has contributed.

    There are countless ways to have a VSS snapshot fail, or snapshot fail with stcbasic.sys.

    Converter relies on the Microsoft VSS writer to be enabled and functional to perform a backup of the system. If VSS is disabled or completely broken, it is only one of many causes.

    Here is a quick breakdown of snapshot failures (in my own persona experience):

    For Any Conversion

    - Disable any diagnostic partitions partitions

    For VSS Based Conversions (XP/2003):

    - Converter not installed/run as admin (reinstall)

    - Converter not installed to C:\ (reinstall)

    - Partition is FAT instead of NTFS (upgrade to NTFS)

    - "MS Software Shadow Copy Provider" from Service.msc (in the case of XP) is disabled or replaced (by another VSS backup software) ... remove other software and enable the service

    - "Volume Shadow Copy" ensure that it is enabled

    - Check for VSS errors in the System's Event Log (eventvwr) - troubleshoot these, and you should fix it (example: http://support.microsoft.com/kb/941956 )

    For stcbasic.sys Based Conversions (2000/NT4):

    - Converter not installed/run as admin (reinstall)

    - Converter not directly installed to C:\ (reinstall)

    - chkdsk the drive for errors on a reboot

    I will post this as a document. what I would suggest is that people post comments to the document and I will add them onto the primary. that way we don't have a forum thread getting flooded, and it will be a quick and dirty summary.

    Cheers,



  • 21.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Broadcom Employee
    Posted Feb 10, 2012 07:31 AM

    Please upload log bundle to check exact problem with your conversion.



  • 22.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 08, 2007 03:09 AM

    not having enough free disk space

    \- if you are resizing the disks you need 200mb free

    \- do not select the diagnostic partition

    \- ignore pagefile

    \- converting into a vmdk file greater then 250gb conflicts with the default vmfs blocksize of 1mb - wont fit

    \- local admin can sometimes do the trick



  • 23.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Dec 06, 2007 02:15 PM

    I found out why the VMconverter was failing, after a number of MS articles and Vmware communities theories...

    In our environment, for whatever reason there is an issue starting the MS Shadow Copy Service, and the fix was not an easy one to find.

    I've put the fix into a batch file (below) that needs to be run on each machine prior to running VMConverter, it re-registers the dlls/components for both the VSS and the MS Shadow Copy Services. This batch file does create a pop up for every .dll it registers, but it works and it takes less than 10 seconds to run manually.

      • the VSS and MS Shadow Copy services MUST be set to Manual and Started**

    It turns out that when the Volume Shadow Copy Service requestor (backup application such as Vmware converter) was calling the Volume Shadow Copy Service, one of the components that VSS relies on (A software-provider) was failing. I think that VMConverter must use or be a software-based shadow copy provider as Software-based providers create/maintain a "point in time" view of a volume. (Can a guru at VMWare confirm this?) The MS Shadow Copy Service manages software based shadow copies so it must link in with the VSS service even though the only dependencies between the two services is the RPC service.

    Anyway, its working now - I can now start the VSS and MS Shadow Copy Service successfully and VMware converter works like a charm..!!

    Here is the batch file, copy and paste into a txt file and rename to .bat! < ; - = )

    cd\

    pushd "c:/windows/system32"

    regsvr32 ole32.dll

    regsvr32 vss_ps.dll

    vssvc /Register

    regsvr32 /i swprv.dll

    regsvr32 /i eventcls.dll

    regsvr32 es.dll

    regsvr32 stdprov.dll

    regsvr32 vssui.dll

    regsvr32 msxml.dll

    regsvr32 msxml2.dll

    regsvr32 msxml3.dll

    regsvr32 msxml4.dll

    net start vss

    net start swprv



  • 24.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Dec 24, 2007 10:04 AM

    Same problem here, but eventhough I did a chkdsk, ran the batch file (regsvr32 msxml4.dll couldn't be loaded), uninstall, reinstall... I still get this message I don't know what to do... any ideas?



  • 25.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Dec 24, 2007 11:46 AM

    I had the same issue on a couple of machines, this batch file works regardless of that error registering that dll.

    Just check that the MS Software Shadow Copy Provider and the Volume shadow copy service is STARTED...

    Goodluck!

    PS tell us more about your error



  • 26.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Jan 12, 2008 04:25 AM

    I had the same problem running the P2V. I've tried everybody's suggestions but none really solved the problem. I uninstalled one program on the server: Amerivault Backup Agent and all problem went away. The Amerivault backup agent must have messed up the Windows Volume Shadow Copy service and its files so unistalling it would restore the original settings.

    So these are the steps I would follow:

    1. Uninstall Amerivault Backup Agent (or any other backup agent such as Backup Exec)

    2. Uninstall Convertor Manager and Agent

    3. Reboot computer

    4. Re-install Convertor Manager and Agent

    5. Run the P2V again and it should work.



  • 27.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Aug 06, 2008 08:24 PM

    Post additions and suggestions to this document:

    http://communities.vmware.com/docs/DOC-6842/



  • 28.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Nov 14, 2008 04:00 AM

    Hi all,

    I need advice on my error as well.

    11:55:28 AM Step 1 : Connecting to VMware Converter Agent on localhost

    11:55:28 AM Step 2 : Creating target virtual machine and converting data

    11:55:31 AM Configuring parameters for the target virtual machine...

    11:55:33 AM WARNING: Dropping extra floppies

    11:55:33 AM Creating target virtual machine...

    11:55:36 AM Taking a snapshot of the volume...

    11:55:37 AM ERROR: Failed to take snapshot of a source volume.

    Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems,

    and not having enough free disk space.

    Please advise.



  • 29.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Apr 15, 2010 08:52 AM

    Volume Shadow Copy "Service" is the caused of this issue.

    Best Regards,

    Hussain Al Sayed

    If you find this information useful, please award points for "correct" or "helpful".



  • 30.  RE: VMWare Converter Fails to take Snapshot of Source Volume

    Posted Feb 09, 2012 10:57 PM

    I had this same issue and this is what i found and worked for me.

    On the server i was trying to clone/convert the  following services were not started:

    Microsoft Software Shadow Copy Provider

    Volume Shadow Copy

    Once they were both started and i ran the scheduled task i was able to complete the clone/convert process.

    The Microsoft Software Shadow Copy Provider on one of my servers was in the "Stopping" state. I was unable to start/stop/restart it.  I had to find the process with ProcessExplorer.exe and find the pid.

    Process is "swprv"

    From a cmd prompt i ran:

    taskkill /pid ***** /F (force the service to stop)

    Went back to Services and started the service and completed the clone.

    Hope this helps!!!