Msg.: Unknown error returned by VMware Converter Agent

[monokelmann]

Hi,

what are these words trying to tell me? Im using the Converter3.0 build 39557.

I've tried a 2k3-Server, a NT4.0SP6-Server, a NT4.0SP6wks. They all went fine up to 97% - 99% and than they failed with:

Unknown error returned by VMware Converter Agent

Has anybody ever got a running VM-image?

The time between happines and disappointment has been quite short

Regards,

Monkelmann

[LeiniesRed]

Same problem, same solution. I'm running the BETA tool for now. VMWare seems to have rolled out a version that flat out doesn't work for many end users.

Come on VMware, look at the post and view counts. This is the largest reported problem with VMware Converter 3.0. Re-Roll the beta version as BETA2 or something so we can get our jobs done while you "fix" the production version.

Message was edited by:

LeiniesRed

[ssltech]

Hi,

We are suffering this exact problem.

Any idea where/how we can obtain the BETA version 33128?

Many thanks.

[ezarikian]

Hello All, I had the same problem and I did two things, after that, I got a successful import, the two things were to disable the antivirus (the server had "Trend Micro" AV running) and I reinstalled the VMWare converter software, this time with a complete install and from the physical console, as per some of the recommendations I read.

I hope that helps some of you out there, it did the trick for me, and I had about 7 unsuccessful import attempts.

If you are migrating a Windows Domain Controller, I also found out the hard way that you shouldn't image it "while it's hot", do it while it is shutdown, and use the image immediately afterwards as it will eventually cause a USN Rollback in your active directory if you take too long to put it to work. You obviously have to run the new server instead of the original one, once one of the starts, the other will be treated as a spoof impostor.

Regards

Esteban

[carehart]

FWIW, I'm experiencing the same error (stops at 97%, with the failure in the log being reported as "P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.CloneFault)").

It's a new install of Converter (never used it before, nor ever successfully), build 39557, the latest (and only) currently available (labelled as the "starter edition").

I've tried both "disk space allocation" options, and I've tried setting the Network setting to 1 NIC, as bridge and nat and "host only", and even with 0 NICs. None work. Any other variants to try? (One respondent above suggested changing to using a static IP, but that just doesn't make sense for me, I don't think. Open to clarifications.)

For clarification, I'm trying to create a clone of my current machine, the very one on which I'm running the converter. That's a fully supported configuration, according to the docs and the interface itself. I am NOT trying to clone it onto the same drive on which the machine is installed. This is a laptop, and I'm trying to do the clone onto a USB-connected external hard drive (with several times more space free than the total hard drive on the laptop, so space is not the issue).

Hope that helps clarify, if those of us failing might have similar unique configs. Open to any more thoughts.

[karldavidson]

Does VMware monitor these forums? All I see is a bunch of people explaining a problem and no solution posted, or even a response.

Help!

[sdemigne]

Hi,

I had the same problem with a physical NT4 box.

I searched the web until I was able to find the BETA version mentionned.

I downloaded it, installed it and it DOES WORK. That fixed my problem.

\[Reference to download that violates VMware license terms deleted]

Sebastien

Message was edited by: Forums Administrator

RDellimmagine

[carehart]

Could the forum admin who deleted the link perhaps also kindly help us out by forwarding this long thread to someone at VMWare who may attend to it? Since the tool is freeware, the thread may not be something they're paying attention to.

Still, the converter is something that I (and others) have used as a tool to motivate others to consider using VMWare. The ability to create a VM out of a physical machine is a nice feature. But if it doesn't work, it just annoys and puts off these prospective new users....not to mention existing users of the tool or VMWare in general.

You may say, "take it up with support", but who wants to pay for support for a freeware tool? It seems we're stuck between a rock and a hard place.

If the admin has the diligence to be watching this thread to remove such a link the day it's posted, could they please offer the same diligence in bringing this long-standing (and seemingly ignored) thread to the attention of someone who may care as much as the license-violating link? Thanks.

Message was edited by:

carehart

[CoffeeActionMan]

I would like to echo the need for an answer to this issue: I am trying to Hot Clone a critical Windows 2000 Professional workstation from an aging hardware platform, and Converter gets to Step 2, 97% and then fails with 'unknown error returned by VMware Converter Agent'. The source box has only a single partition, C:\, and I really need this to work in order to sell this technology to mgmt.

