VMware Cloud Community
SpiritDean
Contributor
Contributor
Jump to solution

VMware Converter Failed at 2% : ERROR: Unable to open file %s

I am trying to convet a winnt system into esx, always fail at setp2. I tired to convet locally and remotely and get the same error message. Please help

10:32:00 AM Step 1 : Connecting to VMware Converter Agent on 172.19.129.10

10:32:00 AM Step 2 : Creating target virtual machine and converting data

10:32:05 AM Configuring parameters for the target virtual machine...

10:32:07 AM Creating target virtual machine...

10:33:04 AM ERROR: Unable to open file %s

The Log has been attached

0 Kudos
1 Solution

Accepted Solutions
IamTHEvilONE
Immortal
Immortal
Jump to solution

is this caused by that the TCP port 443 is blocked?

nope

More than likely, the source system (172.19.129.10) cannot reach the ESX host by DNS or TCP Port 902 is blocked between them.

ha-nfc://\[storage2] Corcus/Corcus.vmdk@172.19.129.32:902



Regards,

EvilOne

VMware vExpert 2009

5441_5441.jpg

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

View solution in original post

0 Kudos
5 Replies
SpiritDean
Contributor
Contributor
Jump to solution

is this caused by that the TCP port 443 is blocked?

0 Kudos
TobiasKracht
Expert
Expert
Jump to solution

check this article http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1006607&sl...

StarWind Software R&D

StarWind Software R&D http://www.starwindsoftware.com
0 Kudos
IamTHEvilONE
Immortal
Immortal
Jump to solution

is this caused by that the TCP port 443 is blocked?

nope

More than likely, the source system (172.19.129.10) cannot reach the ESX host by DNS or TCP Port 902 is blocked between them.

ha-nfc://\[storage2] Corcus/Corcus.vmdk@172.19.129.32:902



Regards,

EvilOne

VMware vExpert 2009

5441_5441.jpg

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

0 Kudos
SpiritDean
Contributor
Contributor
Jump to solution

Sir, I have checked on the TCP port 902 on the source machine by using telnet 172.19.129.32 902, it seems that the TCP 902 is open. I have upload the screen copy of the telnet result.

By the way, what do you meaning by "cannot reach the ESX host by DNS", since I typed the IP address of the ESX host in the conveter, will it also require DNS to solve the address

0 Kudos
SpiritDean
Contributor
Contributor
Jump to solution

Thanks, actually I have already read the document and test the TCP port 902 on the source machine before I created this discussion.

0 Kudos