OVA deployment - "Transfer failed: The OVF descriptor is not available"

[jorge_c]

Hello,

I am having a problem when trying to deploy an OVA file. The message "Transfer failed: The OVF descriptor is not available" is displayed. Any suggestions? Much appreciated.

[daphnissov]

First suggestion is to provide much more information. What version of vCenter? What client are you using? What OVA are you using?

[jorge_c]

Hello Daphnissov,

Thank you for suggestions. Here is the information.

VMware vCenter Server Appliance 6.5

Server: VMware ESXi, 6.0.0

I am using the webclient

Regarding the OVA, I tried multiple OVAs, and all of them have the same problem.

Regards,

Jorge

[daphnissov]

Usually I've seen this caused by the download being corrupted, so check to make sure the ones you're trying are all good downloads. May need to reference the MD5 if available. If you're on U1, check this and make sure the fix is applied, although the symptom is different:  OVF deployment fails after upgrading to vCenter Server Appliance 6.5 U1 (2151085) | VMware KB

[jorge_c]

daphnissovI have re-downloaded and checked the MD5. Regarding U1, I am not sure where to check that. I apologize, but I am a beginner in VMware. I will research though. Any suggestion is welcome.

Thank you.

[daphnissov]

What is the build of your vCenter?

[jorge_c]

The build is of the vCenter is 5973321. The version is 6.5.0

[daphnissov]

So it's Update 1. You need to apply that fix in the KB I referenced.

[jorge_c]

Daphnissov:

Thank you. If I follow you correctly, I will apply the corrections on:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151085

Regards.

[jorge_c]

I followed the directions of the link:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151085

However, the file ts-config.properties.rpmnew is not in the system I am working with (this file is referred to in the above link).

Attached is a screenshot of the two files I have in the directory indicated in the link.

[StoreThomas]

Hi

Just adding my two bits as I was having the same problem running vcenter 6.5 U1.

Couldn't fint the rpmnew files either so I just restarted the content-library service (service-control --stop vmware-content-library;service-control --start vmware-content-library) without making any other changes and that solved my problem, hope it helps you too.

Best

Thomas

[jorge_c]

Thank you, Thomas.

[rpas2915]

Thanks,worked for me!

[AvayaVMSU]

AWESOME!!!  Simply amazing.  Thanks for the suggestion, @StoreThomas!

[btsoh]

Hello,

Also works with vCenter 7.0.3.

Thank you.

Bertrand

[Avinash Savaliya]

Hi

Just adding my bits here.

I was facing same error message with chrome browser..I switched to firefox and installation was fine.

[jorge_c]

Thanks!

[MikeOD]

I found this thread when searching for a solution for the same issue when trying to deploy VROps.  Based on the comments in the thread, I tried using IE (I had been using Chrome).  The OVA deployed OK.

[AvayaVMSU]

I had this problem with Chrome, so I tried FF.  It worked!  Then something else went wrong and I had to re-deploy.  This time FF had the problem.  I tried with IE and it worked.  IDK, but I hope I don't have to try again.  Maybe Opera - is that still a thing?

[Alonso Trejo Mora]

Spent hours on this and the browser was most definitely the problem. Google Chrome installs failed and Firefox came to the rescue.

[tinkeredthinker]

Surprisingly, Firefox worked like a charm. Thanks

[Mandeeeps468]

I was also facing same error message with chrome browser and then switched to firefox.

Thanks  

[Sasha_G]

I've got exact same versions and resolved same issue by opening console via proper FQDN that's been given to vcenter during setup. You need to install the cert then and all will work.

FYI: if you run this in Flash version, it'll give you a bit more info and exact URL to open for which you have to install the certificate.

[toomasm]

For me the the solution was to deploy ova to esx6.5. I tried first deploying from vSphere 6.5 web client to host running esx 5.5 and it failed with this error. Changing  the host resolved the issue.

[abhishekkunal51]

>> I am also facing same issue on

>> And when I tried to follow the KB I am unable to find rpmnew file:

>> I am using this environment for NSX deployment where the initial step is to deploy the controller from NSX Manager---> VC -----> ESXi.

>> I have updated all my ESXi to 6.5

>> Restarted the content-library still the issue ...

[RussellFaraday]

Hmm.  Me too. 

Downloaded the VDP appliance ova multiple different times.  Didn't help.

Different browsers didn't help.

Fiddled around with ovftool, but that never could make a good ova again.

What did finally work is on the VMware downloads page, don't click the regular download link "Download Now" but instead use the smaller link "Download Manager".  This fires up a special downloader web page.  The appliance ova I got by doing that worked first time, no problems.

I guess I really was getting mangled ovas when using the regular link.

Cheers!

[shvedalexey]

Try it on Firefox 56 - it helped me. On all other versions of Firefox, Chrome and IE there was the same error as you.

[RNAR]

vSphere 6.5 latest patches (I think). I too was able to get it to work by just changing over to Firefox (v. 65.0.2).

Once again, a web browser makes for a pretty crappy operating system. Down with web apps!

[aartik1]

It is 2024 now and the same issue still persists with the latest Edge, Chrome.

Ultimately firefox(latest version) helped me to solve this error. Thanks.

[afragop]

Hello all,

I faced the same issue when I tried to deploy the ova using web client though Chrome.

By using Firefox, I had no issue and the ova deployed successfully.

Thx

Tasos

[ThepHuck]

I ran into the same issue.  Fresh deployment of VCSA 6.5, tried deploying the vROps OVA using Chrome and received the "OVF descriptor is not available" error.

