@nraynaud Thanks for the reply. Yes, I figured it out and the import seems to be running now! Thanks

@nraynaud I see you have fixed the bug. How do I implement this? Do I have to rebuild XO from sources again? Also, thanks for fixing it.

@nraynaud I tried that, it didn't work

I am uploading the .ovf file
W2K12Full.ovf.txt

@nraynaud OK, I've just woken up and read your message. Based on the message I am going to add the following information that now seems relevant. This VM, prior to being exported had a disk removed but not deleted from disk. My guess, and of course, it's only a guess, is that the file is listed in the XML file as part of the VM but in reality isn't there because the file was deleted.

I am going to remove the file from the directory and save it somewhere else and then re-export it and see if it works.

But now I will repeat my little mantra that I used to lecture people with as a software developer for decades. Make your error messages meaningful. Had this error message said "Hard disk 2 listed in inventory but file not found" I am guessing it would have triggered a memory in me or anyone else. My favorite pet peeve is the error message "File was not found". That means nothing; the message 'File abc.docx not found in directory C:\somedirectory" is a lot more meaningful.

I'll report back on the success or otherwise of my test.

I am having an identical problem. The error message is the same as stated right at the start. It is made up of English words but makes no sense at all.

I have the appliance with latest stable and I have also built the latest available from sources and both fail identically.

I have previously imported another VM from ESXi 5.5 without problem. This .ova is just about 50 GB.

Maybe, just as a clue, someone could tell me, or us, what the error message is actually complaining about. I live in Texas so I am familiar with grain silos, but I don't recall ever having heard of a grain directory, and I certainly would have given it 8 had I known what it was looking for.