Troubleshoot PST Export in 365 Command

The PST Export functionality in 365 Command will allow to easily export 365 Command mailboxes. While there are some limitations on the number of connections.  The limitations are:

  • 10 Mailboxes per week
  • 1 Mailbox per time
  • The Admin account specified must have a mailbox associated with it. A kiosk license will not work.
  • By default all mailboxes will be kept on the server for 2 weeks

While it is anticipated that these restrictions will be removed, it’s important for us to keep track of how many people are using this feature.

There are several reasons why this can fail.

  1. That given timing issues caused by replication happening on the Server side could be an issue so manually assign Full Mailbox Access may be necessary is some rare cases. For the most it should work, but we have seen intermittent type issues in the past.
  2. How large is the Mailbox you’re exporting depending on the Mailbox content the PST file will get large.  Large number of items create PST bloat which means the PST will be a lot larger than the size of the Mailbox.

  3. Folder corruption in the Mailbox could cause the export to fail, this can be hard to fix and identify you need to look at the Exports log to work out which folder is the problem. To fix this problem may involve renaming (or giving a folder a name if its blank) or normalizing the illegal folder name. Worse case if you have mailbox corruption you may need to use MFCMapi to connect to the Mailbox to clear the corrupted folder.

  4. If there was a failure was there a corresponding outage in Office 365 any Exchange Online outage can cause the export to fail.

  5. If there was there a network outage in the network that is hosting the 365 Command servers.

Other MAPI / EWS issues from the log


  1. Invalid Items causing the EWS find Item request to fail – this can be hard to fix in the Migrator we have the option of doing a MAPI only export which means the Items are listed using MAPI rather than EWS.
  2. IMAPIFolder.GetContentsTable MAPI_E_NETWORK_ERROR – This generally indicates some form of Network failure eg the link has dropped for a period of time, this is a DNS issue. The other thing that can cause this issue is throttling as the sever is restricting access to the user account that has exceeded the quota.
  3. Issues with the Export PST – on rare occasions you could get issues when the copying in of the data during the Export causes the PST to corrupt. In this case you just need to retry the export.
  4. IMAPIFolder.GetContentsTable: MAPI_E_CALL_FAILED – This error indicates the particular Item request has failed. This may be due to underlying connectivity so hopefully during the retry phase it will be successful. If the first batch call failed and retry gives this error it maybe there is a server side issue with that particular Item or possibly just a retry is needed when connectivity/throttling issues resolve.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0
    Steve Wales

    I don't see this error addressed anywhere in knowledgebase:

    ExportId : 4474168d-56bf-4e15-a91c-d377a2b9214e
    Mailbox :
    Start Export : 12/11/2014 11:05:53 PM
    Checking Mailbox Permissions for Export Account
    Check to ensure EWS and MAPI are enabled
    CAS Mailbox EWS setting : True
    CAS Mailbox MAPI setting : True
    Adding permissions for user
    Made unique file name
    Connected to CAS Server :
    Permissions error rights added but may not yet have applied will wait 15 minutes and try again
    Cas Version : 15.01.0031.017
    Logon Status True
    Problems processing Mailbox Error in IMAPISession::OpenMsgStore: MAPI_E_LOGON_FAILED
    Make sure your code runs under the Windows user identity that has MAPI profiles.
    When running in a service (including ASP under IIS), set your code to run under
    the Windows user account that has MAPI profiles.
    When connecting to an Exchange Server, you can also use RDOSession.LogonExchangeMailbox
    which does not require an existing profile.
    ulVersion: 0
    Error: The information store could not be opened.
    Component: MAPI 1.0
    ulLowLevelError: 0
    ulContext: 646

  • 0
    James Snyder

    I would love to see Steve's error addressed.  I'm having the same issue.

  • 0

    I have the same error as Steve Wales  even though I have global admin access and our autodiscover works.
    When I raised a support ticket with Kaseya , they redirected me to this page!

Please sign in to leave a comment.