It means there's something wrong with the VMDK. You'd have to find out what that is and fix it.
Usually this happens with multipart variants of VMDK when you don't have all the parts. It could also mean a corrupted header, or the file isn't a VMDK at all, despite the extension.
See if you can do an MD5 checksum comparison on the file set.
yes, normally I use MD5 comparison for other activities but, unfortunately, it's not clear to me how to use it (MD5) in this contest.
What's the string to compare?
I can't tell you that without knowing how the file set was distributed. Usually it's as installer, or an archive. Either way it's possible for the originator to provide md5 checksums of the files which you can compare against the checksum of your downloaded copy.
Since you are using a VMDK, and it is corrupted, I'm assuming that an OVA/OVF or similar download or USB stick transfer is involved somehow. Either way you have working state A, and communications medium leading to non working state B. Compare the checksums of A and B (pre installation).