did you try to distribute this package again?
Can you check if your hard disk, the disk controller and the RAM is ok?
Since the files are packaged using ZIP you can try to open the package with Windows Explorer or other tools. If they also report a CRC error it might be a hardware problem.
You also can try to zip some folders on this server diretcly and check the files.
This can work if all users are getting the error on execution, because there is a problem with the depot files. But what if only one machine is getting the error, while other machines are installing fine from the same depot? What is the procedure to get that machine to re-download the package to its repository cache and try executing again with fresh package files?
We have the same problem. And we use 2016.2 R2 with Windows 10 1703 at the moment. In our case we have it even on a Hyper-V server!!
Any resolution to this issue? I'm having the same problem as described above by wandclecrk.
did you try to delete all the folders in
C:\Program Files (x86)\Common Files\enteo\RepositoryCache
which have just a number as name?
The packages will be downloaded again. If the problem occurs with several packages on this machine also try to check if there is a problem with the network configuration on this machine, i.e. two network interfaces in the same ip address range. And please do a hardware check on the client.
With a Hyper-V server: is this a DSM server or is it a client?
the message tells you that there is a CRC error. If this happens on only one machine, the package is currupted on this machine only. It is as simple as that.
We have seen issues in the past where one package couldn't be installed in one site while worked in all other sites. Reason was - at least in one case - that antivuris marked one of the files in the package as "suspicious". This caused the files timstamp to be altered and the chscksum to become invalid.
I assume, same thing could happen on a single computer.
Beside this, as Nils mentioned before, other possible reasons are hardware / harddisk issues.
Before being able to delete files in the repository cache on the client you might have to stop the DSM services.