Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1316
  • Last Modified:

Microsoft Exchange 2013 Web Services Connectivity Tests Fails

Microsoft Remote Connectivity Tests all pass except for the "Synchronization, Notification, Availability, and Automatic Replies"

I don't have any issues, but we're migrating from 2013 on-premise to Office 365, so the 1st step we're doing is setting up office 365 as Hybrid and we'll move over the mailboxes.

A prerequisite is that EWS must be working properly so i did this test and it's fails with the following error:

Creating a temporary folder to perform synchronization tests.
  Failed to create temporary folder for performing tests.
 
 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.MultiResponseServiceRequest`1.Execute()
 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: The handshake failed due to an unexpected packet format.
Type: System.IO.IOException
Stack trace:
 at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
 at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)


Elapsed Time: 222 ms.
ews-error.PNG
0
egc0700
Asked:
egc0700
1 Solution
 
R--RCommented:
Hi,

Did you ran command test-outlookwebservices on the server. Please go through the link from http://exchangeserverpro.com as below and run the command and check.

http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/ and
0
 
egc0700Author Commented:
running the test showed me that there's a typo in the external URL
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now