Hello Rickard, This is PG-1212 and will be fixed in ProGet 5.0.9.

I like it, good idea. I've put in a feature request for it, PG-1213 - so if it's possible to do it easily and in a mainteance release well do it! Stay tuned.

Were on it! THe issue is that it's the "new" symbol format. The feature is PG-1054 and we will ship it in a maintenance release soon :)

Alana, I tested the change and it is working for me with version 5.0.8. Ship it! :)

Ok got this working by removing the api key in the feed properties, thanks!

One common way to do this in BuildMaster v4 is to use two pipelines; a "blue" and a "green" pipeline. Another thing is to have a "Blue" and a "Green" environment, and then a pipeline like: Int > Test > Blue > Green Then, basically skip Blue or Green depending on the workflow. You can also have operation groups / action groups with predicates like "if $BlueGreen = Blue". You can certainly use the Set-Release operation (or ACtion in v4) to set configuration variables on a release.

If you go to the "Packages" page, you can see packages in ProGet. The feed view will always aggregate your connectors; so if you don't want to see the aggregated (remote) packages, you'll need to disassociate the connectors with the feed.

Looks like this was answered here: https://inedo.com/support/questions/8233 5.0.8 fixes the issue.

Because of a reinstall of proget with an existing database the package paths were resetted to default. After fixing the paths, the error went away. The error should be more descriptive when the files can't be found on file store.

In the post you linked, the problem was the host operating system (Ubuntu 14.04). So you should upgrade to 16.04.2 LTS. If it's not working, then you'll likely need to explore the docker script, and step into the container to see what specifically is the issue.

Thanks for posting an update! Anecdotally, this used to happen to us "all the time" when rebooting a hypervisor server (i.e. server hosting multiple VMs) because the host/hypervisor server didn't have enough resources to give to each booting virtual machine, and SQL Server couldn't start due to low start-up resources (memory, etc). We've mostly corrected this by staggering start times and increasing VM hardware.

Hi Tod Thanks for the fast response. Since i am not relying on the statistics of Proget i have solved the issue with a bit of work. Created new feed that uses new standards setup custom feedpath and droppackage path for bulk import on the server i located that packages on the filesystem and dumped into the appropiate bulk import folder. wait a minute or two and the new feed has all the packages. Rename feeds so the new one has the name of the old deprecated. It is a workaround but it works but again - you loose statistics. Symbols and Source seem to survive :-D

Thank you for the report - it appears the uninstaller is relying on a configuration value that does not exist; the uninstaller will be fixed in v5.0.8. For reference, here is a quick summary of what the uninstaller does: (IIS only) delete ProGet application pool (IIS only) delete ProGet website stop & delete INEDOPROGETSVC and INEDOPROGETWEBSVC Windows services delete %ProgramFiles%\ProGet directory delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProGet hive from registry (optional) drop ProGet database (optional, SQL-install only) uninstall SQL Server 2016 from "Add or remove programs"

This will be fixed as part of PG-1204 in v5.0.8 - due out early next week.

Apparently this "works" if you do: IIS::Ensure-AppPool Test ( Runtime: "", Enable32BitAppOnWin64: true, Pipeline: Integrated ); Might be better to do something like: set $NoManagedCode = ""; IIS::Ensure-AppPool Test ( Runtime: $NoManagedCode, Enable32BitAppOnWin64: true, Pipeline: Integrated );

This is a "false positive"; https://inedo.com/support/kb/1113/anti-malware-false-positives-code-signing-and-safety-of-inedo-products Please report it to Cylance

You can uninstall, then reinstall. If you follow KB#1013, and make sure to keep the application pool and websites names as specified, then the installer will detect them next time and upgrade as needed.

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203