Task failed: P2VError FILE_OPEN_FAILED

[sonicsw]

Hello Guys, me again

today my task was to convert a real Server to a VM through my VC.

My VC is a Virtual machine and the only one inside the old Network (within the clients)

and my ESX/SAN (iscsi) network.

The Server i like to convert has no direct connection to the esx and the storage, only over the VC.

Everytime i try to import, at 2% the converter stops and destroys my import .

Must my ESX have a direct connection to the Server I would like to import or is it enough that the VC can see them both?

Must be the Port 902 open (read this in another thread)? Coz if i do an telnet localhost (VC) 902 nothing answers...

Plz help me have to move 14 Server over now...

#1] 2008-01-17 17:29:36.843 'Sysimage' 836 info Connecting to host vc on port 443 using protocol https

2008-01-17 17:29:36.843 'BaseLibs' 836 warning SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vc

2008-01-17 17:29:36.843 'BaseLibs' 836 warning SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

* The host name used for the connection does not match the subject name on the host certificate

* A certificate in the host's chain is based on an untrusted root.

2008-01-17 17:29:36.843 'BaseLibs' 836 warning SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

2008-01-17 17:29:36.859 'Sysimage' 836 info Authenticating extension com.vmware.converter

2008-01-17 17:29:36.859 'Sysimage' 836 info Logged in!

2008-01-17 17:29:36.859 'Sysimage' 836 info ImpersonateUser user Administrator

2008-01-17 17:29:36.875 'Sysimage' 836 info Impersonated user!

2008-01-17 17:29:36.921 'P2V' 836 info Adding job 13

2008-01-17 17:29:36.937 'P2V' 836 info Starting job 13

2008-01-17 17:29:36.937 'P2V' 3284 info Starting execution of a Task

2008-01-17 17:29:36.937 'P2V' 3284 info Connecting to IPC$ on 192.148.100.15 as eis_egufer\administrator

2008-01-17 17:29:36.937 'P2V' 3284 info Successfully connected to IPC$ on 192.148.100.15

2008-01-17 17:29:36.937 'ClientConnection' 3284 info Connecting to
192.148.100.15\pipe\vmware-converter-vmdb, use SSL: true

2008-01-17 17:29:36.953 'ClientConnection' 3284 info Successfully connected to
192.148.100.15\pipe\vmware-converter-vmdb

2008-01-17 17:29:37.015 'VcTaskBase' 756 error Update task progress failed on task-151 with exception: vim.fault.InvalidState

2008-01-17 17:29:37.046 'BaseLibs' 3052 warning Unsetting unknown path: /vmomi/

2008-01-17 17:29:37.062 'ClientConnection' 3284 info Making sure that UFAD interface has version vmware-converter-4.0.0

2008-01-17 17:29:37.078 'ClientConnection' 3284 info UFAD interface version is vmware-converter-4.0.0

2008-01-17 17:29:37.093 'P2V' 3284 info Task execution completed

2008-01-17 17:29:37.125 'P2V' 3284 info DoImport called

2008-01-17 17:29:37.125 'P2V' 3284 info Starting execution of a Task

2008-01-17 17:29:37.125 'P2V' 3284 info Successfully connected to VMImporter

