Error In Visual Studio/InternetExplorer/Chrome: This operation requires IIS integrated pipeline mode.

[schmid_6935]

Hey,

Error for Nuget-Package in Visual Studio 2017: 500 (Internal Server Error) => Cannot download package!

This operation requires IIS integrated pipeline mode.

Exception Details: System.PlatformNotSupportedException: This operation requires IIS integrated pipeline mode.

Full Stack Trace:

 System.PlatformNotSupportedException: Für diesen Vorgang muss der integrierte Pipelinemodus von IIS verwendet werden.
bei System.Web.HttpResponse.get_Headers()
bei Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.WriteError(HttpContext context, Int32 statusCode, String message, String description)
bei Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.<ProcessGetRequestAsync>d__0.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.<ProcessRequestAsync>d__3.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.<ProcessRequestAsync>d__8.MoveNext()

Dear
Frank

Product: ProGet
Version: 5.0.13

[atripp]

This is basically an error reporting an error; it can sometimes happen, and thus it masks the underlying error. The usual cause is the client disconnected unexpected, and the error can't be reported.

You can switch to INTEGRATED PIPELINE mode to see the full error

[schmid_6935]

Hey Alana,

how can I switch to INTEGRATED PIPELINE? I'm using the integrated IIS Webserver...

Thanks

Dear
Frank

[Dave]

We are also experiencing this issue.

Fresh proget install using the integrated webserver. Does not occur in chrome, but does in visual studio and through the nuget.exe command line.

[Dave]

I've been investigating this issue with Wireshark and have narrowed it down somewhat.

NuGet will first send a request with no credentials, and ProGet will respond:

401 Unauthorized

With the header:

WWW-Authenticate: Basic realm="ProGet Feed {name of feed}"

Signalling that NuGet should try again with a basic authorization header.
NuGet does just that and it works fine for endpoints such as:

FindPackagesById
Search

However, when requesting a specific package at the URI:

/nuget/{name of feed}/{name of package}/{version of package}

The server will return:

500 Internal Server Error
This operation requires IIS integrated pipeline mode.

And the logs provide the stack trace originally posted by Frank.

System.PlatformNotSupportedException: This operation requires IIS integrated pipeline mode.
at System.Web.HttpResponse.get_Headers()
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.WriteError(HttpContext context, NuGetFeed feed, HttpStatusCode statusCode, String message, String description)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.<ProcessGetRequestAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.<ProcessRequestAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.<ProcessRequestAsync>d__8.MoveNext()

As you can see the first line of the stack trace is the getter for HttpResponse.Headers. The exception is thrown and due to the 500 error not being a 401 NuGet simply makes the request again without adding the Authorization header.

This works just fine for me in chrome - I'd guess because my credentials are stored in a cookie rather than in the Auth header.

Any thoughts from Inedo about why this endpoint behaves differently to others?

[schmid_6935]

Today I installed the update to 5.1.3, but the problem still exists.

@Dave: Thank you for your research.

[schmid_6935]

I have opened a support ticket: https://my.inedo.com/tickets/view?ticketNumber=EDO-5119

[schmid_6935]

Solution

[Dave]

Sadly, for me, the given DLL cannot just be dropped into the folder to replace the old DLL without producing a binding redirect error:

[FileLoadException: Could not load file or assembly 'ProGetCoreEx, Version=5.1.3.10, Culture=neutral, PublicKeyToken=20535527eaf4e568' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
   Inedo.ProGet.WebApplication.<BeginFirstRequestAsync>d__2.MoveNext() +0
   System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start(TStateMachine& stateMachine) +114
   Inedo.ProGet.WebApplication.ProGetHttpModule.BeginFirstRequestAsync(HttpApplication app) +90
   Inedo.Web.<HandleBeginFirstRequestInternal>d__28.MoveNext() +306
   System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
   Inedo.Web.InedoHttpModule.ProcessEnd(IAsyncResult ar) +117
   System.Web.AsyncEventExecutionStep.InvokeEndHandler(IAsyncResult ar) +219
   System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +159
   System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
   System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +611
   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +213
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +131

ProGetCoreEx is version 5.1.3.9, however it expects 5.1.3.10