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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-02T14:19:19+00:00

    Hello, we have also been having issues with PST import since last week with the same error in the logs. It is still not working for us and we have raised a case with Microsoft, but very slow progress so far. We also have one import job which has been stuck since the issues started and I can find no way to delete or clear the job. I have tried with powershell commands below, anyone else had this and managed to clear a stuck job?

    Get-MailboxImportRequest -BatchName batch_name | Suspend-MailboxImportRequest

    Get-MailboxImportRequest -BatchName batch_name | Remove-MailboxImportRequest

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-02T15:46:14+00:00

    Despite a couple of people saying that it's working for them, it's still broken here.

    I tried using GUID as someone suggested. It does exactly the same thing. It hangs at 0% before eventually failing.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-02T18:56:53+00:00

    Yeah, definitely still broken for majority of uploads. Support tech tried to just reiterate that they thought it was reported fixed, then reported not fixed, etc.
    Odd that this isn't on public health list (at least not for me) in admin center
    I know this article has been referenced in our support request, and I assume others.

    Hey MS! Halp!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-03T00:33:46+00:00

    Microsoft has advised its a known issue and they are working on it... looks like its a global problem.. just have to seat tight.,.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-08-03T17:31:21+00:00

    Estimad@s, en nuestro caso el problema ya estaría resuelto, voy por el segundo movimiento con éxito.

    Saludos

    Was this answer helpful?

    0 comments