Posts made by rick.kramer_9238

@stevedennis I swtiched from "V3: Active Directory (LDAP)" to "V4: Active Directory/LDAP (Preview)" and all is good now. Logon went from two/three minutes down to one second.

Hi! Is there away to deprecate or unlist all versions of a first party package at the same time? We are on version 2023.34 of ProGet.

Hello,
I wondering if there is an official recommendation on the ProGet API V2 (OData) and V3-JSON? All our Nuget conncectors are V3 and I have not users report a problem with the ProGet V2. I am asking because there is warning banner on the ProGet home page that states the NuGet feed is using deprecated OData (V2) queries.

@atripp Thanks, we got the cert added and https working fine, but after moving away from IIS and running ProGet self-hosted, if anyting the logging time is worse. Everytime I bring up the UI it re-auths me and spins for minutes before opening. There are no messages in the Diagnostic Center. Is there any place I can turn on additional logging to help diagnose this?

@atripp After re-installed with the IWS, we want to set up HTTPS and bind the the existing cert for the DNS entry we use for our ProGet instance. Is it necessary to do all the steps on https://docs.inedo.com/docs/installation-windows-https-support, or can we just register the certificate underneat "HTTPS Binding to a Hostname"

@atripp If we switch to using integrated web server I would probably upgrade from 2023.30 to 24.0.1. If we would happen to need to rollback, would a database restore be needed-- are there database changes moving between these version? Thanks!

Microsoft.Testing packages 1.02 were available but not 1.1.0.

Once we allowed Micrsoft.Testing.* all versions were available. I'm wondering 1.0.2 was allow because of a dependency chain. MSTest.TestAdapter was allowed and version 3.2.2 has a dependency on Microsoft.Testing.Extensions.VSTestBridge.1.0.2 which has a dependency on Microsoft.Testing.Extensions.TrxReport.Abstractions.1.0.2

I am wondering if the allow filter needs to have them explicitly specfied to show all versions? Is the reason we can see an old version is because an allowed package has a dependency on it? thanks! The filter is set to block and hide.

@atripp After doing more testing, I do not think this has anything to do with IIS. I think the login process is what is spinning for 3-4 minutes on initial testing in the morning. We have Windows Integrated Auth enabled wich is what we had been using before upgrade. It looks like Username/Password is also enabled now, not sure if that was enabled before the upgrade. I would be interested in any thoughts you might have on this. thanks

@atripp Do you have any thoughts on the changing the Start Mode and the idle timeout on the app pool? Or Preload Enabled on the Site?

@atripp Thanks, I will continue to monitor. We did not get the .NET error this morning. There was no server reboot but there was an automated IIS reset. We are going to also set up a synthetic monitor in Dynatrcae on the UI.

@atripp Thanks for the reply. After more data gathering I think only once the I found the app pool stopped so it seems the unresponsiveness is something else. I thought something might be forcing a recycle because it is roughly the same amount of time. I cannot confirm at this time that it is being stopped or recycling.

The .NET exception may be unrelated. but it started post-upgrade. And the unresponsiveness was noted again today (Saturday) when no one is online working. I navigated to UI, waited two minutes for it respond, and then sure enough a new Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer exception is in the event viewer. So if not the root cause of anything, the timing sure makes it seem at least as another effect.

There are no related messages in diagnotics center. I wondering if there is a way to do some tracing.

After upgrading to ProGet 2023 we are seeing errors which causes the IIS app pool to stop, and it will start back up after someone tries to download a package or us the UI, but takes 90 sec - 2 minute to start back up. This is what I am seeing in the event viewer which coincides with with the app pool stops (we are on windows server 2022):

Category: Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer
EventId: 2
SpanId: 6f3ab11a2a3bf2ce
TraceId: ea531c1240218f307196736526edf8bb
ParentId: 0000000000000000
RequestId: 40001e29-0001-d800-b63f-84710c7967bb
RequestPath: /

Connection ID "15564440317292715559", Request ID "40001e29-0001-d800-b63f-84710c7967bb": An unhandled exception was thrown by the application.

Exception:
System.OperationCanceledException: The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at Microsoft.AspNetCore.Server.IIS.Core.HttpResponseStream.ValidateState(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.IIS.Core.HttpResponseStream.WriteAsync(ReadOnlyMemory1 source, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.IIS.Core.WrappingStream.WriteAsync(ReadOnlyMemory1 source, CancellationToken cancellationToken)
at Inedo.IO.SlimmerMemoryStream.CopyToAsync(Stream destination, Int32 bufferSize, CancellationToken cancellationToken)
at Inedo.Web.AhHttpResponse.CompleteAsync()
at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
at Inedo.Web.AhWebHost.<>c.<<Configure>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()