2010 to 2016 Public Folder Migration - Error: MigrationMRSPermanentException

JPoole 21 Reputation points
2021-01-10T23:23:05.28+00:00

Migrating 60gb of 2010 public folders to 2016 (on premise, 9 mailboxes). Mailboxes 2-9 show as "Synced" and mailbox 1 shows "Failed" with this error:

*Data migrated: 8.504 GB ‎(9,130,858,171 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
Error: MigrationMRSPermanentException: Error: Property expression "9598 Folder name" isn‎'t valid. Valid values are: Strings formed with characters from A to Z ‎(uppercase or lowercase)‎, digits from 0 to 9, !, #, $, %, &, ‎', , +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.

I have a pst backup of that folder so I have deleted it from the 2010 server.

How do I restart the migration so I can get to the 95% complete point?

I'm on Step 5 of this guide: https://learn.microsoft.com/en-us/Exchange/collaboration/public-folders/batch-migration-from-previous-versions?redirectedfrom=MSDN&view=exchserver-2016#step-1-download-the-migration-scripts

I tried this command ( Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest ) but it didn't seem to do anything.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,369 questions
0 comments No comments
{count} votes

Accepted answer
  1. Yuki Sun-MSFT 40,871 Reputation points
    2021-01-14T02:41:58.927+00:00

    Hi @JPoole

    Is this issue only affecting the particular public folder?
    Does the public folder name include spaces or any other potential invalid characters?

    For current situation, please try running the command below and see if there would be any difference:

    Start-MigrationBatch <MigrationBatchName>   
    

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful