VMware Cloud Community
kjs00333
Enthusiast
Enthusiast
Jump to solution

An error occurred while opening a virtual disk. Verify that the converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts

Hello,

I am having an issue when trying to configure a VM from VMware converter 5.5.  I start up the software, and select the option to "configure machine". Source type is VMware infrastructure virtual machine, then I put in my server info and admin credentials. 

I am now shown my inventory that I have in Vcenter, however.. when I select a powered off VM (doesn't matter which host the VM is on) and click next, I am presented with the error of:

An error occurred while opening a virtual disk. Verify that the converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts


I am able to telnet to all my esxi hosts on port 902 and 443. I am also able to ping them by name from the converter server and from the vcenter server.  I am banging my head against a wall on this one..  Does anyone have any insight on this? Perhaps there is a file that needs to be configured within VMware converter to allow this to work?  There are no firewalls that should be getting in the way here.


Thanks for taking the time to assist.



1 Solution

Accepted Solutions
POCEH
VMware Employee
VMware Employee
Jump to solution

Ok, your problem is: when you add ESX to VC you don't accept its thumbprint.

Re-attach your ESX and accept its thumbprint, this will solve your problem.

Cheers

View solution in original post

11 Replies
POCEH
VMware Employee
VMware Employee
Jump to solution

Try to run Converter UI 'as administrator'.

HTH

Reply
0 Kudos
kjs00333
Enthusiast
Enthusiast
Jump to solution

Same error.

An error occurred while opening a virtual disk. Verify that the converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Could you upload log bundle?

Reply
0 Kudos
kjs00333
Enthusiast
Enthusiast
Jump to solution

Sure. Attached.

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Ok, your problem is: when you add ESX to VC you don't accept its thumbprint.

Re-attach your ESX and accept its thumbprint, this will solve your problem.

Cheers

kjs00333
Enthusiast
Enthusiast
Jump to solution

Thanks for figuring that out!  Only problem is I'm not sure what you mean Smiley Happy  how is something like that done?

*EDIT*  - Found it on the view window in Vcenter - view / administration / server settings / SSL

I selected the "verified" box at the top to apply to all the hosts and it now works.

Thank you very much!!!

POCEH
VMware Employee
VMware Employee
Jump to solution

When adding ESX host to VC there is a thumbprint shown, you must accept it.

How you can simply disconnect ESX host from VC and then connect ESX host again to the VC, accepting its thumbprint.

ErikCarlseen
Contributor
Contributor
Jump to solution

We had a similar problem (same message) with doing some conversions - it turned out that the system being converted was unable to resolve DNS queries because we were doing system maintenance on other servers.

basten3
Contributor
Contributor
Jump to solution

Thank you Erik.

Now it works. I had to configure dns fine to resolve ESX name.

dalexiev
Enthusiast
Enthusiast
Jump to solution

Adding destination network DNS resolved the issue in my case. Initially I only had IP and SM on the source server. This is an isolated server which in order to p2v I connect the secondary directly to the vCenter vlan. Got the error, read your post, added DNS on the secondary source adapter, works now. Thank you!

oussamaghanem
Contributor
Contributor
Jump to solution

Thank you ,problem solved by fixing DNS settings

worked successfully

Reply
0 Kudos