Consider the following scenario:
You install Microsoft Exchange Server 2010 Service Pack 1 (SP1) or a later version.
You deploy a Client Access server (CAS) array that uses load balancing.
You run the New-MailboxExportRequest cmdlet or the New-MailboxImportRequest cmdlet.
In this scenario, the request may time out and not finish as expected. Additionally, you may receive the following error message:
The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (188.8.131.52 caps:07)' 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.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], TimeoutErrorTransientException
+ FullyQualifiedErrorId : 59EDFA88,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest
This issue can occur if the load balancing device is configured incorrectly. For example, this issue can occur if the load balancer does not let the Exchange Server where the request was created connect to the Virtual IP (VIP) for the CAS array.
To resolve this issue, verify that the following conditions are true:
The Exchange Server can connect to the load balancer as a client.
The Exchange Server can connect to the VIP for the CAS array.
To work around this issue, use one of the following methods.
Configure the RPCClientAccessServer value in the mailbox database to point to a specific CAS server.
Note This setting is read dynamically.
Create an entry in the Hosts file on the CAS servers that resolves the CAS array name to "localhost."
When a mailbox Import or Export request is created, the process is as follows.
Note The steps for an Import or Export request resemble a Move request.
The request is created on the Exchange Server on which the Windows PowerShell session is connected.
As part of the request validation, the Exchange Server connects to the MAPI on the Middle Tier endpoint. Then, the Exchange Server tries to log on to the mailbox that you want to import or export.
If validation is successful, a folder-associated items (FAI) message is created and added to a queue in the System mailbox of the database.
Note The issue that is described in the "Symptoms" section typically occurs after this step. In this issue, the request is not created as expected, and the FAI message is not created.
All instances of the Mail Replication Service (MRS) check the System mailbox periodically. If an MRS server is not specified in the cmdlet, an MRS server is randomly selected.
MRS finishes the Import or Export request and then changes the request status to "Completed."
An administrator clears the Import or Export request.
Note This step is optional
For more information about Import and Export requests in Exchange Server 2010, visit the following TechNet website:
For more information about Move requests in Exchange Server 2010, visit the following TechNet website:
For more information about how to configure the RPCClientAccessServer value in a mailbox database, visit the following TechNet website: