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.
We have also now been able to import PSTs again, Microsoft support had to clear a stuck job for us, which we couldn't delete/progress. Still not officially listed as an issue in 365 (at least for me).
i reimport all failed psts and all done (success 16 from 16 psts)
Since the message on Monday or Tuesday stating that it should be fixed worldwide,
I have been re-running the import jobs over and over about 5 times a day.
From original 100 failed, i am now down to last 20 remaining ..
It seems to be getting better as some batches at start completed as little as 2 and the best one I had so far which was my last try completed 20.
Hoping 2-3 more tries max and I will have all the emails up to date.
as mentioned in one of the previous posts, using GUID instead of UPN as target didn't make a difference for me with the error mentioned, but it did resolve other issues where report was claiming UPN is matching multiple entries. This was because i had some soft deleted mailboxes and mailusers which you can only see in PowerShell.
All the best to everyone, hopefully eventually you all manage to get all the needed imports done!
Any news for this problem ?
Same problem here migrating PST to M365.
I send 18 PST correctly but 6 are failing with same error, hangs at 0% before failing.