Crash when using WebListener and Negotiate auth scheme

[jchannon]

Scenario :

Server is running with options.ListenerSettings.Authentication.Schemes = AuthenticationSchemes.Negotiate;

Client IE settings to automatically logon sites in the intranet zone. URL of site is not in the the sites list.

Client makes request to server and it crashes the server. Put the URL in the sites and auth takes place and all is well.

We ran DebugDiag to try and get a crash dump and below is the stack trace inside it (note this is reproducible on a customer installation currently 😢 ) :

An unhandled exception of type 'System.EntryPointNotFoundException' occurred in Microsoft.Net.Http.Server.dll

Additional information: Unable to find an entry point named 'CancelIoEx' in DLL 'api-ms-win-core-io-l1-1-1.dll'.


    Microsoft.Net.Http.Server.dll!Microsoft.Net.Http.Server.RequestContext.ForceCancelRequest()    Unknown
    Microsoft.Net.Http.Server.dll!Microsoft.Net.Http.Server.RequestContext.Abort()    Unknown
    Microsoft.Net.Http.Server.dll!Microsoft.Net.Http.Server.ResponseStreamAsyncResult.Fail(System.Exception ex)    Unknown
    Microsoft.Net.Http.Server.dll!Microsoft.Net.Http.Server.ResponseStreamAsyncResult.IOCompleted(Microsoft.Net.Http.Server.ResponseStreamAsyncResult asyncResult, uint errorCode, uint numBytes)    Unknown
    System.Private.CoreLib.ni.dll!System.Threading._IOCompletionCallback.PerformIOCompletionCallback(uint errorCode, uint numBytes, System.Threading.NativeOverlapped* pOVERLAP)    Unknown

[Tratcher]

OS? Windows 7 / 2008 R2?
Framework? .NET or .NET Core?
WebListener version?

api-ms-win-core-io-l1-1-1.dll is a dependency not present on older Windows versions but can be bundled or installed. I'll work on a repro and a workaround.

[moozzyk]

(or in case of standalone applications the application was published for a newer version of Windows that it is running on e.g. an app published for win8-x64 being run on win7-x64)

[jchannon]

It is a self contained app published with win7-x64

It is .net core "Microsoft.AspNetCore.Server.WebListener": "1.1.0",

Running on Windows 2008 R2 SP1

[jchannon]

Just a bit more info from the customer.

Their Local Intranet settings does in fact have a *.enterprise.com wildcard in Site List but when they visit https://server.enterprise.com we see the above stack trace. On a machine where they can edit these settings if they directly put https://server.enterprise.com in the Site List all is well.

[Tratcher]

That call stack looks like a secondary exception (which we should fix), but it doesn't tell us what the primary exception was. Can they reproduce it reliably enough to capture the first chance exception with the debugger?

[Tratcher]

Since it's a self-contained app, do you have 'api-ms-win-core-io-l1-1-1.dll' in your app directory?

[jchannon]

The dll is there. I can send the dump file if you like?

…

On Fri, 17 Mar 2017 at 19:35, Chris R ***@***.***> wrote: Since it's a self-contained app, do you have 'api-ms-win-core-io-l1-1-1.dll' in your app directory? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#326 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGaps-SGTZoOt6qjXOUXzLMaguodJIfks5rmuCZgaJpZM4Md5OB> .

[jchannon]

The dump file is here - https://drive.google.com/file/d/0B4zNlOLPdHfeYVdMT2lrT1FVOE0/view?usp=sharing

[jchannon]

Any update on this, customer = large international bank

[Tratcher]

@jchannon urgent customer issues should be routed to Microsoft Support (https://support.microsoft.com/). The dev team does not have the bandwidth for all investigations.

[Tratcher]

I found the primary exception in the dump:

System.EntryPointNotFoundException: Unable to find an entry point named 'CancelIoEx' in DLL 'api-ms-win-core-io-l1-1-1.dll'.
   at Microsoft.Net.Http.Server.UnsafeNclNativeMethods.CancelIoEx(SafeHandle handle, SafeNativeOverlapped overlapped)
   at Microsoft.Net.Http.Server.RequestContext.ForceCancelRequest()
   at Microsoft.Net.Http.Server.RequestContext.Abort()
   at Microsoft.Net.Http.Server.ResponseStreamAsyncResult.FailSilently()
   at Microsoft.Net.Http.Server.ResponseStreamAsyncResult.IOCompleted(ResponseStreamAsyncResult asyncResult, UInt32 errorCode, UInt32 numBytes)}	System.Exception {System.EntryPointNotFoundException}

It's actually the same error triggered slightly earlier:

HttpSysServer/src/Microsoft.AspNetCore.Server.HttpSys/RequestProcessing/ResponseStreamAsyncResult.cs

Line 247 in 8d61026

asyncResult.FailSilently();

vs

HttpSysServer/src/Microsoft.AspNetCore.Server.HttpSys/RequestProcessing/ResponseStreamAsyncResult.cs

Line 270 in 8d61026

asyncResult.Fail(e);

FailSilently would be called when the client disconnected before the response was completed. It's not clear why this would be related to Negotiate, unless they were writing their own 401 error page?

However, it still comes down to not being able to load that dll. I have not been able to reproduce this issue with the 1.1.1 runtime, dev bits, and Win7x64. If you enable COREHOST_TRACE=1 is the specified dll in the trace? You should see something like Probed deps json and matched [C:\Program Files\dotnet\shared\Microsoft.NETCore.App\1.1.1\api-ms-win-core-io-l1-1-1.dll]

[jchannon]

Thanks will get this setup on the customer's install.

Our application does have middleware that does return 401 in a couple of locations eg/XSRF checks, user validation

[jchannon]

Here's a log with the env var set. Thanks

https://drive.google.com/file/d/0B3uxSfah57yBamxoTWhmMzR6cDA/view?usp=sharing

[jchannon]

Any update? Thanks 🙏