From the Client log:

\[2007-04-12 11:32:28.160 'P2V' 3712 info] \[task,275] Starting execution of a Task

\[2007-04-12 11:32:28.160 'P2V' 3712 info] \[ufaTask,173] Successfully connected to VMImporter

\[2007-04-12 11:32:28.160 'P2V' 608 verbose] \[jobManager,269] Raising event 4 for job 5

\[2007-04-12 11:32:28.207 'App' 3712 verbose] \[imageProcessingTaskWrapper,109] Successfully connected to VmiImportTask::task\{4}

\[2007-04-12 11:32:28.238 'App' 3712 verbose] \[imageProcessingTaskWrapper,817] Start managed object method for task VmiImportTask::task\{4}

\[2007-04-12 11:32:28.238 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:28.238 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:28.285 'App' 3016 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:28.300 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:28.300 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:31.050 'App' 3016 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:31.066 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:31.066 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.284 'App' 608 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.331 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.331 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.363 'App' 3016 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.378 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.378 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.925 'App' 3016 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.956 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.956 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:32.988 'App' 3016 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:32:33.003 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:32:33.003 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.173 'App' 3096 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.220 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.220 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.283 'App' 608 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.548 'App' 608 verbose] \[imageProcessingTaskWrapper,886] Remote task VmiImportTask::task\{4} completed

\[2007-04-12 11:33:02.564 'App' 3712 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.564 'App' 3712 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.595 'App' 608 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiImportTask::task\{4}

\[2007-04-12 11:33:02.611 'App' 3712 verbose] \[imageProcessingTaskWrapper,515] Cleaning up remote task VmiImportTask::task\{4}

\[2007-04-12 11:33:02.626 'App' 3712 verbose] \[imageProcessingTaskWrapper,1201] Disposing task wrapper for task VmiImportTask::task\{4}

\[2007-04-12 11:33:02.658 'P2V' 3712 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.CloneFault)

\[2007-04-12 11:33:02.658 'P2V' 3712 verbose] \[task,339] Transition from InProgress to Failure requested

\[2007-04-12 11:33:02.658 'P2V' 3712 verbose] \[task,388] Transition succeeded

\[2007-04-12 11:33:02.658 'P2V' 3712 verbose] \[job,231] Job 5 changing state from 1 to 2

\[2007-04-12 11:33:02.658 'P2V' 3712 verbose] \[serialization,213] Serializing job 5

\[2007-04-12 11:33:02.658 'P2V' 3712 verbose] \[serialization,220] Archiving job to C:\Documents and Settings\neid\Application Data\VMware\p2v30\jobs\00000005.xml

\[2007-04-12 11:33:02.673 'P2V' 3712 verbose] \[jobManager,269] Raising event 2 for job 5

\[2007-04-12 11:33:02.673 'P2V' 3712 verbose] \[jobManager,269] Raising event 4 for job 5

\[2007-04-12 11:33:02.673 'P2V' 3712 verbose] \[jobManager,269] Raising event 6 for job 5

\[2007-04-12 11:33:02.673 'VmdbSvc' 3712 verbose] Shutting down VMDB service...

\[2007-04-12 11:33:02.673 'VmdbSvc' 3712 verbose] Unregistering callback...

\[2007-04-12 11:33:02.673 'VmdbSvc' 3712 verbose] ...done

Thanks

[czatts01]

I've gotten it to work with one of the work arounds listed here. I don't understand how this question can be marked as snswered.

I was able to find a BETA (33128) version of vmware converter. I installed it and changed my date back to August '06. I created the VM from my W2K pro laptop. It work fine and in 1/3 the time of the "normal" version of vmware converter. I loaded the vm onto a spare hard drive I have for my laptop and it booted without the dreded "blue screen of death"!!

I won't publish the link to the beta version here because it will get deleted. However, if you send me an email, I will send you the link and if that doesn't work, I'll send you the beta version. email address: searay1901998@yahoo.com

VMware needs to find an answer to this issue. Why does the Beta version work and "normal" version not?

[mchpis]

Yeah I don't know why this thread is set as "Answered" as it clearly isn't.

I to am having the same issue. I'm currently working with our VMware Systems Engineer, and i'm opening a SR with VMware to see if I can get this resolved.

I get the same error "Unknown error returned by VMware Converter Agent" when trying to COLD convert.

I don't get any errors and the process succeeds when doing a HOT convert, but the VM will not boot, and will not detect any disks.

Seems this version has major problems.

[mchpis]

Ok, so I opened an SR with VM. Opon looking at the logs from my failed conversion they decided it was a bug in the application.

The tech was going to consult with the engineers and see what their next steps will be.

Hope they fix the bug and release an updated version..

[wantmilk]

On the remote source, type `net start stcp2v30` if the driver isn't loaded, try manually installing the agent "with the Converter installer" and reboot the host. Then try the conversion again...

[wantmilk]

This only relates to issues on win2k and nt4...

[sdemigne]

Hi,

This morning, we had a VMware Rep at our offices for some questions about VI3.

I spoke to him about this situation and he told he would look it up with VMware and should get back to me soon.

He also suggested that the Enterprise version of Converter should not have this problem. Has anyone had the problem with the Enterprise version?

I'll keep you updated when I hear back from VMware.

Sebastien

[CoffeeActionMan]

Hi -

I am sorry, but how do I know if I have the enterprise edition? I am not using the free version, if that is the difference. In Help -> About it simply says VMware Converter Application 3.0.0 build-39557. A license file was required for my version.

I have also had 2 more Converter failures, just today:

a) Cold Clone of Windows 2000 server - File setupdd.sys could not be loaded. The error code is 1024. Setup cannot continue - Press any key to exit.