2008-01-17 17:30:18.859 'P2V' 3284 error Task failed: P2VError FILE_OPEN_FAILED(vpxa-nfc://[Datacore Mirror] Mumms_1/Mumms_1.vmdk@172.17.10.21:902!52 22 b2 87 b6 13 c3 79-a7 f4 79 4f c6 87 aa 31)

Thx much

Sonic

[sonicsw]

edit:

now i added as well an service console to the nic into the network where the server is i like to imprt.

I can ping and open from the client the port 902 on the ESX, but my import still fails....

[sonicsw]

addition to my post 2,

when i convert vom the host 2 the esx straid it works!

if i convert from the host 2 the vc fail:

08:51:34 PM Step 1 : Connecting to VMware Converter Agent on localhost

08:51:34 PM Step 2 : Creating target virtual machine and importing data

08:51:39 PM Configuring parameters for the target virtual machine...

08:51:42 PM Creating target virtual machine...

08:52:16 PM ERROR: Unable to open file %s

[snapper_]

I am using 2.5.0 update 1. Did you get solution to import problem?

I also see following in my logs: Task failed P2VError FILE_OPEN_FAILED vpxa-nfc://

[IamTHEvilONE]

If you convert to VirtualCenter ... there are more ports used for a successful conversion. I would suggest to send the servers to the ESX hosts directly since it's working already.

This is a copy/paste from a previous post:

This is a generic guide and all may not apply - for instance if you are not using VirtualCenter, there is no need to test the connection between ESX and VC.

Check basic network

• ping from source system to VC host

• ping from VC to ESX target system

• ping from source system to ESX target system

• ping from ESX target system to VC host

• ping from ESX target to source system

Check the port usage (use telnet to verify)

• Converter application to remote physical machine - 445 and 139

• Converter application to VirtualCenter Server - 443

• Converter application to ESX Server 3.x - 443

• Physical machine to VirtualCenter Server - 443

• Physical machine to ESX Server 3.x - 443 and 902

• If you are using Converter 3.0.x, make sure you do not have a web server using port 443 while running Converter

Check credentials and privileges

• Ensure that each username can login to all systems (you may want to create one admin account on all systems to simply the testing)

• Ensure the user has permission to create a VM on the target system

• Ensure the user has access to LUNs on the target system

• Ensure the user has write privilege on target system storage devices

• Verify that the user can create a new VM on each target system from VirtualCenter

Your Virtual Centcer user (if applicable) needs the following privileges:

• Allow ReadOnly

• Disk Access

• Allow Virtual

• Machine Files

• Download

• Inventory of VMs

Verify space requirements

• Check available file space on all systems (Depending on your method you will either need space equal to the selected drive or to the space used on the source drive.)

• Verify that the Target VMname does not exist on target system

• Optionally, turn firewall off on 3.0.x ESX servers

Source: http://www.vmware.com/pdf/VMware_Converter_manual303.pdf

[IamTHEvilONE]

I had seen something like this a little while ago, and can be related to bad DNS resolution. not a guarantee as the the reason why ESX works and VC fails, but just something I had passed over.

[pablo_picasso]

I ran into this issue and it had to do with my dns server. Whoever set the machine up that I was using put in 162.x.x.x instead of 161.x.x.x.

[grndmstr]

i had the same problem, it turned out to be a firewall issue

the source machine could contact the VC and vice versa, but source could not contact the destination ESX node.once i resolved that, the P2V worked perfectly.

[pnewell]

I had a lot of issues trying to cold-clone a server to VC too.

First, I tried to just use a DHCP address (but specified the DNS and WINS servers) and clone it to the VC server, but that would fail at about 2%.

Eventually I deiced to try it directly to an ESX host, which worked correctly. Now the thing about my setup - my 'normal' LAN is on a 10.10.x.x/16 network, but the ESX hosts are on a 192.168.x.x/24 network. We have a policy setup in our gateway/firewall that will route specific IP addresses on the normal LAN to contact the ESX LAN. With that in mind, if I specified one of those IPs in the networking setup portion of the Cold-Clone wizard, I was golden.

Are your ESX hosts on your 'main' LAN or on their own private segment?

The other odd thing I found out was that if you are attempting to clone to an ESX host (or VC server, I'd suppose) you need to be using standard ASCII characters for pretty much EVERYTHING; ESX host names, vm names and descriptions,etc. If you have anything with a non-standard characters (umlauts, symbols, etc) might cause the conversion to fail.

[darren_siegel]

DNS resolution errors will cause this. Adding the target ESX server to the to-be-converted machine's local host file fixed the issue.

Using the local host file is admittedly a workaround; i stll need to look into why DNS failed in the first place.