2017-02-27 95 views
0

我们正在使用的PushSharpv2.2.1.0略加修改的版本,最近停止在我们的最新版本工作的格式错误。由于重写的时间限制,我们无法将其更新到4.x或3.x版本。经过几天对代码的大部分方面的修改之后,我不确定还有什么可以导致这个问题。到SSPI调用失败 - 收到的消息是意外或

我们收到以下错误,每当我们试图处理数据(到目前为止它看起来像只对事物的苹果侧):

A call to SSPI failed, see inner exception. 
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) 
at PushSharp.Apple.FeedbackService.Run(ApplePushChannelSettings settings, CancellationToken cancelToken) 
at PushSharp.Apple.ApplePushService.<>c__DisplayClass4.<.ctor>b__1(Object state) 

Inner Exception: System.ComponentModel.Win32Exception (0x80004005) 
The message received was unexpected or badly formatted 

我们已经有修复到位提到here。发布很多代码的情况很少,我不确定哪些信息有助于调试。我们没有收到任何问题或错误检索和加载证书(日志记录表明它正确加载和正确的版本)。由于旧版本已过期,因此我们确实对此证书进行了最新更新,但新版本正在正确加载。

什么都没有改变我们的基础设施,将意味着在入站数据的变化。有一些屏蔽更改来保护帐户信息,但删除这些更改并不能解决问题,并且只能在记录过程中进行。我错过了什么?

回答

2

因为我发现,差点这个问题,但并没有完全解决这个问题(因为PushSharp的Git的页面已经表示,他们在从2.x的问题不感兴趣),我会把我的,希望具体回答几个答案它可以帮助某人:

我的问题围绕新的证书。虽然我们安装了新的证书,但我们没有添加持有证书私钥的p12文件,因此邮件无法正确加密。

将p12文件安装到服务器可解决问题。

总而言之,一个很明显的解决方案,目前正在overthought问题。

+0

为了帮助某人,我也遇到了这个问题,摆脱了对Debug Push Broker的调用,为我解决了这个问题。 – torial