@Dan_Woolf Sounds good, thanks for the response.

Apologies, I had seen the StackOverflow post first, so I responded here: https://stackoverflow.com/questions/56338757/proget-symbols-and-source-server-download-pdb-correctly-but-source-not-found/56397293#56397293

I found my mistake I had to specify the "Feed API user" in the API Key configuration.

We can't reproduce this; a more likely scenario is that the nuspec in question has an invalid item and is causing an otherwise unknown and unexpected error We would need to full nuspec and the reproduction instructions to better investigate.

The SQL server and the application are both on server 'Production' and the application is successfully retrieving data from the SQL server. The connection string used in the application configuration is the same connection string being used in the SQL connection in Buildmaster. It is using a SQL account, so not integrated. Here is a redacted connection string: - Data Source=*************;Initial Catalog=*************;User Id=*************;Password=*************;MultipleActiveResultSets=true;

I'm sorry but I'm not understanding what you mean by "queues" or "hangfire"...

Could this be related to Quirks mode? https://inedo.com/support/documentation/proget/feeds/nuget#legacy

Hello Steven, Try visiting this page in a browser: http://<ProGet hostname>/feeds/<feed name>/NuGet.Frameworks/4.7.0-rtm.5148 There should be an error message like this: The version number provided is invalid, but would be valid if this NuGet feed were migrated to SemVer2. You can migrate a legacy NuGet feed to SemVer2 by clicking the button at the top of the feed management page.

This error message is coming from the NuGet client, and it's regrading your server's SSL configuration. Unfortunately I don't have enough information about your server or network configuration to tell you how to begin troubleshooting, but if you search that error, you can find lots of tips on how to ensure you have certificates set-up properly, etc.

The sales team does not check posts on this forum. Please use the ProGet Quote Request form for quote inquiries: https://inedo.com/proget/pricing/request-quote

Hello, these errors are quite erare, but it can happen in dealing with randomly disconnecting web clients. The easiest thing to do is to set automatic recovery on the service. You can do this on the "Recovery" tab. You could also upgrade to iIS, which mas more transparent crash recovery.

The error is "failed with: 401 Unauthorized", so it probably means you need to specify an authentication source? We didn't change the way authentication is handled in v5, so it's likely unrelated to the upgrade.

Thank you, I was not aware of this. Seems to work

Alana, thank you for the update. I guess we can consider this closed until such time as we know otherwise.

Hi, please see: https://inedo.com/support/kb/1072/proget-vs-nugetserver

Changing the name during a promotion can't be done, primarily because that's the key that identifies which packages are promoted. Would it be feasible to create another package with the same contents and non-pre-release name in the Dev Feed, then promote that?

I'm afraid not; it's a generic crash error message. We really need specific ways to reproduce it to help identify what problem is.

Thank you for reporting that, we had scheduled to do a maintenance release v1.7.3 today and were able to get a fix in for it - should be available before the end of the day.

Support for portable PDBs is currently an "open issue", and our initial research found that metadata information was undocumented, however since then it has been: https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md Unfortunately at this time we don't have a timetable for if or when this gets implemented, but it is on our list.