Use network upload to import PST files into Office

Anonymous
2022-07-26T15:47:20+00:00

During network upload, we get back the error MRSRemoteTransientError. Detail: X-Psws-ErrorCode: 841101 X-Psws Exception: Microsoft.Exchange.Net.CommunicationErrorTransientException X-Psws-Warning: When an item can't be read from the source database or it can't be written to the destination database The error occurs if you specify the UPN or GUID as the target. Via Powershell I don't see any output at Get-MailboxImportRequest. The error occurs with all PST files or with all mailboxes.

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

45 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-08-02T06:49:02+00:00

    I have the same problem and also have a case open with Microsoft, ill keep you posted on the result.

    i did also notice they still have the command new-mailboximportrequest, you need a blob storage account to get it working and its no longer supported.. but might as well try my luck while MS support is just seating on my ticket..

    does anyone have a workaround ?

    New-MailboxImportRequest -?

    NAME New-MailboxImportRequest

    SYNOPSIS This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. Use the New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive. Note : This cmdlet is no longer supported in Exchange Online. To import a .pst file in Exchange Online, see Use network upload to import PST files (https://docs.microsoft.com/microsoft-365/compliance/use-network-upload-to-import-pst-files). This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see Add a role to a role group (https://docs.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group). For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-02T06:11:06+00:00

    Hello,

    Same error for me as well.

    Troubleshooting since Friday but none of the article available for further troubleshooting.

    My migration type is PST import into O365 mailbox. Below error showing while import to PST failed.

    PFA for more detailed errors.

    MS should look into it and writeup some blogs to mitigate this.

    Regards

    Anand Sunka

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-01T18:10:40+00:00

    Por acá tenemos el mismo problema, espero se solucione pronto.

    Saludos

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-01T15:01:10+00:00

    Importing through Outlook wasn't reliable for me. We have a user with two very large PST files (30GB+ each) and it refuses to pull everything in. For example, subfolders could be missing hundreds or thousands of emails, even though it appeared that Outlook had finished the upload. If I try to upload again, it instantly finishes. If I manually import one of the single subfolders, it might grab the rest of the emails, it might not. I spent many hours battling Outlook. I was hoping that the PST upload would be my fix.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-08-01T14:41:56+00:00

    Having the same issue since 31 July 2022. Even small pst files are failing.
    Will have to import via Outlook

    Was this answer helpful?

    0 comments