I restarted the content library via SSH to the VCSA:

service-control --stop vmware-content-library

service-control --start vmware-content-library

Tried again, still in Chrome (logged out, logged back in) and OVA deploy worked fine.

[dashoward]

I too had the same issue.  I'm pretty sure know what the cause was as well. I began to deploy an OVF completed the process then deleted the VM.  Immediately upon deleting the VM I tried to recreate with a different OVF but with the same exact descriptor and received the error "OVF descriptor is not available". This was probably due to the fact that the library hadn't cleared the old descriptor from under my username. I read through all of the threads and the vExpert: Luke Huckaba final suggestion was the only one I tried and also successful the first attempt.

I logged off and logged back on and my OVF deployed immediately with the same descriptor as before. no problems at all. Also I was using Firefox as my browser the entire time.

[smccreadie]

This solution posted by ThePhuck was a big help.  I am using VCSA 6.7 U3 and had the same "OVF descriptor is not available" error.  I restarted the VCSA, same issue.

I ran the commands to restart the content-library service and that solved it.

Thanks for the help.

[Pascal Hanke]

We had the issue when we tried to deploy an OVA using Chrome when Web Client connected against the vCenter DNS alias name. After using the vCenter FQDN, the OVA deployment worked fine.

(N.b.: A colleague of mine suspected some certificate issue. Since Firefox has its own certificate store, this might be why IE and Chrome behave the same. I haven't tried to verify by using another browser, yet).

[AlanKass1701]

Thank you, this worked for me!

[ace56]

I am going to be honestly brutal here. I have had nothing but issues with vSphere 6.,5 things like VDP and vROPS. I can see why v6.7 came about so quickly. I am literally pulling my hair out with so many issues experienced, some as easy as deploying an OVA! VMWARE Support is also less than average as well in my opinion and not very helpful. It's almost as if they are not even trained up.

[petemb]

Fresh install, 6.5u2 VCSA - was able to deploy an NSX Edge Client OVF using the HTML5 UI client in Chrome without issues. Had the same issue trying in Flash client in Chrome.

[MartinWest]

Hi

I had the same issue.

In my case it was the time difference from my System to the VCSA.

As the time was the same on all Systems, the deployment runs without any problems.

Hope this help somebody!

Best regards

Martin

[aabdulrahman0]

Using the HTML5 client worked for me. I had been trying to deploy NSX for over a week using the Flash page. I tried with Chrome only.

[PeteLong]

Ive seen this happen on 6.5 and 6.7 each time Ive simply redeployed to a HOST and not the cluster, and its worked fine.

VMware: The OVF Descriptor is Not Available

Pete

[Kevin wenqiang66]

I have the same problem, and i have solved it by redeploying it,selecting a specific host(if fails,try another host)

[iSamNC]

This issue drove me nuts for weeks.  Kept getting Transfer failed: The OVF descriptor is not available. I can deploy fine from the host through the ESXi GUI but not VSphere: HTML5 nor Flash.  Tried FF, Safari, Chrome.  Finally got around to upgrading vSphere appliance and ESXi to latest and greatest 6.5 thinking that might fix it but no.  Checked that the FQDN is resolvable, etc.  Still couldn't get it to work.  Then I read in this thread someone tried IE and that solved it.  I really didn't think this was browser related but I fired up an old Windows 7 VM in Fusion and tried it in IE 11 and voila - worked fine.  It hurts my head that I have to use a 3,000 year old browser to deploy and OVF from vSphere.. but whatever.  Wanted to add this here.

[iSamNC]

Update.  IE worked.  One time.  The very next time I tried to deploy an OVF from the same system with the same browser during the same session if failed.

[Jesus Machado Gonzalez]

in my case I checked everything proposed here, tried the html5 client and it worked.

[omidkosari]

My solution

In Firefox > Options > Privacy & Security > Certificates > View Certificates > Import

Then browse to the directory which contains .ovf and .cert files in my case "vSphere_Replication_OVF10.cert"

After importing the vSphere_Replication_OVF10.cert in to firefox certificates, everything works fine

[Pontificus]

1/14/2023:  I had this same problem.  The solution for me was to assign the VM to the ESXi HOST and not the datacenter or cluster.  It imported correctly then.  In this case, I had a cluster of only one host (Horizon 8, installed via VCenter).  Probably logging directly into the ESXi web interface would have done the same thing.

[DGR_MKeeton]

Late to the party but interestingly as of latest OVF attempt Firefox failed first time around (Transfer failed: The OVF descriptor is not available") and Edge worked fine. To be fair I didn't try closing browser, reauthenticating nor using private window. Either way for people looking at this issue, the first easy checks are to ensure you are logged in and authenticated to vCenter in the web browser followed by trying a different web browser. That is as long as vCenter and ESXi host certs are trusted on the particular computer attempting to upload from.

[Senthil Kumar Chettiar]

when we faced this issue, we disabled proxy in the browser and the deployment got completed.

[RichardKenyan]

It is 2024, and this is still an issue...just adding to the pile as I found this as the first search engine hit:

Edge - Version 122.0.2365.92 (Official build) (64-bit) - failed

Swapped to Firefox - 123.0.1 (64-bit) - worked fine

no other changes other than switching a browser.

[zacdee]

Nov 2024 - Similar workaround to others here.
filehash was correct

tried different browsers

once I put browser into Private\InCognito OVA deployed successfully.

[Wilson Sour]

Thank you, this work for me, but i have another issue with login, can't login to the root user or ping the management ip.