We identified a cause of this, and it was fixed in PG-1121 in ProGet 4.8.6

I see, so the actual problem is that you don't have the ability to create or manage AD Groups? Yes, that is certainly annoying... You will probably be better off working within your organization to change this policy. It's awfully silly, and totally defeats the purpose of using AD to begin with. That said, we will consider adding a "teams" feature for a future version.

Basically, the template doesn't represent valid OtterScript, and that's why there is an error. Basically, this is not a valid OtterScript statement: $Increment(${index}, 1); You can, however, do this: set ${index} = $Increment(${index}, 1); Except, the "set" statement is not supported in a text template, which means you cannot do what you're doing. You could probably work something out with $foreach $i in @Range(...), but it could get a little messy.

Yes, if you create a Artifact Retention policy with these options: Only purge artifacts in deployed releases Only purge artifacts in rejected packages

ProGet Basic includes support via tickets submitted at https://my.inedo.com in addition to this QA forum (which is more often community supported) for each year purchased of Annual Licensing. If you choose the Perpetual option, the 1st year is included, and then support may be renewed each following year for 20% of the "then-current" licensing price.

Issue was due to the noexec option on the /tmp partition. Remove the noexec option and remount the /tmp.

I see what happened, I looked under Servers where I would have thought that info would be but instead it's under General in the docs.

Can you provide the full stack trace? It will be logged in Admin > Errors.

Based on that error, it sounds like ASP.NET 4.5 is not enabled on your server; this is a separate role feature you must install on your computer/server. It could also be a configuration error, as the message suggested, and you've prevented proget's web.config from removing those handlers at the machine level. In this case you'll need to use the built-in web server, or fix the configuration.

There's nothing jumping out in the logs that's off, it likely is bad information that the client is sending. Most likely it's stemming from the fact that, your package is about 100x as big as a NuGet packages (i.e. .NET libraries) are intended to be. Microsoft will probably never prioritize support for this sort of package, so it's not going to be high on our list either to work-around either. I would recommend you to find a different way of solving whatever problem you are trying to solve in a different way. If you're packaging applications, you should consider a format actually built for such purposes, like the Universal Package Format or Romp packages.

This is a false positive; unfortunately we seem to be the target of many of them :( See http://inedo.com/support/kb/1113/anti-malware-false-positives-code-signing-and-safety-of-inedo-products Please report the false positive, because some of the virus total companies will not let us do it, only their customers.

I'm pretty sure mike you don't need to copy the folders one at a time and wait for pickup...you could copy all the packages at once. And watch out for that powershell script -- it will copy all files in all subdirectories into the current directory, so if your subdirectories contain things other than packages you should add a filter to it.

Hello Bruce, I believe the Jenkins plugin does not want the leading slash on the path, so this should work: parent-folder,myFolder/**/* Let me know if I misunderstood your question - I don't usually work with Jenkins.

That was too easy and it was right there in the error message. I need a facepalm emoji right now. Thanks for the quick response!

Thank you Alana. We have a lot of feeds configured. Is there an easy way to distinguish which one is/are failing?

Hey Tod, Thanks for the answer and apologies for not getting back to you sooner... I see a new version of Otter is now available with the fixes included, so I'll try that out and see what happens. Thanks for the great support! Andrew

In this case, it sounds like the permissions for AWS must not be correct...the user must have full control/read/write access to bucket you specify.

These article by AWS will should help provide you details on how to build a connection string to put in there: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.rds.html http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToMicrosoftSQLServerInstance.html

You can use the following docker command: docker rmi tag-name

Hi Travis, thank you for the additional update. I was very confused by this as well... the problem is the documentation that says if "LDAP" is enabled... it should say "if Integrated Authentication is enabled then the API key is ignored". When those docs were written, those 2 were 1 in the same. I guess the whole point of this is to never use a feed "NuGet API key" since it duplicates what the "ProGet API keys" already do in terms of authentication.