Install vCenter Converter on your "Source" vm, reboot it, then try it again.

EDIT:

Then try to V2V from the "Source" VM, not your vcenter server.

Have you installed the latest VMtools? As VMtools is the "controller"  that helps with the quiescing of the processes on the machine and allows the cloning process to continue

Gregg

yes, installed with latest vmtool. the source VM freshly installed OS and nothing running except OS. I can clone on cold vm, only failed when it was started up. i have try disable the anti-virus and it's still same error. also try uninstall vmtool then reinstall back, still same. coud it be issue on version 5.0 since i'm using vCenter 5.0 and ESXi 5.0.

I test clone on vm with OS SUSE x64, and it works nicely. it seems like i only have issue with Microsoft Windows Server 2003 x64. it looks like the error on taking snapshot of virtual machine.

The guest OS has reported an error during quiescing. The error code was: 4 The error message was: Quiesce aborted.

Hi

Have you set the configuration settings for the machines to server 2003 x 64 for the ones that are obviously srver 2003 x64?

I've had problems where a misconfiguration like this has caused errors

Gregg

yes, i did

after did some testing, now i found that among the 4 ESXi hosts, only 1 can run the cloning. other 3 hosts, still unable to. i try to find the different between these hosts, so far all the setting and configuration are the same. 

I have the same problem and same error message.  I cant use vcenter 5 on vsphere 5 to clone a brand new windows 2008 installation with vmware tools installed.  The Source VM is a pure windows install from the disk, nothing else installed, not even antivirus.  We only purchased vmware (as opposed to use the free version) to get the clone feature, which doesnt seem to work for windows server 2008, unfortunately.

Have anyone solved this issue? I have the same problem.

When my backup program Acronis tryies to make a snapshot it fails, but if i make a snapshot in vcenter it succeds. This is a litte bit wired.

I think this issue is caused because the resources are not enough for the virtual machine, but i'm not sure.

Does anyone passed this problem?

Thanks!

I have resolved the issue.

The problem was a disk signature conflict.

I saw an error in application log of windows with the diskpart.

Here you can resolve this conflict with this guide:

http://www.sysadminsblog.com/microsoft/event-58-the-disk-signature-of-disk-n-is-equal-to-the-disk-si...

I hope it will help, for me it worked.

I've seen this be tied to a few different issues..

1. Verify your VSS providers aren't messed up.

2. Try using the VMware converter standalone tool to clone

Hi mesh0

If I didnt come across this type of problem directly ,but

I think there is some compatibility problem , please check with microsoft site if any update

is available to fix this issuse .

"Before you judge a man, walk a mile in his shoe."

@Neo17

When you start an Acronis backup, change the VSS type.

Under "Options" | "Volume Shadow Copy Service" | make sure the option "Use Volume Shadow Copy (VSS)" is selected, then in the drop down list box, select "Software - System Provider".

This should get you going.

On the VM you are trying to clone, try running the "chkdsk <driveletter>: /F /R"

Run that on all the disks on the machine you want to clone.

If that doesn't work, I usually will create a cold backup (Acronis or Ghost) and just drop that image into a VM then do a "Reconfigure" (using VMware Converter 5) of that VM.