Error: Unable to remove the destination virtual machine

[gfdos]

Using VMware vCenter Converter Standalone 5.0

Converting W2k3 32-bit from physical hardware (running machine) to ESXi 4.0.1 Host

failed at 91% complete

7:27:29 AM Completed cloning

7:27:31 AM Creating a snapshot of the source system

7:27:44 AM A snapshot of the source system was created successfully

7:27:44 AM Error: Unable to remove the destination virtual machine 'server.domain.com_2k3'

(note: 'server.domain.com'  is substituted for the real name of my server)

I have tryed booting the resulting vm, and it won't boot (not to say the "cloning" isn't complete, but the resulting vm is not working....)

Q1: What does this error message mean? (Why would it try to remove the destination vm -- isn't the whole point of the conversion to MAKE a destination vm?!)

Q2: What can I do to prevent this as I'm trying to replace this physical machine with the resulting vm?

[Rosen Tomov]

Please upload log bundle for investigation.

[patanassov]

Q1: If a cloning fails, converter deletes the destination VM in order to avoid garbage (it assumes this VM is unusable anyway). It doesn't delete it if only the configuration fails. So in your case the cloning has probably failed.

Q2: As POCEH said, please upload the logs. Go to the failed task (not job) and export from there so that the worker log is also present in the package.

Regards,

Plamen

[gfdos]

Attached are the diagnostic logs....

Looking at the error "FAILED: The session is not authenticated"

http://communities.vmware.com/message/1182712#1182712

I did notice that the time was off on that ESXi server --> it thought the convert started at 5:30am (it was actually 11:19am),

and at about 6:05am, I added NTP servers, and it updated the time to correct -- DURRING the convert.

I'm restarting the convert now while waiting for responses on this, as the last convert took 20 hours and 8 min before it failed.

[patanassov]

It looks like the cloning has finished successfully the first time. Can you try to run just a reconfigure on the target VM?

I suppose you have restarted converter services (both server and worker) based on the discussion you mention.

HTH

Plamen

[gfdos]

I saved the "failed" vm as a backup of sorts.

How would I run a "reconfigure" on it for academic reasons? (Once the new conversion I've started is complete.)

I actually rebooted the machine running the Converter software, and shut down the other vms on the ESXi server and did a reboot....

so I suppose that counts for restarting the converter services?.... The server I'm imaging, I didn't restart.... probably should have... we will see.

[patanassov]

Run converter and select 'Configure machine' button. You don't need to wait the new conversion, reconfiguration affects only the destination VM.

And yes, rebooting the machine with converter server is more than enough.