![]() ![]() This error is unexpected, whereas this 401 would have been expected: The underlying connection was closed: An unexpected error occurred on a send. On a non-working on-prem server, I get the result: Since Autodiscover fails, let’s test it from the on-prem server and see if it can reach the server in Exchange online via Powershell: The underlying connection was closed: An unexpected error occurred on a send The interesting parts of the event above are the following pieces of information:ĪutoDiscoverFailedException: Autodiscover failed > : An existing connection was forcibly closed by the remote host > System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Exception returned is .Availability.AutoDiscoverFailedException: Autodiscover failed for email address with error : The underlying connection was closed: An unexpected error occurred on a send. Process .Delayed`1: failed in application Mailtips. In addition, your on-premises Exchange servers might start logging events like this: This spring, your on-premises users might not be able to do free/busy requests in calendaring from on-premises mailboxes towards Exchange online mailboxes. This article is intended to help customers and motivate them to check their on-premises TLS settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |