Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests under: System.Net.Security.Tests.ServerAsyncAuthenticateTest failed with "System.ComponentModel.Win32Exception" #23692

Closed
KristinXie1 opened this issue Sep 30, 2017 · 6 comments
Labels
Milestone

Comments

@KristinXie1
Copy link

Failed tests:
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_EachSupportedProtocol_Success
System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_MismatchProtocols_Fails

Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_netcoreapp_win7_release/272/testReport/System.Net.Security.Tests/ServerAsyncAuthenticateTest/ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success_serverProtocol__Tls_/

Configuration: outerloop_netcoreapp_win7_release

MESSAGE:

System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm

STACK TRACE:

at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface secModule, String package, CredentialUse intent, SCHANNEL_CRED scc) in D:\j\workspace\outerloop_net---15cfbbd5\src\Common\src\Interop\Windows\sspicli\SSPIWrapper.cs:line 167 
at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCHANNEL_CRED secureCredential) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslStreamPal.Windows.cs:line 408 
at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(X509Certificate certificate, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslStreamPal.Windows.cs:line 131 
at System.Net.Security.SecureChannel.AcquireServerCredentials(Byte[]& thumbPrint) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SecureChannel.cs:line 677 
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SecureChannel.cs:line 784 
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SecureChannel.cs:line 707 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslState.cs:line 749 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslState.cs:line 965 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslState.cs:line 868 
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslState.cs:line 681 
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslState.cs:line 598 
at System.Net.Security.SslStream.BeginAuthenticateAsServer(X509Certificate serverCertificate, Boolean clientCertificateRequired, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation, AsyncCallback asyncCallback, Object asyncState) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslStream.cs:line 161 
at System.Net.Security.SslStream.<>c.<AuthenticateAsServerAsync>b__35_1(X509Certificate arg1, Boolean arg2, SslProtocols arg3, AsyncCallback callback, Object state) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslStream.cs:line 273 
at System.Threading.Tasks.TaskFactory`1.FromAsyncImpl[TArg1,TArg2,TArg3](Func`6 beginMethod, Func`2 endFunction, Action`1 endAction, TArg1 arg1, TArg2 arg2, TArg3 arg3, Object state, TaskCreationOptions creationOptions) at System.Net.Security.SslStream.AuthenticateAsServerAsync(X509Certificate serverCertificate, Boolean clientCertificateRequired, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\src\System\Net\Security\SslStream.cs:line 274 
at System.Net.Security.Tests.ServerAsyncAuthenticateTest.<ServerAsyncSslHelper>d__11.MoveNext() in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\tests\FunctionalTests\ServerAsyncAuthenticateTest.cs:line 154 
--- 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 System.Net.Security.Tests.ServerAsyncAuthenticateTest.<ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success>d__9.MoveNext() in D:\j\workspace\outerloop_net---15cfbbd5\src\System.Net.Security\tests\FunctionalTests\ServerAsyncAuthenticateTest.cs:line 95 
--- 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) 
--- 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) 
--- 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)
@danmoseley
Copy link
Member

@davidsh can network glitches cause this error or is it something different?

@davidsh
Copy link
Contributor

davidsh commented Sep 30, 2017

or is it something different?

I don't think it is a network glitch. These tests use loopback. The problem I think is due to X509 certificate bugs (caused by PFX files being used for certificates) and tests running in parallel. @bartonjs had previously commented on this in #23221 which had similar X509 issues. This still needs to be debugged further.

@karelz
Copy link
Member

karelz commented Nov 30, 2017

BTW: Last failure was on 11/3

@karelz
Copy link
Member

karelz commented Dec 22, 2017

The failure The client and server cannot communicate, because they do not possess a common algorithm wasn't hit in Helix official runs since 7/11.
The only failures happaned 7/6-7/11 -- 55 failures, each day at least 8.

BTW: There are other, likely unrelated failures in these tests later on - not tracked by this issue.

Closing. Please reopen if it happens again.

@karelz karelz closed this as completed Dec 22, 2017
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.1.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants