Instalation fails on simple.cab file issue

[Hadron]

My colleague gets following error on installation of EA client:

The cabinet file 'simple.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

He tried on 3 different computers, tried disabling firewall, running as administrator, redownload installation source, and other options however the result is always the same. He tried versions 13 and 15. Others do not seem to have this sort of problem at all.

Is there any solution for this problem? Thank you.

[Geert Bellekens]

Is he trying to install if from a google drive or something similar?

Let him try to first copy the msi to C:\Temp and then run it from there.

Geert

[Hadron]

Thank you for your reaction.

He is not using any tool of that sort. Just plain double click on .msi file from the File Explorer, without any embedded stuff or any funcionality which could involve GDrive, DropBox, OneDrive or simillar tools. Not even installed.

The installation attempt from C:\Temp provided the same error.

[Geert Bellekens]

Thank you for your reaction.

He is not using any tool of that sort. Just plain double click on .msi file from the File Explorer, without any embedded stuff or any funcionality which could involve GDrive, DropBox, OneDrive or simillar tools. Not even installed.

The installation attempt from C:\Temp provided the same error.

All out of idea's then. Never had issues with the EA installer before.

Geert

[Uffe]

Has he somehow got the downloader into text mode rather than binary?
That will corrupt the contents of a package without it being obvious.

/Uffe

[Hadron]

This is something that puzzled me as well. Could his download be corrupted? We both downloaded same file from Windows Network Share (like \\server\share). We compared byte count via Properties of the file, it did match. But still, I got through installation and he got the error. Really strange.

[Uffe]

Byte count is not a sufficient check, especially in Windows where byte counts are approximate at best. Beyond Compare is a better bet.

This kind of issue is precisely why file repositories usually have checksums associated with the various downloads so you can verify them after transfer. Not sure if Sparx provides that.

/U

[Hadron]

You nailed it Mr. Uffe Such obvious thing.

We tried simple windows tool like>

Code: [Select]

certutil -hashfile "Enterprise Architect 15_1 Build 1528.msi" SHA512and it proven difference. Redownload another way was followed by successful installation 

Thanks to all. Issue can be closed.

[Geert Bellekens]

You nailed it Mr. Uffe Such obvious thing.

We tried simple windows tool like>

Code: [Select]

certutil -hashfile "Enterprise Architect 15_1 Build 1528.msi" SHA512and it proven difference. Redownload another way was followed by successful installation 

Thanks to all. Issue can be closed.

Wow, I would have never guessed that. I don't think I've ever had a corrupt download of anything (except for napster/kazaa/bittorrent type of situations, only for legal content offcourse )

Geert

[Uffe]

Wow, I would have never guessed that. I don't think I've ever had a corrupt download of anything (except for napster/kazaa/bittorrent type of situations, only for legal content offcourse )

Well, to clarify: this was not an issue with the download from Sparx, but something that went wrong (oddly consistently) on the LAN. But yes, file transfers can and do go wrong.

Incidentally, torrent technology can be quite useful on a corporate network, especially if you often need to distribute large numbers of small files. It significantly outperforms SMB.

Mind you, carrier pigeons significantly outperform SMB.

/U

[Geert Bellekens]

Mind you, carrier pigeons significantly outperform SMB.

True! Funny Story:

Back in the day we (in Brussels Belgium) had a customer in Bordeaux (France) that had a issue with a virus and had to reformat their whole server. (yes, no backups!)
When they wanted to re-install our software they discovered that they had misplaced the original CD.

The software was about 250 MB, and we tried uploading it to their server with the model connection we used to do remote support. The upload started and was calculated to take about three days (if we didn't have any disconnects).
We finally had to send someone on the TGV from our office in Lyon with a copy of the CD to help them out.
If only we had a carrier pigeon back then 

Geert

[qwerty]

Someone of the regular posters here was spoofed by visiting http instead of https.

q.