cannot convert server with esx5 converter?

Tpm1973
Tpm1973 used Ask the Experts™
on
hello,

i have a vm where i have installed esx5 standalone converter...
one nic is in the VLAN where the physical host for migration is located
one nic is in the VLAN where vcenter is located....

i start the converter, the agent will be installed on the remote physical server,
then i chose the settings which i want to migrate, destination host, datastore...
and then if i press "start" i get always the following error:

a general system error occured: unknown internal error

???

thx!
Error.doc
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
can you communicate between physical server and vCenter Server or ESX server?

eg ping

Author

Commented:
the physical server can communicate to a esx-host, but NOT to the vcenter...
the vcenter is on a separate VLAN; so i have configured on a esx-host a seccond vmkernal in
the VLAN where the physical machine is located...
this VLAN is not available on the vcenter at the moment...

but: with the converter i can chose only the vcenter for "destination" there i cannot chose the
esx-host for destination... i don't know why?

so is it necessary that the physical machine can communicate direkt with the vcenter?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
if you are using vSphere Hypervisor 5.0 ESXi 5.0 and vCenter 5.0, you must convert physical to vCenter Server.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Commented:
vcenter is the controller so it must be done that way

Author

Commented:
so... i have now the problem that NO!! direct migration from pyhsical server (win2003, and win2008r2) is working....
sometimes i get a error "unknown internal error" if i click on FINISH before the migration starts,,,,

sometimes the migration starts i can see that the VM is created on vcenter, i can also see the files (.vmx, a vmdk file) on the datastore and some minutes later i get again:

"unknown internal error" and the job ends...

so????

i tried now to convert the pyhsical server to a .vmdk file (vmware workstation)
and then from this .vmdk file direkt to vcenter...
the job is still running so it seems that this is working...

is this a bug? or what could be the problem...

it's really strange...

thx,
martin
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
have you installed the app on server to be converted?

Author

Commented:
yes, also with this the same situation...
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
when does this error occur at what percentage?

also review the converter logs

Commented:
sounds like a intermittant network outage issue

Author

Commented:
but why is it then working if the destination first is a
.vmdk file (vmware workstation)

it's only not working when the convert is direct from physical host to vcenter...
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
vCenter issue or network comms between physical and vCenter

is this v5 of converter?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
upload the logs here, see if anything is obvious

Author

Commented:
no direct solution found....
a work around was to convert the physical maschine to vmware workstation, and in a seccond step convert from vmware workstation format to vcenter....

Author

Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Tpm1973's comment #a38699509

for the following reason:

workaround found; no solution for the problem found

Commented:
that does not sound correct vmware converter can do a p2v
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
there is a known bug with VMware Converter converting into ESXi 5.x.

Author

Commented:
ok, and exist there any update or fix or official workarround?
thx!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
VMware have issued a later version of VMware Converter 5.0.1, released on the 25 October 2012. (this was after you question logged in March 2012!).

Not sure if you've tried this recent version.

other workarounds exist, in using converter 4.3.
Commented:
the solution is: the VM must have network access (ping) to a mgmt NIC from at least one HOST.... so the VM with the vmware converter gui must have network access to SERVER which will be migrated and to the VCENTER, and the SERVER which will be migrated needs access to the esx host as the "convert-stream" will be sent direkt to/via the esx host.

Author

Commented:
tested with different customers - always OK

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial