Issue reading nuget package

matt's Avatar


16 Oct, 2014 11:25 PM

Most nuget packages are successfully restored at the start of the build, however the build continually fails downloading the 2 largest packages. these are 14mb and 7mb respectively.

The error message reads
........ \.nuget\NuGet.targets(98,9): error : Unable to read package from path ....

I've checked our private nuget server logs and the files are correctly served, and a local build runs without issue.

Any thoughts on why this fails on the build server.


  1. Support Staff 1 Posted by Feodor Fitsner on 16 Oct, 2014 11:31 PM

    Feodor Fitsner's Avatar

    Have it worked before?


  2. 2 Posted by matt on 16 Oct, 2014 11:39 PM

    matt's Avatar

    No I've not managed to run a successful build through appveyor yet.

    Other packages are successfully pulled from the same feed, and a local build with packages restored from the same feed works without issue, so there seems to be something unusual occurring


  3. Support Staff 3 Posted by Feodor Fitsner on 17 Oct, 2014 12:21 AM

    Feodor Fitsner's Avatar

    OK, could you send me a full part of the build log where nuget restore occurs?

  4. 4 Posted by matt on 17 Oct, 2014 02:35 PM

    matt's Avatar

    Hi Feodor , thanks for your prompt replies. I've found a problem in the feed since then. I'd been trying to package a couple of Telerik dlls we use. For some reason these fail to package up correctly. The local build had in fact been using a cached version. I've moved the required dlls to a sub folder instead for now, as I don't seem to be able to generate a valid package, very odd!

  5. Support Staff 5 Posted by Feodor Fitsner on 17 Oct, 2014 04:36 PM

    Feodor Fitsner's Avatar

    OK, thanks for the update!

  6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:49 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac