I migrated my VCSA from 6.0 to 6.5 and now and i have a strange message when i try to deploy an OVA : This version of vcenter server does not support Deploy OVF template using this version of vsphere web client.To deploy OVF template, login with version 220.127.116.11 of vsphere web client.
Of course i already use a 6.5 version like i am connected to vCenter 6.5.
I tryed to to remove stored data, clear cache, change brower, remove CIP 5.5 et 6.0, reboot VCSA and finely change PC.
I tryed with root and firstname.lastname@example.org.
Always the same message (popup)
is anybody have a new idea ?
I implemented this "work-a-round" today in my environment and it did in-fact fix the problem. This is by no means a true fix though. This has to do with the migrated file not having or using the original file name because it appends a different extension to it. VMware will have to fix this actual issue in the next release.
However, I didn't find or see any downside to implementing this work around to fix the problem. I definitely recommend it for the fix currently.
I tried KB2151085 and I am also running vCenter Version 18.104.22.16800 Build 5973321. I even opened a ticket with VMWare to get some resolution. Their ultimate answer was to export the OVF from the actual host. This was fine by me, if it was going to work.
Upon trying that, I got about 16.2GB into a 18GB download and it would fail, reporting Network error.
I finally resorted the the OVFTool. The syntax was confusing and didn't look like it was giving me the options I needed. I finally found a page with a better example of the tool syntax.
I installed it on my vRanger server and ran:
C:\Program Files\VMWare\VMWareOVF Tool> ovftool "vi://root@<password>@<IP of VM host>:443\<VM server folder>" "H:\OVF\<VM server name>.ova"
This seems to have worked for me.
This (KB2151085) didn't work for me. After performing the steps, I got a bunch of messages that said 'An error occurred while starting the service' multiple times, but with nothing useful. My vCenter has been upgraded form 6.0, to 6.5, to 6.5U1. The OVF deployment functionality worked before I upgraded to 6.5U1.
It's basically acting like the 'ts-config.properties' file isn't even there - for grins, I deleted it and tried to start the service and got the same exact message. Coped the ts-config.properties.rpmnew.orig to ts-config.properties and tried to start the service, same thing again. Deleted the 'new' ts-config.properties and copied the original backup to ts-config.properties and same message.
Tried to deploy it using the HTML5 client and it seemed to start to work, but failed before I got to the deploy page. Now that the service it broken, it is greyed out int he HTML5 client.
When I tried to deploy it directly to a host, I got:
'Failed - Access to resource settings on the host is restricted to the server that is managing it:'
Not good that this is broken...
I got it fixed and was able to upload the OVA - I don't know why it didn't work the first time, but copying the files changed the permission of the destination file, so the service couldn't use the file. I removed the ts-config.properties file, copied the ts-config.properties.rpmnew.orig file to ts-config.properties, fixed the permissions and it was able to start, and after a browser refresh, I was able to start uploading the OVA, but now it's failing for other random reasons. One time it complained the 'OVF Descriptor was not available', one time it complained that the checksum didn't match for one of the VMDKs, and then 'Invalid Response Code:500'.
Never had these issues before 'upgrading' to 6.5U1, and certainly not before 'upgrading' to 6.5 and losing the C# client. The Web client sucks so bad.
1. Install trusted root CA certificates - KB - 2147256 - VMware Knowledge Base
2. For this error "The OVF descriptor is not available", apply this KB - 2151085 - VMware Knowledge Base
3. Use full FQDN of your vCenter Like - https://vcenter.vmware.com/vsphere-client/
Use above three steps and issue will get resolved
I tried all these steps and working for me and it should worked for others too but may require some more troubleshooting.
I just had this problem trying to deploy an ova. In Chrome it failed with the same error. In Firefox, it succeeded with no errors.
vCenter : 6.5 (Build 751524)
ESXi: 6.5 (Build 7388607)
for real with firefox?
in my case I've been trying to export some VMs as OVF and won't work all
it's stuck a 33%, last time I tried and I leave the task running, 16 hours later still at 33% no matter chrome, firefox, flash o html 5
I have this OVF issue with my vCenter.
I run vCenter 6.5.0 build 8024368 that seems to me above the VMware vCenter Server 6.5 Update 1d (build 7312210), so it should contains the resolution for the issue.
But maybe I'm wrong.
So please advise me if my analysis is correct.
Thanks in advance for the help.
I had the same issue this week. It was the first time attempting it so I can't say it ever worked before. However, the virtual appliance installed was a fresh install and not an upgrade.
I upgraded the virtual appliance two from version 22.214.171.12400 to version 126.96.36.19900. The issue did not go away. It actually seemed to get a little worse. It went from starting the ova export and getting stuck at 25% to not starting the download at all. It led me to believe it might be the browser. I added an exclusion for Java in chrome for the virtual appliance URL. Tried it again and to my surprise, it worked. The actual .ova file was the first thing to download. Prior to that, it was a tiny vmdk. This time I ended up with four files. and ovf a vmdk for each disk and a .mf file.
Now I guess I need to import it to test.
My problem to deploy an OVF was due to the size of the OVF (more then 10 Go).
Using IE 11 to connect to the vCenter and then start Deploy the OVF but if failed with the "...invalid parameter" error.
I have found some articles related to a limitation of file size that IE can handle for such action.
With Firefox, I have no more the issue.
I hope this help.
this is a long running thread that will probably attract attention of many people struggling with OVF/OVA import/export with vSphere.
As a workaround I want to point anyone to a free Java based GUI tool that will get every job related to OVF/OVA done for you quickly and without the need to struggle with the oddities of the vSphere Web Client:
It's the VMDeployer tool created by stevejin
You can download it from here after a free registration: DoubleCloud Inc - Integrated Search and Automation @ Cloud Scale
In my case I had the following service stopped state
service-control --status vmware-content-library
Restarted service and refreshed browser and it is working fine now. And I can deploy OVF file and that option is not grayed out anymore.