Failed install after going to 97%

[tiggemann]

Since I installed the new version(39557), I have not been able to get a successful convert either. I had no problems yesterday using the previous version. I even installed it on another machine and still have issues.

Issues: pauses at 5% for a while then jumps to 97% and then fails. Converting live machine and using the VC server as the host. The live machine is 2003 standard.

Here is the error from the client log:

\[2007-02-01 11:50:49.287 'P2V' 4188 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.CloneFault)

\[2007-02-01 11:50:49.287 'P2V' 4188 verbose] \[task,339] Transition from InProgress to Failure requested.

Here is a log entry from the conver log:

\[#1] \[2007-02-01 11:52:32.627 'App' 5736 warning] \[,0] VMHS: Failed to load vmnetMgr.dll.

[tempuseranp]

I have the same issue except mine gets to 99% and bombs.

ANybody else seeing this?

[bigroovy]

Yup....i have yet to successfully import any physical box...i keep getting P2V errors for "P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)" or "P2VError UNKNOWN_METHOD_FAULT(vim.fault.TooManyDevices)".

The "too many devices error" seems to only be with 2003 Ent. Server whereas the "sysimage.fault" one only happens to me with 2000 Adv Server.

[CUDC]

Yesterday, I got 1 image with converter 3, but today, I can't image anything.

[Jasemccarty]

The "too many devices" error can be remedied by removing all com ports from com 3 to com 9 before Converting.

Keep in mind that VM's have a limited amount of virtual hardware.

[jlindner]

We are geting the same error as tiggemann;

P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.CloneFault)

we also had one successful migration yesterday. :smileyhappy:

opening a ticket with vmware to get to the bottom of this.

[DaveH_4]

I don't know if this is coincidence or not, but I had the same stay at 5% for a while, jump to 97%, and then fail symptoms. I was trying to reconvert a previously failed convert when this started happening. I deleted all my convert tasks, rebooted both the source and destination machines, recreated my convert tasks, and the convert then worked.

[VMRoger]

I am having a similar problem: we are trying to import a Windows 2000 server or Advanced Server with SP4 machine and it quickly progresses from 5 to 97% then fails with unknown error. I am pasting vmware-converter-1.log file.

\[2007-02-07 10:08:38.303 'App' 5556 info] \[utils,153] Cleaning up temp directory C:\WINDOWS\TEMP\vmware-temp\vmware-SYSTEM\sysReconfig ...

\[2007-02-07 10:08:38.303 'App' 5556 verbose] Plugin 5 path: ufa-vmImporter.dll

\[2007-02-07 10:08:38.303 'App' 5556 verbose] Plugin 5 absolute path: C:\Program Files\VMware\VMware Converter\ufa-vmImporter.dll

\[2007-02-07 10:08:38.422 'App' 5556 info] \[plugin,111] VMImporterPlugin Init

\[2007-02-07 10:08:38.422 'Ufa' 5556 info] Initializing SSL context

\[2007-02-07 10:08:38.437 'BaseLibs' 5556 info] Using system libcrypto, version 90709F

\[2007-02-07 10:08:38.437 'Ufa' 5556 info] VMDB pipe name:
.\pipe\vmware-ufad-p2v30-vmdb, use SSL: true

\[2007-02-07 10:08:38.437 'VmdbAdapter' 5556 info] Using new VMDB VMOMI serialization format

\[2007-02-07 10:08:38.437 'Ufa' 5556 info] Plugin started

\[2007-02-07 10:08:38.437 'App' 5556 info] \[plugin,119] UfaClientPlugin Start

\[2007-02-07 10:08:38.452 'App' 5556 info] \[plugin,132] UfaSlavePlugin Start

\[2007-02-07 10:08:38.452 'App' 5556 info] \[plugin,182] SysMigrationPlugin Start

\[2007-02-07 10:08:38.452 'App' 5556 info] \[plugin,119] SysReconfigPlugin Start

\[2007-02-07 10:08:38.452 'App' 5556 info] \[plugin,126] VMImporterPlugin Start

\[2007-02-07 10:08:38.452 'App' 5556 info] \[serviceWin32,411] ufad-p2v service started

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] Impersonating user Administrator in session 3C8182D6-BF90-40D7-8D69-DF772ADD4026

\[#1] \[2007-02-07 10:16:30.810 'Vmsvc' 5604 info] VMServices Plugin initializing

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] \[,0] Msg_Reset:

\[#1] \[msg.dictionary.load.statFailed] Unable to get information about file "C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\config.ini": The system cannot find the file specified.

\[#1] \----

---

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] \[,0] PREF Optional preferences file not found at C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\config.ini. Using default values.

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] \[,0] Msg_Reset:

