VMware Cloud Community
jeffoutwest
Contributor
Contributor

Unable to obtain hardware information for the selected server

VMware vCenter Converter Standalone Client / 4.0.1 build-161434

ESX server / 4.0 update 1

Wizard fails to select a Windows Server 2008 R2 64 bit guest VM with the following error:

Unable to obtain hardware information for the selected server

The guest OS is powered of and the selected source type is VMware Infrastructure virtual machine, VMware tools is installed on the guest.

Below are the relevant snips from the log.

Converted works with other Windows Server 2008 R2 64 bit guest VM's.

Any advice would be appreciated. Thanks, -Jeff

===================

Connecting to server on pipeName
.\pipe\vmware-converter-server-soap.

SSL:false

Path:/converter/sdk

VMODL version:converter.version.version1

NOT using SSL to connect to VMOMI server
.\pipe\vmware-converter-server-soap

Getting ServiceInstance contents

Yes, we connected to Converter Server.

Logging in to Converter Server (Using Impersonate).

Converter Server session established. (Session ID = "9CCCD0A1-2644-4C68-BA35-972BD19AD927")

SourceSelectPluginModel::BuildFilter 3rd party type microsoftVirtualPCVM not found

SourceSelectPluginModel::BuildFilter 3rd party type parallelsVM not found

SourceSelectPluginModel::BuildFilter 3rd party type vmwareVCBBackup not found

SourceSelectPluginModel::BuildFilter 3rd party type livestateBackup not found

SourceSelectPluginModel::BuildFilter 3rd party type shadowProtectBackup not found

SourceSelectPluginModel::BuildFilter 3rd party type acronisBackup not found

SourceSelectPluginModel::BuildFilter 3rd party type vmwareVM not found

SourceSelectPluginModel::BuildThirdpartyHostedExtVector 3rd party type vmwareVM not found

Logging out of the Converter Server. (Session ID = "9CCCD0A1-2644-4C68-BA35-972BD19AD927")

Connecting to server on pipeName
.\pipe\vmware-converter-server-soap.

SSL:false

Path:/converter/sdk

VMODL version:converter.version.version1

0 Kudos
5 Replies
moniquevmb
Contributor
Contributor

You could try changing the machine type of the source machine to windows 7 64b, this worked for me.

You have to remember to change it back afterwards

0 Kudos
continuum
Immortal
Immortal

Win 7 - 64bit works ? - interesting and unexpected.

I would have set it to 2008 64bit




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

jeffoutwest
Contributor
Contributor

Nope, changing the setting to Win 7 - 64bit porduced the same error

0 Kudos
moniquevmb
Contributor
Contributor

@continuum; yes you are right, that's what I meant to say, and what I did with my machine, I know I should have gone to bed...

Also I had to change the network adapter after the conversion, back to E1000. Don't remenber if that was a setting in the wizard. And ...my machine was a v4, not a v7

0 Kudos
jeffoutwest
Contributor
Contributor

My best guess to the root cause was moving from a 64 bit server to a 32 bit server.

Did not have any issues moving 32 bit VM's. Thanks all. -Jeff

0 Kudos