PST Capture Import to Exchange Online (Office365) - RPC Unavailable RRS feed

  • Question

  • I am trying to use PST Capture to import PST's into Office365 Exchange Online.  Each time the import starts and crashes shortly after with an RPC Server Unavailable error.  I have tried different machines, networks and anything else I can think of.  The error is:

    Import Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
    Folder IPM_SUBTREE\Calendar.

    If I turn off importing Calendar items it just crashes in the Inbox instead.

    When the tool crashes an Application fault is registered in the App log on the host computer.  After this the PST import cannot be restarted, (Error Opening PST), and I have to reboot the server to try again.

    Had anyone got this to work?  I see others have had similar issues but there are no concrete steps to resolve. (See http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/b2ae6730-0723-4784-a947-158b7782c7fc)

    Any help would be much appreciated as this is critical to our deployment.


    Tuesday, March 20, 2012 2:17 PM

All replies

  • Hi Chris,

    Please try to disable the firewall and anti-virus application first if you didn't do that.

    I'm researching the issue and will update it soon.

    By the way, you can also try to seek the solution in the 3rd Party Applications forum:


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Frank Wang

    TechNet Community Support

    Wednesday, March 21, 2012 7:09 AM
  • Try the below links out and see if it resolve your problem.



    Wednesday, March 21, 2012 8:21 AM
  • Thanks for the replies.

    I can confirm that I have tried this on multiple machines, with and without AV or Firewall and there is no difference.  I have also tried from corporate and home networks to rule out perimeter firewall issues.

    I'm afraid the link provided by Girishp just talks about importing the PST's via Outlook, not sure how that is a relevant solution to a problem with PST Capture.

    Any other help or suggestions would be welcome.  I am trying the MessageOps tool as an alternative so will let you know how that goes.

    As a side issue has anyone seen a report of someone actually getting this to work?  I can only find negative reports so far.



    Wednesday, March 21, 2012 9:37 AM
  • Hey Chris,

    I had the same problem like you but i was doing it on premiss.

    I moved most of my company PST's using the shell command  and only one mailbox kept failing so i decided to try it with PST Capture and got the error. I can say that bigger mailboxes when fine using PST Capture and only this one fails on both GUI and CLI.

    My advice to you is to try and see if you can import it into a local Exchange.
    Also you can try and ScapPST the file.

    Wednesday, March 28, 2012 2:05 PM
  • Hello Chris,

    I have tried the PST capture tool and it works without any issues, most of the item it could be beacuse of the network  or any corrupted item.



    Monday, May 14, 2012 5:45 AM
  • Hi guys,

    I'm trying to upload to Office 365 and I'm receiving the same error(s) - the RPC error followed by the 'Error opening PST' error and have tried on multiple OSes (Win 8 Consumer Preview, Win7, Server 2K8 R2) and multiple network connections (via proxy, straight to the internet) with the same result. I have to kill the PSTCapture Console service and restart it to be able to 'attempt to' upload any other PST files.

    Using ScanPST it shows there are errors in the PST files, even after a repair. The odd thing is that 2 of the PSTs (with errors in them as well) were uploaded ok. I haven't been able to upload any others.

    This is really frustrating and is delaying multiple projects.. the manual upload process just takes too long (via outlook client)

    Are there any detailed logs that I can look at?


    Monday, May 28, 2012 10:09 PM
  • I too have been struggling with this trying to upload PSTs to O365, but I have a really good explanation and answer now finally.  I hope people find this valuable.  This would apply to both on-premises and O365.

    PST Import fails with RPC Server Unavailable Error.

    The Log shows a folder that caused the failure.

    Problem:  The PST Folder contains a message that triggers the Anti-Virus system to block it.  Phishing emails are perfect examples of this.  Forefront will catch and block emails that contain phishing links/content.

    Cause:  A user most likely archived email messages based on dates.  A phishing email that was laying around ignored flowed into the PST.  *OR* The user works in IT and had examples of phishing emails that were archived as part of a project/things they were working on.  *OR* A user opened a ticket about a phishing email and the ticketing system emailed them a summary of the ticket that contained the text from the phishing email in the body.

    Solution:  Delete the phishing emails out of the PST and run again.

    • Proposed as answer by SSall Thursday, June 7, 2012 9:06 PM
    Thursday, June 7, 2012 9:06 PM
  • I have found that if I receive the error:

    Import Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
    Folder IPM_SUBTREE\Calendar.

    I need to remove the check box in the upload tool for non-mail items. The tool can upload the Mail items fine, but if I try to upload any of the non-mail items I have an RPC error and a failure.

    Thursday, June 7, 2012 9:16 PM
  • There is a separate issue for Calendar folders where the type is stamped incorrectly in the PST.  Fixing it will allow it to import correctly.  *OR* the user works in IT and has a phishing email referenced in a meeting invite.
    Thursday, June 7, 2012 9:31 PM
  • To fix the issue where Calendar folders are stamped incorrectly, does it require recreation of the Calendar in the PST?

    Thursday, June 7, 2012 9:56 PM