Microsoft 365 and Office | Subscription, account, billing | For business | Other
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Tambien tengo el mismo problema.
Use network upload to import PST files into Office
![](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)
Anonymous
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.
45 answers
Sort by: Oldest
-
Anonymous
2022-07-30T14:37:05+00:00 -
Anonymous
2022-07-30T14:49:27+00:00 i changed a emailboxes to shared but import psts failed again
-
Anonymous
2022-07-30T16:32:53+00:00 We have the same Error. Exchange Online only some PST Imports always Fail, but always at the last step when importing to o365 from compliance portal
-
Anonymous
2022-07-31T09:05:10+00:00 We also have the same error
-
Anonymous
2022-07-31T20:34:42+00:00 Exactly the same here ,
had a scenario where cutover migration started erroring and lost its sync,
sadly MS support was unable to help me at all.
Decided to cancel the migration job and get missing few weeks of email via PST export and import instead . Worked fine the 1st round .. (9th July 2022)
Now at migration weekend to go live in the morning and I have about 100mailboxes missing couple weeks of email.
My import batch had 180 PSTs/Users, and only about 80 imported, the rest keeps failing with this same error no matter what I try :\
MS Please fix it, see this is happening "globally"