Hello Greg It is fine. I would keep a number of days instead a number of log but the result is the same :) Best regards

Copying from associated support ticket: It's not a bug per se, more of a design flaw with the introduction of external package stores. Basically, it checked to see if the package could be opened and if not, deleted it from the DB. However, there are many reasons a package might not be accessible (network down, invalid S3 credentials, disk inaccessible, S3 down, etc.), so this functionality was removed since then.

You can just run "ProGet for Linux", it's already in a container.

This is actually an artifact of the OData specification from when ProGet was first developed - that was actually the preferred format specified, and NuGet.org didn't support $format=json, so we just followed the OData spec. Anyway, those are just .NET DateTime Ticks in there (and the +0 just indicates UTC), so in your example it would just be: new DateTime(636650168208570000, DateTimeKind.Utc) Of course, if we had it to do over again, it would be something more sensible like ISO-8601.

Hi George, Do you have any suggestion that I can do to fix this issue?. Thank you.

Hello William, This will be fixed in ProGet 5.1.2. (PG-1294)

Thank you John This is exactly what I was looking for. You save my time and I really appreciate the time you have spent to answer me Best regards

Here are the possible reasons for reactivation: https://inedo.com/support/documentation/various/licensing/activation#re-activation

We definitely plan to improve the event handling & logging, across the board for our products. I don't have a date on it, but it's in the specification process; we always welcome feedback at this stage, so if you are interested in reviewing once it's ready, we would definitely appreciate it. We don't have an import/export feature for these events. However, they are stored in the database (across a couple tables - EventOccurences and EventOccurenceDetails), so you could extract using this.

It sounds like you don't have the extension installed... Go in to your extensions folder, then delete the extensions. restart ProGet website. Then go to reinstall the OSSIndex instead. Then it'll appear :)

Basically you need to make sure all three servers have the same machineKey in the machine.config section. OrchardCMS has a nice docs page on it: http://docs.orchardproject.net/en/latest/Documentation/Setting-up-a-machine-key/

The issue that you linked has since long been resolved; it was a problem with our beta v4. At that time, the problem was the ProGet was "leaking" some connections (i.e. not properly disposing, as your DBA noted). So, if you're seeing the problem now, it's unfortunately not so "simple" of a problem to fix. It basically means that there is some sort of latency between the web/database servers and/or the database is not able to respond to queries as fast as the web server is making them. There's a lot of things that can cause these, from fragmented indexes to low resources on the database server. Do you know what changed recently? Etc. I'm afraid increasing the connection pool likely won't help :/

Confirmed that was the issue, thanks Tod.

It's possible it may work (I can't verify) if you specify the port in the domain controller host value under advanced settings (i.e. enter your-dc-server:636 as the value). See the LDAP Advanced Settings documentation for info on how to find that page to configure that value. If that doesn't work, I suspect a code change is needed - it is not clear via the Microsoft documentation what the default AuthenticationType is for this call: https://github.com/Inedo/inedox-inedocore/blob/master/InedoCore/InedoExtension/UserDirectories/ADUserDirectory.cs#L268

Make sure you change the proget webservice to run as a user account that has domain access and not use the local system account on the server.

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

Hey! It did solve my problem, thank you so much! Have a great week-end. :)

ProGet is licensed per server, so if you were to have two servers (even if one is just a test / pre-production environment), you would be required to a purchase a separate license. However, if it's just for migration purposes, then you can use your existing license for the migration period.

Hi Oleg, Hedgehog is now installed using our new install center using a totally different process, and I believe this particular issue is already fixed, and I can confirm that in our environment network service installs seem to work correctly on Server 2016. If you're still seeing this issue as of the Hedgehog v1.0.4 installer, let us know :)

Thank you Alana. That worked.