Jun 13 2019 05:06 AM
Hello,
i am currently trying to configure the Hybrid Agent Public Preview and i am always getting the following error in step 8d. (described here: https://docs.microsoft.com/en-us/exchange/hybrid-deployment/hybrid-agent#installation-steps) with the following error:
Microsoft.Exchange.Management.Migration.MigrationService.Endpoint.TestMigrationServerAvailability.InternalProcessEndpoint(Boolean fromAutoDiscover)' IsValid=1 Message='The connection to the server '<GUID>.resource.mailboxmigration.his.msappproxy.net' could not be completed.' ObjectState='New' Result='Failed' SupportsCutover=0} 2019.03.28 15:26:19.498 10341 [Client=UX, Page=HybridConnectorInstall, Step=TestOrgRoute, Thread=26] FINISH Time=345.4s Results=Failed The connection to the server '<GUID>.resource.mailboxmigration.his.msappproxy.net' could not be completed., The call to 'https://<GUID>.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out while waiting for a reply after 00:00:00.0024533. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The HTTP request to 'https://<GUID>.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0020000. The time allotted to this operation may have been a portion of a longer timeout. --> The operation has timed out, The request channel timed out while waiting for a reply after 00:00:00.0024533. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout., The HTTP request to 'https://<GUID>.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0020000. The time allotted to this operation may have been a portion of a longer timeout., The operation has timed out
Another description o the error can be found here:
Is anyone facing the sam issue or has got a solution for that? Maybe it is a temporary bug caused of the preview?
Jun 15 2019 12:49 AM