Hi Alana, the EventView helped. Thanks for the hint. An SQL Error was noting that the "EXECUTE" permission was missing for the Database-User of ProGet. Once I fixed that, everything runs smoothly now.

We don't have a guide for that, but if you uninstall ProGet and reinstall, that might be easy. You can also try to reverse the steps here: https://inedo.com/support/kb/1013/hosting-through-iis-instead-of-the-integrated-web-server

The URL must be in the form http://host:port/ You are missing the "/" at the end of the url you entered.

I see. It appears that dist-tag rm is now failing. We'll investigate and if we are able to reproduce this then it should be easy enough to get in the next maintenance release.

Thanks a lot. It works ;)

Yes, although this is currently extensible by extending the UserDirectory class.

That particular error message is a result of the connection string missing from the configuration file. Please ensure there is a key present in both web.config and in ProGet.Service.exe.config. Most likely, someone had inadvertantly deleted it from the configuration file when attempting to configure the server in IIS. <add key="InedoLib.DbConnectionString" value="Data Source=...;Initial Catalog=ProGet;Integrated Security=SSPI" />

Hi Christian, the information you posted had mentioned internal packages (Aeon Framework, etc), so I removed it That said, it wasn't an error message, but a JSON document that contained metadata information about packages. This is an expected response if you visit an API URL directly in your browser, and when the npm client relies on the JSON data. If you are receiving an error from the npm client, please make sure to share: the precise error message that npm client is using the precise URL that the npm client is requesting; you can get this by running Fiddler, and seeing the requests that the client makes Note that you will need to disable Windows Integrated Authentication at the IIS level, not just within ProGet.

Alex-Hempel said in Proget Jenkins Plugin: Not working on Slaves?: Caused by: java.io.NotSerializableException: com.inedo.proget.jenkins.DownloadPackageBuilder java.io.NotSerializableException can occur when you serialize an inner class instance because serializing such an inner class instance will result in serialization of its associated outer class instance as well. How to solve it? If the class is yours, make the class serializable by implementing the interface java.io.Serializable. All non primitive members implement Serializable (or are transient instead) If your class is an inner class it's either static or the outer class implements Serializable If the class is 3rd party, but you don't need it in the serialized form, mark the field as transient It is important to note that Serialization of inner classes (i.e., nested classes that are not static member classes), including local and anonymous classes, is strongly discouraged.

This is not possible, because that is not a package (but a git repository).

This was removed when all the feed pages were combined (NuGet was the only feed type with an additional filter). We'll have to figure out a good way to add it back - it should be returned in an upcoming maintenance release of v4.4.

See: http://inedo.com/support/questions/5371

Do you have specific guidance on how to setup the separate site?

We refactored a lot of the user-interface code for ProGet 4.4, so this is unfortunately a regression introduced due to those changes. I've logged the issue and it will be fixed in the next maintenance release.

You can temporarily use your key for this purpose, that's quite alight. Just enter the key in, and it will activate.

Well i finally was able to publish to our Powershell feed. I updated the PackageManagement and PowerShellGet modules to version 1.1.0.0. which were released a few days ago... 12 Oct 2016 I hope this helps .

It's still on our roadmap, but it was pushed back to 4.7.

Looks like reinstall helped. Thank you!

This is a limitation of npm unfortunately; scoped packages are not included in the npmjs.org index, therefore there is no way to search for a scoped package via a connector. However if you already know the name, then it will work, and can be retrieved from the connector.