Forum Discussion
MRS Proxy
Hi NunoAriasSilva,
yes i have restart iis but nothing change.
Yes all service point new server exchange 2019.
Hi have try this test in PS:
Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress angelotest4@mycompany.it
this is the output:
PS C:\> Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress angelotest4@mycompany.it
Richiesta credenziali di Windows PowerShell: cmdlet Test-MigrationServerAvailability at command pipeline position 1
Avviso: uno script o un'applicazione nel computer remoto OUTLOOK.OFFICE365.COM ha richiesto le credenziali dell'utente.
Immettere le credenziali solo se si considerano attendibili il computer remoto e l'applicazione o lo script che le
richiede.
Supply values for the following parameters:
Credentials
RunspaceId : f94047a5-e3b6-4315-80a8-5f048583a837
Result : Failed
Message : The ExchangeRemote endpoint settings could not be determined from the autodiscover response. No
MRSProxy was found running at 'mail.mycompany.it'.
SupportsCutover : False
ErrorDetail : internal
error:Microsoft.Exchange.Migration.MigrationRemoteEndpointSettingsCouldNotBeAutodiscoveredException:
Non sono riuscito a stabilire le impostazioni dell'endpoint ExchangeRemote dalla risposta
dell'individuazione automatica. Non ci sono MRSProxy in esecuzione su 'mail.mycompany.it'. --->
Microsoft.Exchange.Migration.MigrationServerConnectionFailedException: Non sono riuscito a
completare la connessione al server 'mail.mycompany.it'. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemoteTransientException: La chiamata a
'https://mail.mycompany.it/EWS/mrsproxy.svc' non è riuscita. Dettagli errore: The underlying connection
was closed: A connection that was expected to be kept alive was closed by the server. --> The
underlying connection was closed: A connection that was expected to be kept alive was closed by the
server. --> Unable to read data from the transport connection: A connection attempt failed because
the connected party did not properly respond after a period of time, or established connection
failed because connected host has failed to respond. --> A connection attempt failed because the
connected party did not properly respond after a period of time, or established connection failed
because connected host has failed to respond. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: The underlying connection
was closed: A connection that was expected to be kept alive was closed by the server. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: The underlying connection
was closed: A connection that was expected to be kept alive was closed by the server. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: Unable to read data from
the transport connection: A connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed because connected host has failed
to respond. ---> Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: A
connection attempt failed because the connected party did not properly respond after a period of
time, or established connection failed because connected host has failed to respond
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceFault.ReconstructAndThrow
(String serverName, VersionInformation serverVersion)
at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.<>c__DisplayClass4_0.<CallSe
rvice>b__0()
at Microsoft.Exchange.Net.WcfClientBase`1.CallService(Action serviceCall, String context)
at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.CallService(Action
serviceCall, String context)
at Microsoft.Exchange.MailboxReplicationService.WcfClientWithVersion`2.CallService(Action
serviceCall, String context)
at Microsoft.Exchange.Migration.MigrationExchangeProxyRpcClient.CanConnectToMrsProxy(Fqdn
serverName, Guid mbxGuid, NetworkCredential credentials, LocalizedException& error)
--- End of inner exception stack trace ---
at
Microsoft.Exchange.Migration.MigrationEndpointVerifier.VerifyConnectivity(MigrationEndpointBase
endpoint)
at Microsoft.Exchange.Management.Migration.MigrationService.Endpoint.TestMigrationServerAvailabili
ty.InternalProcessEndpoint(Boolean fromAutoDiscover)
--- End of inner exception stack trace ---
TestedEndpoint :
IsValid : True
Identity :
ObjectState : New
Regards
Angelo
Hi angeloforum,
Regarding the error that you are facing may be some permissions or problems on Autodiscover.
Enable the MRSProxy and set the authentication required to perform the move. To do this, run the following cmdlet:
Set-WebServicesVirtualDirectory -Identity "Server\EWS (default Web site)" –MRSProxyEnabled $true – WSSecurityAuthentication $True
Can you see this post if it resolves the problem?
Unable to configure migration Endpoint - Hybrid Exchange - Microsoft Tech Community
Best Regards,
Nuno Árias Silva
Office Apps and Services
https://www.nuno-silva.net
- angeloforumDec 23, 2020Copper Contributor
sorry for the delay of my reply
This is the poutput of GET command
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory -Server SERVEREXCNAHE |fl
RunspaceId : 0a443cd0-a54a-4d6a-8b88-ccae1d1cdd11
CertificateAuthentication :
InternalNLBBypassUrl :
GzipLevel : Low
MRSProxyEnabled : True
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : True
AdfsAuthentication : False
MetabasePath : IIS://SERVEREXCHANGE.MYCOMPANY.com/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.2 (Build 464.5)
Server : SERVEREXCHANGE
InternalUrl : https://mail.MYCOMPANY.it/ews/exchange.asmx
ExternalUrl : https://mail.MYCOMPANY.it/ews/exchange.asmx
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=SERVEREXCHANGE,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Gruppo Zenit,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=gruppozenit,DC=com
Identity : SERVEREXCHANGE\EWS (Default Web Site)
Guid : ed902395-5303-4d73-9a10-dfa247f2232f
ObjectCategory : MYCOMPANY.com/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 28/11/2019 14:38:37
WhenCreated : 28/11/2019 13:21:58
WhenChangedUTC : 28/11/2019 13:38:37
WhenCreatedUTC : 28/11/2019 12:21:58
OrganizationId :
Id : SERVEREXCHANGE\EWS (Default Web Site)
OriginatingServer : DOMAINCONTROLLER.gruppozenit.com
IsValid : True
ObjectState : Changed- Dec 23, 2020
Hi angeloforum,
The configuration seems correct or some issue that is not explicit. If that command does not resolve the problem, I suggest opening a support ticket.
Best Regards,
Nuno Árias Silva
Office Apps and Services
https://www.nuno-silva.net- HaniGhaddafApr 15, 2021Copper Contributor