b) Cold Clone of a different 2000 Server - same old unspecified error message.

Thanks much to you and everyone else who is persuing a solution with VMware.

Craig

[sdemigne]

CoffeeActionMan,

If you have entered a license file to use Converter, you are using the Enterprise version (the free edition does not need any license file).

You cannot do a cold clone either with the Starter Edition. (See http://www.vmware.com/products/converter/get.html)

So, you must have the Enterprise Edition.

Have you tried to clone with the Beta version to see if you have the same result ?

[CoffeeActionMan]

Sebastien -

I tried, ran into the expiration issue, set my (Converter Client) clock back 1 year, ran thru the wizard, but the beta Converter simply died. In short, I did not spend any more time because our computers are all set to synch time and I did not want to interrupt that function because on many of our servers it is critical that the date and time be correct.

Craig

[L-Plate]

Seems to be caused by the way microsoft splits its virtual disks.

I downloaded and installed Microsoft virtual PC.

Go to File / Virtual Disk Wizard

Using the Virtual Disk Wizard compress the VHD file (I saved to a new file name).

Wierdly it turned out the same size.

I then went File / New Virtual machine Wizard and imported the virtual machine.

Then click on Settings and the disk, then set the Virtual Disk file to the compressed file.

I was then able to import it using the VMWare tool.

I hope this helps.

[carehart]

L-plate, just to be clear, are you referring to some message in this long thread that relates specifically to creating a VMWare VM out of a Virtual PC VM? Or are you somehow proposing this as a solution that (I think) most of us have of simply creating a VMWare VM from an existing physical machine? Just checking, thanks.

[tlc_trax]

This is a resolution which worked for me for the 1% - 5% - 97% failure but only relates to working on the physical machine and not remotely. (BTW This was caused by initially either having player on the machine I was trying to convert or by previously having a failed convertion from a remote machine which leaves temp files behind.)

1. Uninstall all instances of anything to do with vmware.

2. Run a search for any file containing vmware in the title and delete it.

DO NOT CARRY OUT STEP 3 THE FIRST TIME as this step may not be necessary. Also always backup your registry before editing it as you can seriously mess up your computer system if you delete keys which do not relate to vmware. Please do not edit your registry if you are not confident working in it.

3. Search for vmware in the registry and delete any keys found (including all of the vm services.)

4. Restart the machine.

5. Reinstall vmware converter.

6. Restart the computer.

This worked a treat for me but please note that you may not need to edit the registry. I only did this because I wanted to be sure that I had removed everything to do with VMWARE. I think it is worth doing all of the other steps above first without editing the registry and only then, if it is still failing, resort to registry editing and even then only if you are confident working in the registry.

Initially I thought what I had done hadn't worked but after rebooting I found that it had.