Can create Content Library, but can't use it

[Rsasjol]

Hi,

After an upgrade from 6.0 to 6.5, and 6.7 (VSphere hosts and VCenter), I'm unable to use Content Libraries.

I'm able to create one, either on local datastores or NFS remote storages. But when I try to display information, I end up with a result like this :

Right now, I'm even able to upload an OVA in the Content Library without error. Unfortunately, as you can imagine, freshly uploaded template remains unable.

What I've tried :

• Use either HTML5 or Flex interface. Same symptom.
• Looked at KB2151085 details. Unfortunately, my content-library service is up and running, and I don't have "ts-config.properties.rpmnew" file.
• Tried as administrator@vsphere.local. Same behaviour.

Any ideas ?

Thanks for your help,

[Rsasjol]

A quick update after one month :

Problem is still there, but it is VCenter fault somewhere.

Even if the name is set to "null" in HTML5 interface, I'm able to upload files to a NFS4 remote content library.

But in either "Templates" or "Other" tab, there is no evidence of my newly uploaded file.

Thanks again for your help/

[JWilliamson]

I'm currently dealing with the same issue, on two vCenters.  Did you ever find a resolution?

[not2sure]

We are experiencing a very similar issue on one of our vCenter servers. Has anyone found a workaround or a fix yet?

Thanks in advance!