\[#1] \[msg.dictionary.load.statFailed] Unable to get information about file "C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\settings.ini": The system cannot find the file specified.

\[#1] \----

---

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] \[,0] PREF Optional preferences file not found at C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\settings.ini. Using default values.

\[#1] \[2007-02-07 10:16:30.810 'App' 5604 info] \[,0] Msg_Reset:

\[#1] \[msg.dictionary.load.statFailed] Unable to get information about file "C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\config.ini": The system cannot find the file specified.

\[#1] \----

---

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] PREF Optional preferences file not found at C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter\config.ini. Using default values.

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] Msg_Reset:

\[#1] \[msg.dictionary.load.statFailed] Unable to get information about file "C:\Documents and Settings\Administrator\Application Data\VMware\config.ini": The system cannot find the file specified.

\[#1] \----

---

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] PREF Optional preferences file not found at C:\Documents and Settings\Administrator\Application Data\VMware\config.ini. Using default values.

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] Msg_Reset:

\[#1] \[msg.dictionary.load.statFailed] Unable to get information about file "C:\Documents and Settings\Administrator\Application Data\VMware\preferences.ini": The system cannot find the file specified.

\[#1] \----

---

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] PREF Failed to load user preferences.

\[#1] \[2007-02-07 10:16:30.826 'App' 5604 info] \[,0] Using system libcrypto, version 90709F

\[#1] \[2007-02-07 10:16:30.887 'App' 5604 warning] \[,0] VMHS: Failed to load vmnetMgr.dll

\[#1] \[2007-02-07 10:16:30.887 'VmMisc' 5604 info] Max supported virtual machines: 1200

\[??] \[2007-02-07 10:16:30.887 'App' 5440 info] \[,0] HOSTINFO 1332687547920 @ 2000100000Hz -> 0 @ 1000000Hz

\[??] \[2007-02-07 10:16:30.887 'App' 5440 info] \[,0] HOSTINFO ((x * 2198913309) >> 42) + -666310458

\[2007-02-07 10:52:48.052 'VmdbSvc' 4144 verbose] IVmdbPipe2Impl operation completed with error: The pipe has been ended.

\[2007-02-07 10:52:48.052 'App' 4144 verbose] CloseSession called for session id=3C8182D6-BF90-40D7-8D69-DF772ADD4026

\[2007-02-07 10:52:48.052 'VmdbAdapter' 4144 verbose] Removed vmdb connection /db/connection/#1/

\[#2] \[2007-02-07 10:53:15.740 'App' 4144 info] Impersonating user Administrator in session 16CE92BB-4DD7-47A6-97AB-

Can someone help?

[MTLG]

Same / similar issue attempting to convert Windows 2000 physical machines.

Gets to 100% and fails. Here's a snippet from the client log:

09:32:00.130 'P2V' 1952 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)

And from the converter log:

\[#2] \[2007-02-12 09:31:59.799 'App' 1960 error] \[imageProcessingTaskImpl,552] UfaSysReconfig::task\{1}::task\{8}: Image processing task has failed with MethodFault::Exception: sysimage.fault.FileCreateError

\[#2] \[2007-02-12 09:31:59.819 'App' 2504 error] \[imageProcessingTaskWrapper,1124] ImageProcessingTask FAILED. Fault name: sysimage.fault.FileCreateError

\[#2] \[2007-02-12 09:31:59.959 'App' 2504 error] \[imageProcessingTaskImpl,552] VmiReconfigTask::task\{7}: Image processing task has failed with MethodFault::Exception: sysimage.fault.ReconfigFault

Any help with this would be GREATLY appreciated.

[hamed_m80]

Can you check if your server is configured with dynamic disks?

[lacan]

The console always displays 97% even if fails at 5%...it makes u think it was about to end but don't be fooled by this..even if it fails at 3% it will jump to 97%. Hope this helps....I was fooled by this myself a couple of times.

[seamus19]

I had the same problem. I was trying to convert a drive that was larger than the block size. Check the block size of the datastore that you are converting the server to. If its 1mb it will only convert a max of 256GB. 2mb only converts max 512GB, 4mb converts max 1024GB, 8mb converts max size 2048GB. I had to remove and add this datastorage and reconfigured.

[TexasRed1974]

I've been banging my head against the wall to get this to work. I was having these same issues on 2 servers. I want to share what it took to get mine to work:

Server A:[/u]

Windows 2000 Server SP4

120G HD (Single IDE Dynamic Disc)

What I did:

-Uninstalled VMWare Converter

-Rinstalled Converter on server.

-Rebooted and Disabled Symantec AV

-Converted local machine directly to ESX Host, bypassing Virtual Center Server

-Increased size of both volumes

Server B:[/u]

Windows Server 2003

500G HD (6 drive SCSI Array)

What I did:

-Uninstalled and Reinstalled Converter on Server

-Checked necessary services (from an earlier post) and found that "MS Software Shadow Copy Provider" was stopped and set to manual.

-Set shadow copy service to Automatic, started it, and rebooted the server.

-Disabled Symantec AV

-Rebuilt destination datastore to use 2mb block size instead of 1mb

-Converted local machine directly to ESX Host, bypassing Virtual Center Server

-Increased size of 2 of the 6 volumes

Summary:[/u]

It appears that the 2000 box was having an issue with the flakyness of Converter, and a simple uninstall/reinstall along with the conversion direct from physical box to esx host is what allowed the conversion to run.

It appears the 2003 box was having an immediate issue with the destination datastore only allowing 256GB when converter needed 500GB; although I wish converter was more concise in it's failure messages.

That's my two cents.

[teknurd]

sysimage.fault.ReconfigFault

This particular fault is during the reconfiguration phase of the virtualization. I have experienced this exact issue on several Windows 2000 Server virtualizations. You should have the .vmx and .vmdk files in your destination location. Perform the following:

1. Move the .vmdk file to the working directory of a known good virtual machine

2. Edit the .vmx file of the know good virtual machine to add the .vmxd file you moved to the configuration. In the file, you will see something similar to the following:

scsi0:0.present = "TRUE"

scsi0:0.filename = "windowsserver.vmdk"

in the above example, you would add the following to the .vmx file:

scsi0:1.present = "TRUE"

scsi0:1.filename = "filename_of_failed_virtualization.vmdk"

3. Boot the known good server. When it boots, you will notice that the problematic drive will be available. Run a chkdsk on the volume. It may require a restart.

4. After chkdsk has run, shut down the known good virtual server and move the file back to the working directory you took it from

5. Remove the configuration changes you made to the .vmx file of the known working virtual machine

6. Using Converter, run the 'Configure Machine' process on the newly repaired vmdk file. This will make the machine bootable.

7. If step #6 worked, you should be able to boot the machine successfully.

Happy Virtualizing!

[__invited__gile]

We are also having the exact same issue, the beta converter worked exceptionally well for us, in fact we never had a failure. Since moving to the final relase we have had a poor conversion rate with lots of the 97% error.

We have tried reboots, uninstalling and re-installing, nothing appears to work. The most annoying thing is that we now cannot revert back to the beta, since it now is showing as expired!

Anyone found a fix?

[mixolydian]

I was only successful twice with this process. I thought I figured out the problem but it came back. With my physical server I got the 97% situation then removed everything and started the installations from scratch. I was successful importing my server. Next import using same server and destination, guess what, 97% error. Trying different servers and destinations but cannot succeed.

This is the most disappointing VMware product release from the best product suite in the industry I can think of.

I am not going to continue trying until another revision is released.

Hands up in the air.

[Speedbmp]

Has the Vmware team said this is a bug? I am having the same problem of getting to 97% or 99% and it fails. I have tried all of the ideas posted so far and none of them work.

Stephen

[theron]

YES

The most disappointing VMware product release ever.

[jlindner]

Did anyone try this.....(taken from Release Notes on VMware Converter 3, Build 39557)

Manual cleanup required of some Converter Agent files from remote source physical machine[/b]

In some cases, the automatic cleanup of Converter Agent files from the system on which it ran is incomplete. If there are vmware-ufad-p2v-XXXXX subdirectories remaining under %SystemRoot% on the remote source physical machine after completion of the import (either successful or failed), automatic cleanup was not totally successful, and might cause future import attempts to fail. To clean up manually (recommended), follow these steps:

1. Launch regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

2. Remove the stcp2v30 key

3. Remove the vstor2-p2v30 key

4. Remove all vmware-ufad-p2v-XXXXX keys

5. Remove all courier-XXXXX keys

6. Reboot

7. Under %SystemRoot%\system32, remove all vmware-ufad-p2v-XXXXX subdirectories

[mixolydian]

jlindner,

I did investigate this and those directories do not exist on my source server.

How about anyone else?

Thank you for the reply.

[BeSchue]

In my case it wasn't so easy. I was unable to delete the vstor2- entrys. I added the registry key DWORD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment "devmgr_show_nonpresent_devices" with a value of 1 and have done a reboot. After that I had to open the device manager, and marked the "show hidden device" under view. Now a device vstor2xx was visible und none-plug and play Drivers , and I uninstalled the driver.

Anyway, it still not working. :smileysad:

[yike]

I'm about 2 for 20 on conversions using VMware Converter 3.0. Unfortunately I did not download the beta, so I can't even go that route.

The majority of my errors are similar to what are described here. The one conversion that I did get to complete was a result of the comm port fix. Although I do the same on all servers (export and deletion of applicable SERIALCOMM keys) I'm still running into other problems. Mostly this error:

Image processing task has failed with MethodFault::Exception: sysimage.fault.FileCreateError[/i]

This is after running up to 100% usually. No leaps from 5% to 97% or anything ... slow progress until 100%, STEP2 (on the task progress tab) complete and then in STEP3 preparing the target virtual machine it fails.

Surprised so many people raved about the beta only to complain about the production release. Is that sour grapes for a small group of people or is the consensus that something is terribly wrong with the production release?

[sheetsb]

I've been having the same problem and it appears that it may be indirectly related to networking. The system I'm trying to convert has the Citrix Program Neighborhood Agent installed. It creates a fairly heavy load. I couldn't even get the conversion agent to start on the machine until I killed the one from Citrix. I tried installing and removing the converter several times on this machine and running it remotely. I couldn't use the bootable CD because the system doesn't have enough memory.

As I type this the conversion is at 16% and counting...the estimated time to complete is about 40 minutes. The system is Win2k SP4 with two "BASIC" disks of about 5-6gb each which I am increasing to 10gb each.

Bill S.

[orasun]

Hands up in the air as well! I give up!! :smileyangry:

[BRYCE STENBERG]

Same problem with various flavours of image file (symantec, microsoft, storagecraft). Think I'll go try virtual pc since this seems to be an ongoing issue with the vmware converter....:-( (pity though as I did like vmware server).

[Daniel_K]

try http://www.vmware.com/community/thread.jspa?threadID=72198&tstart=0

[Speedbmp]

Any word on a fix from Vmware?

Stephen

[admin]

Same issue converting 2003 Std with 39557.

I get "Image processing has failed with MethodFault:Exception:sysimage.fault.reconfigfault"

[zelda]

I maneged to correct this error on a w2kserver.

I had a servicepartition on an old IBM-server.

Raid 5 on an basic disk and raid 1 on an dynamic disk.

Edit boot.ini and point out the new bootpartition like this.

(old partitionstart was 2)

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS (changed 2 to 1)

\[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2000

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2000 (new)

Leave the old startpartition in the ini-file so you can choose "the right one" when you start up the new virtual server.

Delete the servicepartition before converting and good luck.

Message was edited by:

zelda

[eric_kufrin]

[i]I maneged to correct this error on a w2kserver.

I had a servicepartition on an old IBM-server.

Raid 5 on an basic disk and raid 1 on an dynamic disk.

Edit boot.ini and point out the new bootpartition like this.

(old partitionstart was 2)

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS (changed 2 to 1)

\[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2000

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2000 (new)

Leave the old startpartition in the ini-file so you can choose "the right one" when you start up the new virtual server.

Delete the servicepartition before converting and good luck.

Message was edited by:

zelda[/i][/b]

That worked for me. My Dell server had a 30MB utility partition. To delete it, I first installed the Windows Recovery Console on the server, then booted to it and used Diskpart to delete it. Prior to doing that, I modified the Boot.ini as described above.

[LeiniesRed]

Yeah, I'm kinda pissed at VMware for breaking stuff with the production roll-out. It did not bode well when they rolled out a production version that expired the same day as the beta version. That was just sloppy. The current version just flat out doesn't work on my 2k rigs.

Same server, same settings, same, same, same. The only difference between it works and it fails is that the BETA tool works and the production tool doesn't.

the 2.0 tool didn't work on cold clones on this server. The only tool that worked is the beta P2V 3 tool installed locally.

Here is what I'm doing:

Install the beta version of the P2V tool Version 3.

Reboot.

Make sure you have valid local admin accounts because you may have trouble joining the domain if you reboot with the date being off.

Change the date on the server you are trying to image. (I just roll the year back to 2006.)

Kick off the hot P2V image with no settings changes and aim it at your virtual server.

Done? Change the date back and uninstall the beta tool. No need to reboot even.

This is working great for me. Too bad I have to take an outage to P2V my Windoze (sic) 2000 rigs because I have to change the date so I can run expired BETA software.

Come on VMWare, roll out the new(er) production version of the P2V tool that works as well as the beta did. You are killin' me here. I could be hot cloning rigs if you simply re-set the expiration on the P2V Beta tool and pushed it out as production!

[rnobre]

I got the same error with this build, really dissapointing.

As from VMWare web site no beta release is available to download it, does anyone have it at your Pc that could share by mail ? Thanks

[jlindner]

The Beta expired. you can't run it even if you have it.

[LeiniesRed]

Yes, it is expired, but it runs against system date. Just change the date.

That's what I have to do until VMWARE releases a functional production release.

[aleph0]

Hi all,

I'm facing a problem with convert physical HP BL35p with NO SCSI disc on board.

I'm able to convert these servers with VMware Converter 3.0 but when I try to power on virtual machine it do not want to.

so I've solved in this way:

\- add a new virtual disc on the machine

\- boot the machine from a live CD OS (bartPe)

\- recreate the partition as primary on the newly added virtual disc

\- clone the exixting logical partitions to the newly created primary.

\- with diskpart set as active the right partition end then do a fixmbr on that disk

\- reboot and disconnect live CD.

Now all works fine

cheers

mf

[chad_vz]

POST CONTENT DELETED. (why can't posts be deleted??)

null

[coutlaw]

I've spoken to a VMware rep, who said that VMware is aware of this bug but need more tickets opened on this incident. Everyone should contact tech support (email or phone) about this problem?

[tasander]

I opened a ticket for mine, provided may logs, and then they came back and said we know its a bug. Your ticket is closed...

[tasander]

Well, thanks to an earlier post, I was able to get a server converted that had failed numerous times before. What worked?

Editing the boot.ini file and adding a new line entry, modifying the partition ID from 2 to 1. Like the other post, I too have a utility partition on the server, so my windows boot partition wasn't the first one.

Of course, I have many more servers to try it on before I'll be convinced that it's THE answer.

[tasander]

Sorry to get anyone's hopes up. It worked on the first server, but not the 2nd or 3rd. Still stuck in the same place as the rest of the people on this thread.

[lacan]

This tool works fine on some on the systems that I'm working with but it's extremely slow on other systems. I have too servers that I'm monitoring and the job is being going for over 30 hours now and none of the partitions are over 60GB. I verified all the other variables such as: Duplex/Speed settings, Switch settings, error with NICs using PERFMON and everything is fine. Something's up with this tool.

[chrislees]

I am also having this problem. I've tried P2V on WinXP Pro (two existing machines, a clean build as someone earlier suggested and W2K server). I've tried converting several W2K servers with P2V both locally and remotely. Always the same error.

I'm upset because I too have found VMWare extremely reliable in the past and this testing was the last precursor to moving our entire infrastructure over to ESX. I think we'll need to look at other alternatives... dare I even ask if anyone would recommend another vendor's P2V solution?

[lacan]

Are you using the VM converter or the old P2V. If you are using the old one try using the converter. I'm currently using the converter with some production servers and it's being working fine...slow sometimes but it works.

[chrislees]

Apologies - I should have been more explicit: I am using VMWare Converter 3.0.0 build 39557 - what OS have you had success with both as converter host and import host?

[lacan]

Well I'm using that same one..and it has worked w/ Win2k3 standard edition servers and Win2k Servers. I'm having problems w/ speed but I think I already figured what it was.

[lacan]

The one server that I haven't being able to convert is an old WinNT 4.0 SP6. They told me to verify the SP but it has SP6 on it already. I think one or two of the Win2k and Win2k3 gave me a hard time the first time but I cancelled the job and restarted the server, ran the job again and the job ran fine that time.

[JediCub]

I experienced a similar issue this weekend and found issue to be windows services related.

Check the dependencies on the Converter service in the services snap-in: services.msc. A minimum number of services are required in order for Converter to function correctly: I simply found this issue to be a matter of poor programming on VMware's part - a simple service dependency module checking for the status of relevant services would be the simple solution.

Moving along... the services to ensure are NOT disabled (and running) on the system are as follows:

\- COM+ Event System

\- MS Software Shadow Copy Provider

\- Server

\- TCP/IP NetBIOS Helper

\- Workstation

My two cents worth - keep the change.

[metroPCS_Admin]

I called VMware and opened a case as well. I was told to try converting to a standalone machine and then converting that to ESX. The conversion to a standalone machine failed with the same error. (All of my conversions are from a cold boot disk.) I was then told to try a hot conversion. I am trying that now but with little hope for success.

[mltaylo3]

I can't make any guarantees, but here's what worked for me... I was experiencing the same problems described in this forum. I believe my personal mistake was trying to run the converter without rebooting (after agent install on WinSvr2k machine). I have thus far successfully converted a Win2k3, and 2 WinSvr2k machines. So, after following these steps:

Launch regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Remove the stcp2v30 key

Remove the vstor2-p2v30 key

Remove all vmware-ufad-p2v-XXXXX keys

Remove all courier-XXXXX keys

Reboot

Under %SystemRoot%\system32, remove all vmware-ufad-p2v-XXXXX subdirectories

I finally went to add/remove programs and uninstalled vmware converter from the source machine as well. Then, using the install file I used to install the vmware converter manager (as opposed to letting the management tool do it for me), I reinstalled the agent (when installing, choose "custom install", de-select the manager, only select the agent). Worked like a charm. Good luck to you all. My e-mail is: [e-mail] if you have any questions (I honestly only browse these forums when I have a problem... selfish, but hey, I'm posting a solution now!).

[vincent_tu]

I have the same error symptom as you.

Issues: pauses at 5% for a while then jumps to 97% and then fails.

Hot P2V. objective server: Win2K SP4, with converter on my PC;

Some error logs are as follows.

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

\[2007-04-11 18:24:03.833 'P2V' 4704 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.CloneFault)

I solve by install converter (version 39557) on my VC, restart my Win2K server and then it goes all fine.

[uruiamme]

I am having this problem on a weird laptop. It runs Windows XP SP2, but it is a Macintosh laptop running bootcamp, so the partitions are in a GPT disk. The NTFS C: drive that Windows boots to is at the end of the 160 GB internal drive. I am running a program called MacDrive 7 to give me access to the Macinotsh disk as an E: drive (formatted HFS+ I think) (Or is that HFSJ?). I have about 4GB of programs installed on E and the rest is on C. Norton Ghost chokes, and now so does VMware Converter. I'm not sure why I couldn't just keep a single directory on the E: drive. The only thing that will backup successfully is plain old ntbackup, which just keeps the files and ignores that it is HFS/HFS+.

Is there a provision to just store directories such as I want to do for my E: drive?

My process failed once at 2%. I noticed that there was an error message that said that only one partition could be marked actuve. So I went to the 160GB main disk I then went into Disk Managment and selected the Macintosh formatted partition (E:) and slected "mark partition as active." This WORKED!! I was able to complete a majority of the Converter process, but now it failed at 95% like the rest of you. Along with this log (below) there was one indication that there was no hal.dll -- but that may be normal. NOTE: the majority of the C: and E: drives were backed up to a network drive, so something was working until this error.

Connecting to Software registry hive...

Loading registry hive from /\system32\config\Software

Rolling back the reconfiguration transaction...

Deleting pending files...

Writing the undo log ...

Debug

Cleaning up temp directory C:\WINDOWS\TEMP\vmware-temp\vmware-SYSTEM\sysReconfig ...

UfaSysReconfig::task::task: Image processing task has failed with MethodFault::Exception: vim.fault.NotFound UfaSysReconfig::task::task: SetState to error Remote task UfaSysReconfig::task::task completed

Waiting for updates from UfaSysReconfig::task::task Got an update from UfaSysReconfig::task::task Cleaning up remote task UfaSysReconfig::task::task

Disposing task wrapper for task UfaSysReconfig::task::task object explicitly disposed: UfaSysReconfig::task::task Debug Debug Debug Info UfaSysReconfig::task::task being destroyed

VmiReconfigTask::task step "Reconfigure VM" failed Reporting image processing task failure for task UfaSysReconfig::task::task ImageProcessingTask FAILED. Fault name: vim.fault.NotFound object explicitly disposed: computer= Cleaning up computer's child objects Unregistring volume id=virtVol={computer=,0} Unregistring volume id=virtVol={computer={7a683468e6367fe94275e2205a7645aa8e1e98a},1} Unregistring disk id=disk= VmiReconfigTask::task step "Reconfigure VM" destroyed

Reconfiguration failed

VmiReconfigTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.ReconfigFault VmiReconfigTask::task: SetState to error

object explicitly disposed: VmiReconfigTask::task VmiReconfigTask::task being destroyed

CloseSession called for session id=A73C48DC-6773-4D0B-B04E-2CD08BCDB212

Removed vmdb connection /db/connection/#4/

[ottoman4566]

Has anyone had problems doing a cold clone using the latest converter software (3.0.1 build 44840) We are doing some timing tests against a W2K3 server and are getting consistent failures with the message :

sysimage.fault.ReconfigFault

What sort of things should we be checking under the cold clone option as obviously nothing is running apart from the VMWare boot CD ?

I've enclosed the final lines from the converter log below...

\[2007-05-04 00:02:03.187 'P2V' 1064 info] \[task,274] Starting execution of a Task

\[2007-05-04 00:02:03.187 'P2V' 1064 info] \[ufaTask,191] Successfully connected to VMImporter

\[2007-05-04 00:02:03.187 'P2V' 1064 info] \[postProcessingTask,73] Calling DoReconfig

\[2007-05-04 00:02:03.187 'P2V' 1168 verbose] \[serialization,221] Archiving job to Z:\Documents and Settings\Default User\Application Data\VMware\p2v30\jobs\00000001.xml

\[2007-05-04 00:02:03.187 'P2V' 1168 verbose] \[jobManager,375] Raising event 4 for job 1

\[2007-05-04 00:02:03.265 'App' 1064 verbose] \[imageProcessingTaskWrapper,109] Successfully connected to VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.281 'App' 1064 verbose] \[imageProcessingTaskWrapper,817] Start managed object method for task VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.281 'App' 1064 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.281 'App' 1064 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.281 'App' 1168 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.296 'App' 1064 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.296 'App' 1064 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.625 'App' 1168 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.640 'App' 1064 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.640 'App' 1064 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.640 'App' 1168 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.656 'App' 1064 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:03.656 'App' 1064 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.218 'App' 1168 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.234 'App' 1064 verbose] \[imageProcessingTaskWrapper,437] Waiting for updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.234 'App' 1064 verbose] \[imageProcessingTaskWrapper,668] (Re)Start waiting for property updates from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.953 'App' 1088 verbose] \[imageProcessingTaskWrapper,749] Got an update from VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.953 'App' 1088 verbose] \[imageProcessingTaskWrapper,886] Remote task VmiReconfigTask::task\{14} completed

\[2007-05-04 00:02:04.968 'App' 1064 verbose] \[imageProcessingTaskWrapper,515] Cleaning up remote task VmiReconfigTask::task\{14}

\[2007-05-04 00:02:04.984 'App' 1064 verbose] \[imageProcessingTaskWrapper,1201] Disposing task wrapper for task VmiReconfigTask::task\{14}

\[2007-05-04 00:02:05.343 'P2V' 1064 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[task,339] Transition from InProgress to Failure requested

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[task,388] Transition succeeded

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[job,276] Job 1 changing state from 1 to 2

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[serialization,214] Serializing job 1

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[serialization,221] Archiving job to Z:\Documents and Settings\Default User\Application Data\VMware\p2v30\jobs\00000001.xml

\[2007-05-04 00:02:05.343 'P2V' 1064 verbose] \[jobManager,375] Raising event 2 for job 1

\[2007-05-04 00:02:05.359 'P2V' 1064 verbose] \[jobManager,375] Raising event 4 for job 1

\[2007-05-04 00:02:05.359 'P2V' 1064 verbose] \[jobManager,375] Raising event 6 for job 1

\[2007-05-04 00:02:05.359 'VmdbSvc' 1064 verbose] Shutting down VMDB service...

\[2007-05-04 00:02:05.359 'VmdbSvc' 1064 verbose] Unregistering callback...

\[2007-05-04 00:02:05.359 'VmdbSvc' 1064 verbose] ...done

\[2007-05-04 18:23:15.484 'ClientConnection' 1928 info] Connecting to
.\pipe\vmware-ufad-p2v30-vmdb, use SSL: true

\[2007-05-04 18:23:15.484 'ClientConnection' 1928 info] Successfully connected to
.\pipe\vmware-ufad-p2v30-vmdb

\[2007-05-04 18:23:15.484 'VmdbSvc' 1928 verbose] Connected to stream: SSL(\[class Vmacore::System::NamedPipeClientStreamWin32:022C0928])

\[2007-05-04 18:23:15.484 'BaseLibs' 1064 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2007-05-04 18:23:15.500 'ClientConnection' 1928 info] Making sure that UFAD interface has version vmware-ufad-p2v30-build-44840

\[2007-05-04 18:23:15.515 'ClientConnection' 1928 info] UFAD interface version is vmware-ufad-p2v30-build-44840

\[2007-05-04 18:23:15.546 'VmdbSvc' 1928 verbose] Shutting down VMDB service...

\[2007-05-04 18:23:15.546 'VmdbSvc' 1928 verbose] Unregistering callback...

\[2007-05-04 18:23:15.546 'VmdbSvc' 1928 verbose] ...done

Thanks

[ottoman4566]

Re: my post above. I've checked the logs further and found we are suffering from the following known issue :

Cloning fails with "Can't create undo folder" error

Cloning of some hosts, especially if they have diagnostic partitions, can fail during post-processing with "can't create undo folder" error messages at the end of the log. This occurs because boot.ini is not adjusted correctly in the destination virtual machine. You can identify this issue by looking for these lines in the logs:

\[#2] \[2006-12-08 22:43:40.468 'App' 368 warning] \[volumeMappingInfoBuilder,685] Adjusting boot.ini: Didn't find volume 2 on the disk 0

\[#2] \[2006-12-08 22:43:40.468 'App' 368 warning] \[volumeMappingInfoBuilder,685] Adjusting boot.ini: Didn't find volume 2 on the disk 0

If the virtual machine from the failed import is left behind on the destination, advanced users can work around this by:

1. Attaching the system disk to another virtual machine

2. Adjusting boot.ini manually to point to the correct partition

3. Running the Configure Virtual Machine wizard on the virtual machine

This is supposedly fixed in the latest release but we are running that and still get the same issue. We are raising a ticket against VMWare about this.

Other than the above suggestion, does anyone have any other fixes for this error ?

Thanks

[Dabestspoona]

I was failing at 97% until I ran chkdsk /f on 4 of my source machines that failed.

All were successful in converting.

[ottoman4566]

Thanks for that - we will try anything at this stage !

VMWare are sort of recognising the fact that they may not have fixed the previous known issue too.

[jpjeffery]

Just installed the new version of VMWare Converter to v3.0.1 but I'm still getting the "Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)" error. And that was with cleaning up the registry of the source machine and installing the v3.0.1 VMWare client locally to that same box.

Argh!

[ottoman4566]

Hi,

we ran our 'real' conversion this weekend using VMWare Converter 3.0 Build 44840

We successfully converted 9 systems (W2K3 and W2K) using the warm clone approach and selecting the options to build the disks at 'Minimum' size. Any databases were shutdown.

We gave up on the cold clone option due to lack of drivers, recognising RAID etc...

Everything worked fine and converted at a rate of approx. 15Gb/hr.

The only problems encountered were around remnants of earlier installed converter agents still being on the servers. These were removed and all went ok.

Must admit, after logging a call the response from VMWare was very prompt.

If you have any specific issues, please drop me a line and I'll see if I can help.

[VMfan101]

Hi, I would really appreciate if someone could help me with the issue I am seeing.

I acutally want to convert the Microsoft Virtual PC image to VMware image. The reason for this is our original project was in Evaluation copy of VPC and used pre-configured VHD. As a result, after the expiration period the VPC is rebooting every 2 hours or so. There is no way I can activate or upgrade the VPC (pre-configured evaluation copy). So, thinking to address the issue moving to VM image instead. However, i getting “P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)" error almost at the end of the convert process. Tried few recommendations in the thread like cleaning registry. But no luck. Your any help would be really really really appreciated.

I have attached log file as well; if that helps.

I am converting VPC with Windows Server 2003 to VMWare image.

[Milton21]

since the system is already a virtual machine use converter to convert a 3rd part image not a physical machine. Power of the Microsoft VM. Point converter to the VM files and this should work

[VMfan101]

Thank you for your response. I really appreciate it. I did select "Standalone Virtual machine, backup or disk image" as Source Type. Is that what you mean as well?

[Milton21]

yeah. Thats odd that it dies at 97% with an image.

[Dready]

Till now all went smooooth with converter 3, but since yesterday I got the same problems.

I'm trying to set up a test terminalserver by converting a production server (not in the farm) to a virtual machine.

And after 97% bingo - same error. Cleaning registry doesn't do the trick :smileysad:(

[arbiter]

I'm using the latest Converter (3.0.1 build 44840). W2K3 servers convert without a hitch here but when you try W2K (Professional), it's super happy fun time with "The 97%". The vmdk is allocated on the destination and cloning goes through without a problem, but when it gets to preparing the VM..

There's only one partition here, and it's not dynamic or RAIDed + the boot.ini is valid - there shouldn't really be a problem here. Converter has no trouble determining the OS version when I'm walking through the wizard and setting up the conversion. Agent has no trouble determining the OS version before starting the vmdk allocation and cloning:

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[extendedOsInfo,395] \[boot loader]

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[extendedOsInfo,395] timeout=30

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[extendedOsInfo,395] default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[extendedOsInfo,395] \[operating systems]

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[extendedOsInfo,395] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[disposable,122] object explicitly disposed: localFile=

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 info] \[attachedVolumeWin32,363] Opening host registry with path="SYSTEM"

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[disposable,69] Registering disposable session object id=hostRegistry=\{attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},1}},SYSTEM

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[disposable,80] Associating disposable session object id=hostRegistry=\{attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},1}},SYSTEM with session id=08DA89D6-B825-4671-A434-1EB2A4AF626A

\[#3] \[2007-07-25 13:31:31.802 'App' 1360 verbose] \[disposable,122] object explicitly disposed: hostRegistry=\{attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},1}},SYSTEM

\[#3] \[2007-07-25 13:31:31.812 'App' 1360 info] \[attachedVolumeWin32,363] Opening host registry with path="SOFTWARE"

\[#3] \[2007-07-25 13:31:31.812 'App' 1360 verbose] \[disposable,69] Registering disposable session object id=hostRegistry=\{attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},1}},SOFTWARE

\[#3] \[2007-07-25 13:31:31.812 'App' 1360 verbose] \[disposable,80] Associating disposable session object id=hostRegistry=\{attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},1}},SOFTWARE with session id=08DA89D6-B825-4671-A434-1EB2A4AF626A

\[#3] \[2007-07-25 13:31:31.812 'App' 1360 info] \[extendedOsInfo,758] ParseNTRegistry FOUND: Microsoft Windows 2000 root:WINNT\ SrvPack:4 SMP:0 64:0 Ver:5.0

After the allocation and cloning have finished, it tries to determine the version from the virtual volume(?):

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[extendedOsInfo,395] \[boot loader]

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[extendedOsInfo,395] timeout=30

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[extendedOsInfo,395] default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[extendedOsInfo,395] \[operating systems]

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[extendedOsInfo,395] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

\[#3] \[2007-07-25 15:27:46.190 'App' 1360 verbose] \[disposable,122] object explicitly disposed: localFile={
.\vstor2-p2v30-20942094007E00000000000004000000\boot.ini}

\[#3] \[2007-07-25 15:27:49.045 'App' 1360 verbose] \[disposable,69] Registering disposable session object id=fileRegistry=\{virtVol={computer={fd20d598a3fcc2e4c42984167c5f3fbff07c7005},0}},WINNT\system32\config\SYSTEM

\[#3] \[2007-07-25 15:27:49.045 'App' 1360 verbose] \[disposable,80] Associating disposable session object id=fileRegistry=\{virtVol={computer={fd20d598a3fcc2e4c42984167c5f3fbff07c7005},0}},WINNT\system32\config\SYSTEM with session id=08DA89D6-B825-4671-A434-1EB2A4AF626A

\[#3] \[2007-07-25 15:27:49.045 'App' 1360 verbose] \[disposable,122] object explicitly disposed: fileRegistry=\{virtVol={computer={fd20d598a3fcc2e4c42984167c5f3fbff07c7005},0}},WINNT\system32\config\SYSTEM

\[#3] \[2007-07-25 15:28:08.022 'App' 1360 info] \[extendedOsInfo,151] Getting extended OS info by parsing boot.ini and/or analyzing the registry failed

..culminating in a sysimage.fault.OsVersionNotFound exception. It looks like it fails to parse boot.ini on both ends and ends up resorting to registry; working on the source, failing on the image. Any tips?

[kingpin_ca]

In my case I solved the issue on my server. It was a drive configuration, the machine wouldn't boot after the 97% failure. I had a software mirror setup on the server, I broke the mirror, deleted the mirror drive and re ran the p2v. 100% success

[orasun]

After multiple failures, I just about gave up. Then, I tried one last time, without doing anything or making any configuration changes what so ever, it worked. Confused and... yeah, confused. :_|

[virtuosity]

This is not a good fix, but we moved the target machine to the same subnet as the esx server that is receiving the virtual machine, gave it an ip address from the new subnet and voila! It worked. It's not a good solution but indicates a firewall problem in most probability. We're still looking at that.

[BugMeNot22222]

I tried many of the recommendations in this thread, but each time the hot conversion of my Win2K Server failed at 97%. The VM obviously would not boot after the failure.

In desperation, I clicked on the VMWare Converter main screen "Configure Machine". I followed the prompts and entered the path to the failed VM. Lo and behold the configuration finished successfully and the VM now boots!

I have done some testing on the VM, and it seems to be complete.

[Donald_SBC]

I have had the same problems. Did what BugMeNot22222 did and it also worked for me. Except I got an error in the Configure Machine process. But the VM did boot. The VM was W2kPro.