Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

ProGet Symbol server - 404 Error



  • Hello

    I am running ProGet 2.1.4.

    I have a feed named "default". The feed is configured to enable symbol/source server. When I browse into the URL that proget specifies as the symbol server URL, I get a "Request handler not found (404)" error with following details:

    /symbols/default does not map to any handlers...



  • Followup question:

    I understood from http://inedo.com/support/questions/891 that the symbol server url is not browsable. However, when I configure VS.NET to use this URL, I can see at fiddler that VS is requesting an internal url inside "/symbols/default", but the request times out after about a minute.
    I tried setting up a new feed and uploaded a single package to it using the ProGet web UI, and then everything worked just fine. However when using the symbol server on my existing feed, the symbol request always results in a timeout.



  • Hi David,

    The "404" is expected (we'll add a message in a future verson of ProGet), but the timeout is not.

    How large are your packages?

    Alex



  • The package is small, also when I create a new feed where the same package is the only package, it works fine.



  • An update: I finally solved this problem. Apparently we had another package (not related) in the feed which contained a 18 mb pdb file (slimdx.pdb). We had about 10 versions of this package. I removed all versions but the last one, and then the timeout was gone.

    However, this is only a workaround, because ProGet server is stuck on the big package for a really long time (or forever?) when requesting a symbol. It locks the handle of the file and does not release it until I restart the ProGet service.



  • Thanks for the update; we do have a work item (PG-130) for improving indexing of .pdb/source on large packages. This will come in a future version, hopefully soon.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation