Wednesday, March 8, 2017

Attempting to export a mailbox to PST from the Exchange Server 2013 ECP throws the error: “The call to ‘net.tcp:// (15.0.1178.0caps:1FFF)’ timed out. Error details: This request operation sent to ‘net.tcp://…”


You attempt to export a user’s mailbox to PST via the Exchange 2013 ECP console but receive the following error:

The call to

‘net.tcp:// (15.0.1178.0caps:1FFF)’ timed out. Error details: This request operation sent to ‘net.tcp:// 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 becase 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’ve had clients call me about this error message in the past and most of them would have Google-d the error and come across the following KB:

Mailbox import or export fails in Exchange Server 2010

Many other forum posts also suggests the two updating the RpcClientAccessServer to point to one of the CAS servers but if an attempt was made to do that with the cmdlet:

Set-MailboxDatabase “Mailbox Database Name” -RpcClientAccessServer

… you’ll quickly notice that this cmdlet no longer exists and the only way to change this attribute is to use ADSIedit.

What I’ve noticed is that there have been plenty of times where the above KB does not apply so prior to going down the route of either creating a host record or adjusting the RpcClientAccessServer variable, check to ensure that the path specified in the following step for the export is correct:

Export to a .pst file

*Specify the path to export the .pst file to (example: \\server\folder\ExportFile01.pst)


The error message above could also be thrown if you specify a path that is not reachable.


Anonymous said...

Thank you!!! A typo in the filepath was my problem!! (Forgot "c$" in the path)
You saved me from doing a lot of un-necessarry stuff!

Anonymous said...


agent_buzz said...

This happened to us because the name of the mailbox was wrong in the PowerShell command. It was being typed as "Joe User" instead of "User, Joe". The samAccountName would have worked, too. Thanks for the article.