The virtual disk references in rel_apimgmt.ovf match the filenames of the VMDK files. I don't know the details of the OVF format well enough to spot any mistakes, and a quick look at the VirtualBox sources didn't show me how the file extension could get lost on the way to the error message.
It seems that I cannot help you further. You could create a ticket in the Bugtracker, though.
VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension
Re: VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension
hi All,
Any updates to proceed ahead ?
Any updates to proceed ahead ?
Re: VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension
hi All,
Thanks to all for your replies.
Finally, I was able to resolved this issue by following a quick workaround as to selecting the 2 disk image entries in the GUI and add an extension manually. After that the import should work just fine.
It was a bit silly workaround but no other choice as if now.
I will be closing this post now
Thanks
Sanchit Gupta
Thanks to all for your replies.
Finally, I was able to resolved this issue by following a quick workaround as to selecting the 2 disk image entries in the GUI and add an extension manually. After that the import should work just fine.
It was a bit silly workaround but no other choice as if now.
I will be closing this post now
Thanks
Sanchit Gupta