Tod, XML Configuration, in fact, is as you suggested, I was only using "MyAssembly" for reference. This is how I have it. <{Company}.ProGetExtensions.FilteredPackageStore Assembly="{Company}ProGetExtensions"> </{Company}.ProGetExtensions.FilteredPackageStore> I tried to start it from command line, same error.

Hi Tod, Restarting the service fixed the issue. I broke a few CI builds, but oh well! Thanks for the help.

The GetUpdates() method is now included in v3.2.1

Running from console asked me for some input, so entered 1 to Run the service, then entered the feed url that I wanted to start. It then found all of the packages and updated the database. However, upon pushing more packages, I found that those packages weren't updated. Once this happened, I remembered that I had to explicitly create a SQL user for the ProGet database (our server team doesn't allow local server accounts to authenticate to SQL but our domain accounts can). Once I edited the ProGet.Service.exe.config file with the correct credentials, it worked as expected. Thanks so much for the help and the very quick responses! Dave

Something like this should work: sealed class FilteredPackageStore : DirectoryPackageStore { private const int PackagesCount = 5; public override Stream Create(string packageId, SemanticVersion packageVersion, bool allowOverwrite) { var packagesToDelete = StoredProcs.Packages_GetPackages(this.FeedId, "Y") .Execute() .Where(p => p.Package_Id.Equals(packageId, StringComparison.OrdinalIgnoreCase)) .OrderByDescending(p => p.Published_Date) .Skip(PackagesCount); foreach (var package in packagesToDelete) this.Delete(package.Package_Id, new SemanticVersion(package.Version_Text)); return base.Create(packageId, packageVersion, allowOverwrite); } }

This error is related to the UploadReadAheadSize value that is configured in IIS. For IIS7+, see: http://www.iis.net/configreference/system.webserver/serverruntime For IIS6, see: http://msdn.microsoft.com/en-us/library/ms525310(v=vs.90).aspx

Got there in the end. Turns out that the proget service wasn't correctly configured. Once I changed this and restarted the service the packages turned up!

Sounds like you basically just made that check list :) There is no "max password attempts" option as the built-in invalid credentials delay mechanism is sufficient to protect against brute-force/guess attacks. Otherwise, SSL and no anonymous is sufficient.

An administrator must log in and run the ProGet.Service.exe executable and reserve the URLs you are using, which will also require a system restart before it takes effect.

Most likely, the user that ProGet is running under is having difficulty requesting this information; you can try to restart the ProGet service, or the WMI service, and if all else, just reboot the server.

ProGet logs all errors to its error log or indexing errors log in the software itself, otherwise to the Windows event log. You can test by running the service (and/or IIS app pool) as your account if you're certain that your account has enumerate privileges.

Looks like a bug; IIS detection does not work on 2012 unless 4.5.1 is also installed. Will be fixed in maintenance release, but you should install 4.5.1 anyway since it has a bunch of bugfixes.

Thank you. I have replaced the contents of the WebApp and Service folders with the contents of the 3.1.0 manual installation zip file (except the config files of course). This seems to work as well. I think it is more or less the same effect as what you did by uninstalling and reinstalling, although your method is probably a bit safer! Luckily the database schema doesn't seem to have any updates in 3.1.1 that means it doesn't work with 3.1.0.

I installed ProGet 3.1.2 today and the errors I experienced with 3.1.1 are gone. Thanks for the quick turn-around on the fix, you guys are great. Riko

Does one of your embedded scripts contain a reference to a module that doesn't exist on a remote server, e.g. Web Server Administration for IIS? Unfortunately the error returned by PowerShell is fairly useless in determining which exact module is missing :)

Thanks for the report - I'll have a dev take a look at this and fix it for the next version, which should hopefully be out today (8/14/14).

Curious, what versions of PowerShell do you have installed on the machine with the ProGet service, and also on the remote machine?

Thank you for the report - this will be fixed in the maintenance release coming out today (v3.1.1)

Looks like Chocolatey now requires the description field to have a value, whereas pre-v0.9.8 it did not require one. We've updated the editor for v3.1.1 to require a description, though this will not impact existing data, so you'd still have to edit existing descriptions so that they have a value.

It's unlikely this will be supported. There is no way to identify from metadata a symbol package vs a regular package... you have to open the zip file and see if it contains pdb/src files... which means we'd have to download every version of every package in a remote feed. If Microsoft / NuGet team ever implements a mechanism for identifying , then it's a possibility.