堆栈内存溢出
  简体   繁体   English

通信后无法使用授权建立SSL / TLS的安全通道

[英]Could not establish secure channel for SSL/TLS with authority after communication

 原文  2016-07-05 14:25:18  7   1    c#/ .net/ wcf/ tls1.2

问题描述

Recently one of our clients installed a new certificate on their server. 最近，我们的一位客户在其服务器上安装了新证书。 I installed the certificates including Root certificates on my server. 我在服务器上安装了包括根证书在内的证书。 Since then I'm getting the following error. 从那时起，我得到以下错误。

“Could not establish secure channel for SSL/TLS with authority” “无法通过授权为SSL / TLS建立安全通道”

The error is suddenly thrown between the minute 0 and 10 while continually requesting and posting to the web service. 在连续请求并发布到Web服务的同时，错误在0到10分钟之间突然抛出。 I'v created a consale app writing the method and soap header to the console to see if everything is going good. 我创建了一个consale应用，将方法和soap标头写入控制台，以查看一切是否正常。 Then suddenly the error is thrown. 然后突然引发错误。 If there was something wrong with the certificate I should not even be able to call the first method “getsoapheader”. 如果证书有问题，我什至不能调用第一个方法“ getsoapheader”。 Any idears how this error rises and why. 任何想法者都会指出此错误的原因以及原因。 I have already tried the following. 我已经尝试了以下方法。

I also mailed the application to our client for testing. 我还将该应用程序邮寄给我们的客户进行测试。 They unfortunately could not find an error. 不幸的是，他们找不到错误。 The application run perfectly every time. 该应用程序每次都能完美运行。 I can't get it to work once om my PC using the exact same code. 我无法使用完全相同的代码在PC上运行它。

Any help would be highly appreceated. 任何帮助将不胜感激。 


(1) Start webservice test
(x) Exit



1 28-6-2016 14:18:18 SoapHeader: bf2c890a-18c1-4fe0-8197-9da2bd37f0c0 28-6-2016 14:18:18: GetConstructorCLWorkOrderList date: 1 28-6-2016 14:18:18: GetConstructorCLWorkOrderList date: 1 28-6-2016 14:18:18: GetConstructorCLWorkOrderList date: 2 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 3 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 4 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 5 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 6 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 7 28-6-2016 14:18:19: GetConstructorCLWorkOrderList date: 8 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 9 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 10 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 11 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 12 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 13 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 14 28-6-2016 14:18:20: GetConstructorCLWorkOrderList date: 15 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 16 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 17 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 18 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 19 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 20 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 21 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 22 28-6-2016 14:18:21: GetConstructorCLWorkOrderList date: 23 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 24 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 25 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 26 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 27 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 28 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 29 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 30 28-6-2016 14:18:22: GetConstructorCLWorkOrderList date: 31 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 32 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 33 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 34 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 35 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 36 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 37 28-6-2016 14:18:23: GetConstructorCLWorkOrderList date: 38 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 39 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 40 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 41 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 42 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 43 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 44 28-6-2016 14:18:24: GetConstructorCLWorkOrderList date: 45 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 46 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 47 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 48 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 49 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 50 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 51 28-6-2016 14:18:25: GetConstructorCLWorkOrderList date: 52 28-6-2016 14:18:25 GetWorkOrder start 28-6-2016 14:18:30 GetWorkOrder: 104159 28-6-2016 14:18:30 SoapHeader: c033f8da-1b4a-45f3-a160-7727b8086123 28-6-2016 14:18:30 GetWorkOrder start 28-6-2016 14:18:34 GetWorkOrder: 99055 28-6-2016 14:18:35 SoapHeader: 8eea7e21-23bd-4cf5-8d56-28606f8527b2 28-6-2016 14:18:35 GetWorkOrder start 28-6-2016 14:18:38 GetWorkOrder: 109876 28-6-2016 14:18:39 SoapHeader: 7df630db-c8e5-4bd6-9558-ea05cf541e4b 28-6-2016 14:18:39 GetWorkOrder start 28-6-2016 14:18:44 GetWorkOrder: 101382 Kan geen veilig kanaal tot stand brengen voor SSL/TLS met autoriteit acceptatie-webservice-xx.xxx.com. -2146233087 De aanvraag is afgebroken: Kan geen beveiligd SSL/TLS-kanaal maken.



Server stack trace: bij System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) bij System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) bij System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) bij System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) bij System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) bij System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) bij System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)



Exception rethrown at [0]: bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) bij Webservicetest.Gemma.GemmaWebService.Authenticate(String username, String password) bij Webservicetest.Gemma.GemmaWebServiceClient.Authenticate(String username, String password) in C:\Webservicetest\Webservicetest\Service References\Gemma\Reference.cs:regel 14444 bij Webservicetest.Program.GetSoapHeader() in C:\Webservicetest\Webservicetest\Program.cs:regel 78 bij Webservicetest.Program.Validate() in C:\Webservicetest\Webservicetest\Program.cs:regel 131 bij Webservicetest.Program.StartWebserviceTest() in C:\Webservicetest\Webservicetest\Program.cs:regel 62



(1) Start webservice test (x) Exit

1 个解决方案

解决方案1
 0  2016-07-07 07:13:43

I'm having the biggest headache right now. 我现在最头疼。 The awnser is a Microsoft update that was installed on my laptop the same day as the client installed there new certificate. awnser是在客户端安装新证书的同一天在笔记本电脑上安装的Microsoft更新。 Making me search in the wrong place for the error. 让我在错误的地方搜索错误。 If you get this error please remove the following update. 如果出现此错误，请删除以下更新。

Security update for Microsoft Windows (KB3163017) Microsoft Windows安全更新（KB3163017）

After removing this update everything worked fine again. 删除此更新后，一切恢复正常。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 错误：无法通过授权为SSL / TLS安全通道建立信任关系 - Error: Could not establish trust relationship for the SSL/TLS secure channel with authority 无法为具有“xxxxx.com”权限的 SSL/TLS 建立安全通道 - Could not establish secure channel for SSL/TLS with authority 'xxxxx.com' 无法使用 IIS 的权限为 SSL/TLS 建立安全通道 - Could not establish secure channel for SSL/TLS with authority from IIS WCF：无法为具有权限的SSL / TLS安全通道建立信任关系 - WCF: Could not establish trust relationship for the SSL/TLS secure channel with authority WCF WF服务，无法通过授权为SSL / TLS建立安全通道 - WCF WF Service, Could not establish secure channel for SSL/TLS with authority 无法为具有“...”权限的 SSL/TLS 建立安全通道，但在代码中设置了 TLS。 在本地机器上工作正常，但在生产中不行 - Could not establish secure channel for SSL/TLS with authority “…” but TLS is set in the code. Works fine on local machine but not in Production SSL WCF“无法与权限'localhost'建立SSL / TLS安全通道的信任关系 - SSL WCF "Could not establish trust relationship for the SSL/TLS secure channel with authority 'localhost' 通过SSL的WCF服务无法使用授权'test-service.hostname.com'为SSL / TLS建立安全通道 - WCF Service over SSL Could not establish secure channel for SSL/TLS with authority 'test-service.hostname.com' 无法为SSL / TLS建立安全通道 - Could not establish secure channel for SSL/TLS 调用第三方Web服务和证书时无法使用授权建立SSL / TLS的安全通道 - Could not establish secure channel for SSL/TLS with authority when calling third party web service along with certificate
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM