Corrupt Packages when restoring

Hi,

We have Proget installed as a Nuget Cache for external packages. I am getting this weird error when restoring through the command line as part of our build process (e.g. nuget.exe restore oursolution.sln -source "http://proget.mycompany.com:81/feeds/external" -NoCache"), I get the error "Unable to read package from path 'EntityFramework.6.1.1.nupkg'".

When I try to open the downloaded package with 7Zip, I get an error saying the package is not an archive. What I found is that if I download the package through the GUI of our Proget instance it works and when I compare it to the file downloaded via the command line, there is a size difference. For example, package 'EntityFramework.6.1.1.nupkg' is 4,135 KB when downloaded via the GUI and 4,129 KB when downloaded via the command line. So there is a difference of 6 KB. I can't open the corrupt package to see what's missing.

Proget is running behind IIS and I am on the latest version. I get the same error for several packages. Can't see what I am doing wrong, any suggestions?

Thanks,
Milan

Product: ProGet
Version: 3.5.6

I don't think you're doing anything wrong, but based on this, and your previous error... it sounds like you've got some server/network oddities. That could be any one of a THOUSAND things, but it's definitely not ProGet nor the NuGet clients.

So, I'd suggest to put some wireshark or fiddler monitoring in between to see exactly what's happening, where they are coming from, and what the actual responses are.