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 No comments

45 answers

Sort by: Newest
  1. Anonymous
    2022-08-02T12:38:50+00:00

    Also here it seems that something is being moving.
    The new behavior I'm facing is that even if I submit a batch with 20 (or 50) import requests, only 6 will be really processed...others still fail with the same error as before.
    From PS there is no clue of them. The only way get some evidence of failed request is to download the log from the Compliance Portal

    so better, but not well

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-08-02T10:39:49+00:00

    seems to be working again, for me at least!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-08-02T08:30:34+00:00

    So I logged a ticket with Microsoft for this last week as we had the same issue on various M365 tenants in both the EU and South Africa region. We collected a whole lot of data and a bug fix was logged with the PG.

    Today I was informed that a worldwide fix was deployed, I am retesting my import to see if it works now.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-08-02T07:56:40+00:00

    We've had this bug while doing a cutover migration with PST import over the azcopy Tool and we've found that using the Mailbox GUID instead of the SMTP Address in the csv file is a functioning workaround!

    You can get the GUIDs of the existing Exchange Online Mailboxes with the Cmdlet Get-Mailbox | ft GUID, alias

    At least in our small migration of 18 Mailboxes this has worked nicely for all of them.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. 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 No comments