The OVF package is invalid and cannot be deployed. The following manifest file entry (line 1) is invalid: SHA256 (xxxxxxx.ova.

[boubou]

Hi,
When I try to deploy the ova on my vCenter, I got this error message.
vCenter 5.5u3.

The OVF package is invalid and cannot be deployed. The following manifest file entry (line 1) is invalid: SHA256 (xxxxxxx.ova.

[boubou]

It will be appreciate if you can release an ova in vSphere 5.5.
I think it will be compatible with all version!

[enoch85]

Hmm, that's strange since it's made with ESXi 5.5 compatibility.

The OVA is exported in Workstation 12, but maybe only the VMDK is compatible. Could you please try to extract the OVA manually, and then import the VMDK?

Thanks!

[enoch85]

@sboulianne Did it work?

[enoch85]

Made a new release. Try that one instead.

Closing due to inactivity and new release. Please reopen if the issue persist.

[boubou]

Hi again,
Im sorry to tell you I redownloaded the ova and I tried to deploy it BUT I have the same issue.

Do you have a workaround for that issue ?

[boubou]

The OVA is exported in Workstation 12, but maybe only the VMDK is compatible. Could you please try to extract the OVA manually, and then import the VMDK?

I just saw your post, I will try!

[IPCaptain]

I had the same problem. I also tried to import the VMDKs but didn't succeed.
Searching the web, I found that the root cause seems to be the SHA256 hashing algorithm. See: this KB from VMware.
@boubou: To solve the problem convert the OVA from SHA256 to SHA1 as described in the link.

Anyway: @enoch85: Thanks for your work and providing this great VM!

[enoch85]

@IPCaptain Thanks for investigating!

[iyushaw]

I am facing similar issue

[enoch85]

Just an update here, we will remove ESXi 5.5 compatibility all together, as it's EOL anyway. Please see linked issue.

[mamama1]

Actually I just saw this - the problem is, that current OVA exports (like the current ovatool versions and more recent VMware workstation releases) create a SHA256 signature whereas vSphere 5.5 does only support SHA1 signatures.

The solution to this is to extract the OVA file with a zip program (it is nothing more than a zip archive with OVA ending) and then delete the .mf (manifest) file.

Apart from that, one really should move away from vSphere 5.5 as that's unsupported for a very long time now and even vSphere 6.7 is approaching its EOL slowly but steadily. Even vSphere 6.0 is out of support.