我正在尝试从testconnectivity.microsoft.com进行“Exchange Web服务同步,通知,可用性和自动回复”测试。
但它失败并出现以下错误: 创建临时文件夹以执行同步测试。 无法创建用于执行测试的临时文件夹。
完整的详细错误:
Additional Details
Exception details:
Message: The request failed. The underlying connection was closed: An unexpected error occurred on a send.
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalBindToFolders(IEnumerable`1 folderIds, PropertySet propertySet, ServiceErrorHandling errorHandling)
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The underlying connection was closed: An unexpected error occurred on a send.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
Exception details:
Message: Authentication failed because the remote party has closed the transport stream.
Type: System.IO.IOException
Stack trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, 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 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
Elapsed Time: 180 ms.
这是我们的Exchange环境配置方式。
我们有4个Exchange服务器,3个具有CAS角色。使用Kemp负载均衡器对连接进行负载平衡,我们使用TMG来展示我们的OWA并为Internet配置自动发现。
请帮助解决此错误。
答案 0 :(得分:0)
您提到您的CAS服务器正由Kemp Load Balancer进行前端处理。鉴于您发现MS Exchange行为存在问题,我们建议您访问我们的support center。在那里,您可以查看相关文档或向我们的支持团队提交票证。如果LoadMaster对我们的工程师能够提供帮助的行为做出贡献。
答案 1 :(得分:0)
我们的TMG网站IIS网站(新创建的)虚拟目录是问题所在。为了测试这一点,我们创建了一个直接防火墙规则,将流量发送到我们的Exchange服务器上的TMG IIS网站的Kemp Loadbalancer IP,我们遇到了同样的问题。然后我们将流量定向到我们的交换服务器上的默认IIS网站,测试分析仪显示没有错误。
所以问题是TMG IIS网站虚拟目录,用于驻留在我们的交换服务器上的自动发现和EWS服务。
我们现在已经创建了一条规则,可以在单独的外部IP上接受交换在线流量,并将其发送到我们的Exchange IIS默认网站。
<强>更新强>
我们不得不将负载均衡器完全从设置中删除,因为它正在修改我们的电子邮件标题,并且因为在本地Exchange Online和Exchange之间发送的所有电子邮件都被标记为匿名而不是内部。这导致我们的会议室不接受预订邀请的问题。
如果您需要更多信息,请发表评论。