VMWARE converter 5.1 crashes and 4.1 errors out with "invalid fault"

I am attempting to convert a 2008 R2 to a VM ,

the converter 5.1 will crash when i attempt to log in so i installed 4.1 and get the invalid fault error

where can i get more info from logs on this issue

this happends with all 4 servers that i am attempting to convert!
LVL 1
NAMEWITHELD12Asked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Found dangling SSL error:  is in most conversion logs, this is not the issue.


At present there are some issues with converter and ESXi 5.1.

Have you installed Converter on the machine to be converted, and are you sending the conversion to the ESXi host or vCenter server?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
NAMEWITHELD12Author Commented:
Here's a bit more info...

Physical server info: 4 servers are running Windows 2008 R2 SP1, 1 test workstation, Windows 7 Pro SP1

when using 5.0 converter (on both physical platforms):
- after I enter the IP, username, and password for the ESXi 5.1 intended host, I get "Converter Standalone appliation has stopped working", the problem details are:
Prob Event Name: appcrash
App name: converter.exe
App version: 8.0.0.11006
Fault Module Name: converter-logic.dll
Exception code: c0000005

when using 4.3 converter (on both physical platforms):
- I get all the way through specifying all the details of the physical system, no red Xs on any of the options, all seems well...then I click finish and I get "invalid fault".  The converter log has these details:

[ADS] GetTokenInformation failed: 1312
[04836 error 'App'] Found dangling SSL error: [0]

I've added local host entries for the intended host ESXi 5.1 system, and the firewall is off on the physical system I'm trying to convert.

I'd prefer to make the latest version of converter work with the latest version of ESXi, but not having any luck :(
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
NAMEWITHELD12Author Commented:
The converter is installed on the machines to be converted -- at present, I have no issues downgrading the host from 5.1 to an earlier version that's known good, if that's the next step?  It's not really hosting anything at the moment...
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
with the number of ESXi 5.1 bugs, flooding in at present, I would not recommend, an upgrade at present.....
0
 
NAMEWITHELD12Author Commented:
Ok...this was a fresh install, new player in the VMware game myself :)  What latest version is suggested?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
5.0 Build 768111

5.1 is a little fresh, only released last week!
0
 
NAMEWITHELD12Author Commented:
we tryied it both ways installing the vm converter on the source servers and on the same server that is running vcenter

it still fails it looks like we are going to have to try to downgrade the eSXi 5.1 to 5.0


thanks for all the help !
0
 
NAMEWITHELD12Author Commented:
Version 5.0 ESXi coupled with the 5.0 converter did the trick!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, ESXi 5.1 has a few issues!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.