Looks like the database table NuGetPackageSymbols got corrupted somehow. After restoring it started working as expected.

Surfing Pikachu, That was one of the steps I mentioned in my original post. Did not work for this issue. Alana, Already attached Fiddler before original post. Just showed 404's for symbol requests. Downloading the package locally allows the symbols to be found; but using ProGet's symbol server doesn't work.

I think its now implemented: https://inedo.com/proget/versions 5.0.9

Thanks for the quick reply! Ok, that's a shame but understood.

The default PDB format for the project files was changed from Full to Portable (see https://github.com/dotnet/core/blob/master/Documentation/diagnostics/portable_pdb.md). The portable format is not compatible with the symbol server. To switch back to the old format just add this to a property group in the *.csproj file: <DebugType>Full</DebugType>. You can also override this with /p:DebugType=Full in your build command. Also make sure that the nuget packages are created with --include-symbols --include-source

Hi Team, Thanks for all your support. I was clearing the temp cache for symbol server. Cleaning up a nuget cache fixes the problem for me. Thanks.

Unfortunately Visual Studio doesn't support authenticated symbol servers; i.e. if ProGet sends a 401 response, there is no authentication challenge. We may be adding a feature in 4.7 that allows for "url authentication" of sorts, where you use a "obscured" url with an api key in it somewhere that will cause authentication to be effectively bypassed.

Here is an example path to a .pdb file, the same folder contains .dll: C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\lib\dnx451\JA.AppCentral.Logging.pdb Package folder also contains the source in C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\src folder

This was a regression in 4.1.2, but it is fixed now in 4.1.3.

Unfortunately symbols/source can be a little complicated to set up and debug; please review the various resources on the symbols tag, such as the tutorial and questions.

This is by design; symbols work quite weirdly for native packages, and don't follow consistent conventions like .NET packages. So, we can't arbitrarily strip all .pdb files (we only remove them from the /lib path). In this case, we suggest to make a separate symbols feed.

There have been a few modifications since the version you're running to the symbol/source server that will likely fix the behavior you're experiencing. There is one issue in particular that involved reverse sorting of the symbol file's age value that I believe is related. When you upgrade to the latest, it should resolve the issues.

Unfortunately the behavior of Visual Studio's Debugging/Symbol Serving can be a bit strange; there's not much we can do to control that... however if you carefully follow the tutorial, it should help you get set up!

Wow, great find :) This will be addressed in the next maintenance version.

This is unfortunately not trivial to debug, and will require understanding/learning how the symbol/source serving work (and the arcane tools to inspect said files), since it could be any number of things at this point, from your local pdb cache to improperly build pdb files. But take a look at some of the other Q&A posts with symbols tag, specifically this one which shows how to use pdbstr.exe to inspect. If you find out specifically what the issue was, please do share it.

I see, while that works for some projects, not all of our projects uses a build server which complicates the process of deployment. Thanks

I've got it working now, but only with the port. I'd rather not have to do that, but it will work for now. I'd really like to know why I can't use a reverse proxy in front of ProGet to avoid needing to specify port numbers.

There's nothing special that ProGet is doing, it's effectively just inserting a SRCSRV stream into the pdb, exactly as pdbstr would. I'd also check out #3061, and specifically http://techblog.dorogin.com/2012/09/troubleshooting-debug-symbols-indexing.html

The SRCSRV stream for downloaded PDBs was always empty. Once I added that stream ProGet correctly updated it to point at itself. I never saw errors on the /administration page of ProGet. Is there somewhere else to look? I'd like to be able to skip the local indexing step if possible.