So its early days but performing the basic Functions from both the PowerShellGet and PSResourceGet modules seems to work as expected without issue, i.e. Find-Module, Find-PSResource, Install-Module, Install-PSResource, Publish-Module, Publish-PSResource work well. I guess the main reason for asking this question was to check that you guys keep track of these modules released by Microsoft since they are widely used and its nice to know support is on hand if necessary. Its always comforting to know that a vendor is keeping track of issues on platforms such as GitHub etc.... thanks for prompt replies.

@Dan_Woolf awesome thanks

Hi @moez-ul-hasan_3818 , ProGet only supports SAML-based authentication; as you noticed, we recommend and document using SAML for Azure. So I would just recommend creating a SAML-based Enterprise App for that. OpenID is a totally different protocol, and our products do not currently have support for that. Cheers, Alana

@rhessinger ok thanks

Hi Atripp, We have received some scripts from Alex Papadimoulis. We started running these yesterday and the SQL blocking has so far disappeared and the Dashboards_GetLargestPackages now has no issues. Looks like Brett Shearer and Alex have a solution for both problems. Our load is still an issue at peak times but features are now working fast. Will keep monitoring and get back to Alex confirming the outcomes of the new stored procedures next week. Thank you

@forbzie22_0253 performance should be about the same, correct

Hi @dan-brown_0128 , The latest version includes a migration tool, so I would recommend using that. The URL has been changing throughout ProGet 2023, but you will be safe whitelisting cdn.inedo.com and security.inedo.com. This is only required for downloading updates, as it's an offline database that ships with ProGet. Cheers, Alana

@atripp ok that makes sense, thanks for confirming.

Hi @scott-wright_8356, We haven't seen any other issues with this procedure in particular, but it's something we can consider to update. Have you considered that doing the commit with UPDLOCK and SERIALIZABLE could be causing issues with AlwaysOn and sycnchronsist commits going to the secondary? One thing we faced with ProGet 2023's new database model was handling different bugs in different version of SQL Server's analysis engine. Without this pessimistic lock, some versions of SQL Server 2019 will deadlock while updating totally unrelated indexed view. That said, you shouldn't need to use synchronous commits with ProGet in AlwaysOn. That's going to slow things down a lot to begin with, and that level of data-integrity is so important in ProGet. Thanks, Alana

Thank you atripp, confirmation of everything we thought was the problem and working on it now.

@atripp said in ProGet Diagnostic Center: Delete All Messagses: TRUNCATE LogMessages Thank you worked perfectly yes there were a lot of logs.

Hi @yogeshshines_9136 , This should be resolved by downloading the latest Inedo Hub from https://my.inedo.com/downloads Thanks, Alana

Hi @Justinvolved , I've never seen that error and it makes no sense. It's a random Windows COM error. It's not BuildMaster-specific, it's happening when invoking the MWA libraries to save IIS configuration. This would happen if you performed the identical action from with IIS Manager as well, wrote a PowerShell script, etc. I searched "a specified logon session does not exist. it may have already been terminated" and the advice is all over the place. It has something to do with permissions, I guess? Adding "IIS" adds more specific results, so maybe that will help. So my advice from here is to just search and try random things that people said work. Feel free to share what you found ! Best, Alana

Hi @atripp, So I associated the deployment targets with environments and that fixed both of my issues: $EnvironmentName is populated and now the environments are showing on that application screen: [image: 1707424775266-f2980f10-64c0-41a7-a082-7115d0d3b1ba-image.png] Thanks!

Thanks @dongjie789_8066; of course we can definitely consider creating a different API, but you are first non-Edge user to ask about it :) It's best to handle that through your My Inedo account with your work email, so we can work with your team/company about it

Hi @PhilipWhite , You're correct, this is a regression in the validation code... if (!value.All(c => (char.IsLetterOrDigit(c) && char.IsLower(c)) || c == '.' || c == '_' || c == '-' || c == '/')) return new ValidationResults(false, $"Docker Repository names may only contain lowercase letters, digits, periods, underscores, slashes, or dashes."); I guess we recently added char.IsLower because UpperCase characters caused all sorts of problems.... easy fix, and easy work around. Just enter blah in the Repository name field, Click Save Click "view all" Click on the Docker repository in that view, edit We'll get this fixed for teh next maintenance release via BM-3932 Cheers, Alana

@atripp Thanks, I installed 23.0.10 this morning and the git checkout task succeeds on the RedHat server. Next step is getting the docker build task to succeed. I may open a separate post for that.

It seems the 401/403 only happens for NPM/NuGet calls and not on the Web UI. If you'd like I can search for the corresponding log messages and get them to you for further troubleshooting. However, with the appropriate DB sizing the issue is mostly non-existent (once every few days) which is totally tolerable. Cheers Simon