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 126.96.36.199 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 email@example.com.
Always the same message (popup)
is anybody have a new idea ?
We also have this problem, but only on 1 of 2 different vCenters. Both of our vCenters are running the same version. The one that works, was upgraded from a Windows vCenter 6.0. The other was upgraded form a VSCA 6.0. A workaround until the problem is solved, is to use the Windows client connected directly to a host.
I'm am new to virtualisation and VMWare in general.
I also stumbled uppon this issue, while testing with the trial version.
I was planning on buying the "VMware vSphere Essentials Kit" for a customer of mine, but since I've stumbled uppon this issue, I'm not really sure about it anymore.
Unless,... when I do buy this can I download the "vcenter appliance 6.0" instead of the 6.5 ?
I was gonna try that, but the trial only allows me to download the 6.5
(the work around doesn't really work for me, since when I'm trying to do that the client says my esxi is controlled by a vcenter server and doesn't allow me to do it)
Would really appreciate it if someone could answer me this.
Thanks in advance.
There's now a resolution posted which is to upgrade VCSA to 6.5.0b (188.8.131.5200 Build Number 5178943).
My VCSA is now: 184.108.40.20600 Build Number 5178943
I still can't export OVF template. Message remains: "This version of vCenter Server does not support Export OVF Template using this version of vSphere Web Client. To Export OVF Template, login with version 220.127.116.11 of vSphere Web Client."
OVF is broken in vSphere 6.5
If the update to 6.5b didn't fix the issue, you can deploy the OVF manually using the OVFTool. This article has some instructions on the process. The parameters may be different, but the OVFTool should get the job done.
any resolution for this problem?
I have upgrade my Vcenter on version 6.5 update 1 5973321, but this problem still appears
because of that i can't deploy vmware vreplication appliance
Still having this issue in vCenter VCSA 6.5.0e build 5705665. Using Firefox/Flash interface since it's the only one I can find that actually works. Trying to deploy an EMC OVA file. I get this wonderfully useless message:
New KB is published with resolution.
Please follow the steps mentioned in the KB in order to correct the behavior.
I agree. I had the same problem after the latest VCSA 6.5.0-5973321 update and the solution described in KB2151085 resolved it for me.
I don't export VMs very often. Mine is downloading a vmdk file. Is that the expected result. I thought that "Exporting an OVF" would give me an OVF file and not a vmdk file.
Am I missing something?
OVF export creates multiple files. The OVF file is only a descriptor/metadata file, the .vmdk file contains the virtual disk.
In the past it was possible to export to an OVA, which is basically a single archive that contains all the required files.
Thanks for the reply Andre, but that is exactly my question.
In vCenter6.5, when I choose "Export as a OVF", when the process is done I only see a vdmk file. No OVF or OVA file, or any other files.
My question is, "Is this operating correctly?"
I have tested various possibilities and work-a-rounds of this particular issue in my VMware Enterprise vCenter Environment at work.
I am running: Version 18.104.22.16800 Build 5973321
If i use the vSphere Web Client (FLASH) I get the same error like everyone else has posted. That it's not supported on this version, blah blah blah. However, if i use the vSphere Web Client (HTML5) version, it appears to work fine but takes a long time validate the file when browsing and selecting the .OVA from local disk.
The purpose of this reply to the original post: I Hope this helps people that have the same version as me or newer that have still been experiencing this same error when doing OVF/OVA imports and so forth. I also prefer this method as it does not require any modifications or third party tools, or working around vCenter in regards to connecting to individual hosts directly, that reside within a cluster.. as you shouldn't have to for something like this.
Extra note(s): I only started investigating this issue as of yesterday afternoon. So i do apologize if my information has come late but i did read through all the existing replies and noticed that one reply even stated that HTML5 version of the vSphere Web Client does NOT support OVF/OVA import/export at all. However, on the version that I am currently running and managing (as specified above), this is definitely not the case and it is definitely supported. It is the only method that I have found and thoroughly test that is working for me to successfully upload an OVA file for an appliance via URL or Local Disk. Also, as a side note to this issue; I had not previously had any issues prior to the last upgrade that we completed across all of our blades "VMware Hosts" throughout our environment. In-fact i'm 99% certain that the original 6.5 version officially released that I upgraded us to initially from the final 6.0 version at that time, did not have ANY of these OVF/OVA import/export issues in general.
PS: I will also check and review the latest VMware KB / Articles that have been released to see what is stated officially as of current date vs. what I have stated above in regards to this "bug". Since it does work for me in the HTML5 version but NOT the Flash version, i'm actually beginning to think that it may just be another step towards them phasing out the older "original" Flash based Web Client.. I wouldn't be surprised. It would be definitely be premature though (In my opinion at least) since there are still a lot of features missing or unsupported in the HTML5 based version of the vSphere Web Client. So, after I have done my due diligence by completing the necessary remaining research, I will then post an update here if I do find out anything else that would be helpful for anyone at all. I also have the capabilities to spin up test environments of any of the available versions at any given time, which may be helpful in this particular scenario. We'll see what i run into before I elaborate any further on this.
Sorry for the long winded post everyone. I wanted to keep it informative but straight to the point. However, my first draft was not near thorough enough for me.
FYI - The most important information is at the top, prior to any "Notes, Extra Info, PS, etc".
Attachments: The first two images are showing the Version and Error message directly within my vSphere Web Client (Flash Version). The second two images are showing the Version and the OVF/OVA Import dialog display successfully and Error free from directly within my vSphere Web Client (HTML5 Version).
Kevin C. Brown
Systems Engineer II