This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 features that help users manage their subscriptions, account settings, and billing information.
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.
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.
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
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
seems to be working again, for me at least!
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.