(404) Not Found.

Oct 31, 2011 at 7:08 PM

So we've setup an internal package server a while ago and have been happily using the server for a while with many packages.  Over the weekend we've creted a new package and have deployed it to the server and tried referencing the project but we are getting "The remote server returned an error: (404) Not Found." error.  All of our other packages are still working without any issues, I've even updated older packages and they still work.

I'm wondering if there are any ways to help diagnose the problem? 

I've used fiddler and have gotten the following for the package:

GET http://wpgbuild02:8090/download/ASSEMBLY-NAME/ HTTP/1.1
User-Agent: NuGet Add Package Dialog/1.5.20902.9026 (Microsoft Windows NT 6.1.7600.0)
Host: wpgbuild02:8090
Connection: Close

HTTP/1.1 404 Not Found
Content-Type: text/html
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Mon, 31 Oct 2011 18:02:37 GMT
Connection: close
Content-Length: 1245

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>404 - File or directory not found.</title>
<style type="text/css">
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF;
#content{margin:0 0 0 2%;position:relative;}
<div id="header"><h1>Server Error</h1></div>
<div id="content">
 <div class="content-container"><fieldset>
  <h2>404 - File or directory not found.</h2>
  <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>

Any ideas?

Oct 31, 2011 at 7:25 PM

One thing to check: Make sure the case of package name on the url matches the case of the package file on disk.

Oct 31, 2011 at 7:48 PM

Just checked they do match.  FYI we are packing the nupkg via the csproj file.

Oct 31, 2011 at 7:57 PM

if you enter http://wpgbuild02:8090/download/ASSEMBLY-NAME/ into your browser, does it download the package?

Oct 31, 2011 at 8:02 PM

Nope same issue.


404 - File or directory not found.

The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Oct 31, 2011 at 8:04 PM

It looks like this is not the NuGet client issue. What are the urls of the other packages? Try debugging the server.

Nov 1, 2011 at 3:20 PM

I've updated our local nuget server to use the newest nuget.server components with no luck.  Though with local dev nuget server, before I published to our IIS server, it looks like it can host the package but not our IIS server. Odd.

FYI all of our other custom packages are still working, before and after the update.