Solved

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

Posted on 2012-09-16
10
8,911 Views
Last Modified: 2012-09-18
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!
0
Comment
Question by:NAMEWITHELD12
  • 5
  • 5
10 Comments
 
LVL 119
ID: 38403271
0
 
LVL 1

Author Comment

by:NAMEWITHELD12
ID: 38403337
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
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 38403367
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 1

Author Comment

by:NAMEWITHELD12
ID: 38403442
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
 
LVL 119

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 38403451
with the number of ESXi 5.1 bugs, flooding in at present, I would not recommend, an upgrade at present.....
0
 
LVL 1

Author Comment

by:NAMEWITHELD12
ID: 38403462
Ok...this was a fresh install, new player in the VMware game myself :)  What latest version is suggested?
0
 
LVL 119

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 38403501
5.0 Build 768111

5.1 is a little fresh, only released last week!
0
 
LVL 1

Author Comment

by:NAMEWITHELD12
ID: 38403505
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
 
LVL 1

Author Closing Comment

by:NAMEWITHELD12
ID: 38409251
Version 5.0 ESXi coupled with the 5.0 converter did the trick!
0
 
LVL 119
ID: 38409271
Yes, ESXi 5.1 has a few issues!
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question