Hi @scott-wright_8356 , You can change if you'd like, I'm not sure if it makes any difference with .NET6+ applications. Cheers, Alana

A possible solution to this is to use Extended Properties in SQL. That way you can check the version of the files in the upgrade and not re-create them when they have already been updated?

When you say Web Server Windows Service, I think you should put the account against the ProGetAppPool Identity. We are running as an integrated SQL connection, and the account is a DB Owner. Both the APP Pool and ProGet Service run as this account. We added the following to the connection string Persist Security Info=False;Integrated Security=true;

Just to close this thread off. I tried below but no joy: Rebooting server several times Server is not under any load All other feed related API's worked fine Re-installed proget Resolved: Re-installed proget and re-created DB

Hi @jw , thanks for pointing this out! I added a note to review/investigate this in our run-up to finalizing ProGet 2024.

Hi @philippe-camelio_3885 , We haven't run into any of these issues in our testing, but this error is a "generic database timeout", which is implying that "something" is going on with the database. That's the only information we have, "something". To troubleshoot this, you'll need to use some of SQL Server's performance/activity monitoring tools to spot what's going on at the time. It could be anything from outdated statistics to a missing index to a bad query. Or who knows. Best, Alana

Hi @philippe-camelio_3885, We do not support "sub-path content/URL Rewriting" in any of our products and strongly discourage even trying. It won't work and will just lead to lots of wasted time and headaches, since everything from javascript ajax requests to CSS background images to cookies assumes a well-known root path of / for the application. Best, Alana

Hi @mahdy-merry_6333 , It's possible, and you can do this by creating a second feed that effectively proxies the first feed and uses disk storage. You could use a Connector on the two feeds or REplication. Cheers, Alana

Hi @jw, Thanks for letting us know about these. To answer your questions: This is an issue with the order of how we delete the projects and their child items. If you delete all the builds first, then the project can be deleted without issue. We will fix this as part of PG-2596 that will be released tomorrow in ProGet 2023.31. This is an oversight on our part. We will get delete buttons added to the Edit Project Settings and Edit Build Settings page also as part of PG-2596. Thanks, Rich

Hi @matt-wood_5559 , Looks like your account was added to My Inedo incorrectly due to a human error (someone manually added it on our end since you had been talking to sales)... but it looks like its already been corrected, and you have a working key to use now. You shouldn't have any issues going forward. Cheers, Alana

@atripp We applied the script, can confirm that we are not getting the error anymore. Thanks!

Hi @norm-ross_1437 , I'm not sure what version of ProGet you're using, but this sounds familiar and I'm almost certain we fixed this specific case a while ago. So I would try to upgrade. I don't realy recommend playing around with data in the tables.... Best, Alana

Hi @forbzie22_0253 , We are aiming to release ProGet 2024 in early April; here are the upgrade notes in progress, which will give some idea of what's coming: https://docs.inedo.com/docs/proget-upgrade-2024 Best, Alana

Excellent, we have just moved to using integrated security with the SQL server. The account was configured as DB owner. Will test the next upgrade when available.

Thank you for the information. I will investigate the virus scanner

Hi @scott-wright_8356, This is usually due to a networking error; it may also be resolved by restarting. It's also just something you can ignore. The service messanger isn't very important in ProGet. Best, Alana

Hi @proget-markus-koban_1462, Thanks for clarifying; the "User directory" is outdated and I removed that from the documentation. In old versions of ProGet, you'd need to set up a separate directory. Now they are just added as Built-in users. The Trial version should allow you to configure SAML. It sounds like the issue is that Keycloak is not redirecting to ProGet. I really wish I knew how to help troubleshoot... but after logging in, Keycloak is supposed to POST to /saml-acs-callback in the ProGet instance. I wonder if there's n additional thing that's not configured on Keycloak? Best, Alana

@atripp Thank you!

Hi Alana, thanks for the input. Made me reconsider our current versioning scheme to a much simpler and more deterministic solution. This topic can be marked as resolved now!