Loading Symbols from Symbol Feed Results in 404

[Steve Davison]

I found ProGet while looking to set up a symbol server for our internal packages and the product looks like exactly what we're looking for. While testing the installation, however, I've run into an issue I just can't resolve on my own. Specifically, requests to load the symbols within a Visual Studio 2013 debug session are returning a 404 error (file not found). Here's some background on our setup:

Two feeds defined, "Default" serves the "real" packages and "Symbols" serves the symbols packages.

Package downloads work fine through the web interface and NuGet Package Manager for both feeds.

The "Symbols" feed shows that symbols are included and clicking on the "Download package with symbols" link works (URL is http://cpunuget/api/v2/package/Symbols/CPU.CISAPI/1.1.27.0?includeSymbols=y) and the downloaded package includes both the .pdb and the source files.

I've configured my Visual Studio settings to point the Options->Debugging->Symbols to the URL http://cpunuget/symbols/Symbols

When running a debug session on a console application that references the package, I'm unable to step into the package source code. I installed Fiddler to see what traffic was occurring and when I force Visual Studio to load the symbol information through the Modules window, the URL requested is http://cpunuget/symbols/Symbols/CPU.CISAPI.pdb/5E358192FAF24731B3E4D1AA33E299C61/CPU.CISAPI.pdb but a 404 is returned, so Visual Studio reports that the symbols can't be found.

Any ideas?

Product: ProGet
Version: 3.2.0

[Tod]

It sounds like everything is configured correctly on the ProGet side. Can you verify that you have:

• "Enable source server support" checked
• "Enable Just My Code" unchecked
• "Automatically load symbols for 'All modules, unless excluded'" checked

Note that if you have multiple instances of Visual Studio open, it may overwrite your settings once they are closed.

Also, not sure if this package is proprietary or not, but would you be able to email us the package to support@inedo.com to see if it works on our test machines?

[Steve Davison]

I believe I have the settings correct. Here are some screenshots:

I've mailed one of the symbols packages to support@inedo.com.

Thanks for the prompt response!

[Hassan]

What was the resolution to this? I'm having a similar problem and would like to know how to fix it.

[Jim D.]

I'm having this exact same issue as well. ProGet 3.8.6 on IIS. Looking at the IIS logs, all calls to /symbols/<feed> return a 404.

[Alana]

Make sure to very carefully follow the tutorial/docs; symbol/source serving is a brittle, 20+ year old technology that’s been implemented on the NuGet side with separate symbol/source packages. There are a lot of things that can go wrong here (from not generating symbols correctly in the first place, to network/firewall filters), and none are easy to debug.

The 404s you are seeing are expected for packages that aren’t in ProGet (like the mscorlib, etc).

[Steve]

In my case, I was generating the "real" packages in Release build configuration but generating the symbol packages in Debug build configuration. Once I realized the symbol server wouldn't respond correctly when the build configuration differs between the packages, I published the symbol packages in Release build configuration so the packages matched and everything started working correctly. Hope this helps someone else in this same situation!