Hi ,

I am currently testing a cross forest migration from exchange 2007 to exchange 2013. i do not have trust between my forest but i did set up conditional forwarding in both the source and target environment.

The Mailbox replication service does not behave as expected when i submit a new move request.

the move request : New-MoveRequest -Identity "f2867850-5e88-4f97-9efb-0b867a1fdb4b" -BadItemLimit "10" -TargetDeliveryDomain "TargetDomain" -TargetDatabase "{cbc90e5e-6124-458c-8105-464bc27d26c1}" -RemoteCredential (Get-Credential "sourcecredential") -RemoteGlobalCatalog "FQDN of source GC" -RemoteLegacy:$true

the error : "The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."

I can ping both global catalog in the source environment and in the target from both side. nslookup and autodiscover is working as well.

MRS Proxy is enable on the exchange 2013 side and i have enable remote Powershell on both side.

i do not have any load balancer configure.

If anyone can point me in the right direction where to look it would be greatly appreciated.

thanks you

I tried to input the source EWS URL into a browser in the target exchange server.

It asked me for credential and then the browser load the https://source.exchange.fqdn/ews/services.wsdl page without error.

I did the same with the target EWS URL into the source exchange server and it did the same.

is there a better way to test this ? anything else i should look

You might check this thread:

http://social.technet.microsoft.com/Forums/en-US/279bac54-f7bd-4d5e-884e-6c8701db13cc/remote-2010-2010-crossforest-mailbox-move-timeout?forum=exchangesvrdeploylegacy

There are a lot of under-the-covers things that can cause problems with mailbox moves.

Hi,

Please refer to the following article to troubleshoot the issue:

https://blogs.technet.com/b/asiasupp/archive/2011/06/23/when-you-attempt-to-move-mailbox-from-to-exchange-online-you-receive-the-error-quot-the-call-to-microsoft-exchange-mailboxreplicationservice-timed-out-quot.aspx

To isolate the issue, you may check how it works if you increase the timeout with the following steps:

1. On the Client Access server, open the following file with a text editor such as Notepad:\ExchWeb\EWS\web.config
2. Locate the following section in the web.config file:

<!-- Mailbox Replication Proxy Server configuration -->

<MRSProxyConfiguration

IsEnabled="true"

MaxMRSConnections="100"

DataImportTimeout="00:01:00" />

Hope this helps!

Thanks.

i have looked at the web.config file and it seems to have changed with exchange 2013  , i cant find the

DataImportTimeout="00:01:00"

In the folder exchangeserver\v15\bin there is a file : MsExchangeMailboxReplication.exe.config in this file there is a section MrsProxyConfiguration with the DataimportTimeout value set to "00:01:00". I have change this value for "00:10:00" , restart the Microsoft Exchange Mailbox Replication service ,  IISreset.

result : i still have the same error with the same timeout value , maybe i am not changing this value at the right place

another test i have done : i have enter the credential in the format domain.lab/admin instead of domain/admin and strangely enough the mailbox did transfer from the source to the target but with a warning that i am not comfortable with :

The following failure occurred after the active directory modification completed : couldn't find database "SourceExchangeServer\SourceStorageGroup\SourceMailboxDatabase". Make sure you have typed it correctly ..