none
Public Folder Migration Fails RRS feed

  • Question

  • I am trying to migrate public folders from Exchange 2010 to Exchange online. The migration fails with this error

    MapiExceptionBadValue: Unable to synchronize manifest. ‎(hr=0x80040301, ec=-2147220735)‎ 

    Most posts seem to indicate this is something wrong with inbox rules, but there are no mail enabled public folders

    We also see this error in the windows event log

    A problem occurred while getting the properties for the automatic reply message from <NULL>, Error code: -2147221233
    Try to clear the rules or run ISINTEG to check for any problem in the database "Public Folder Database"

    I have a copy of the public folder database running on a different Exchange server, but when I try and run ISINTEG against it the store process crashes.

    How do I identify where the issue is in this db so we can migrate the public folders?

    Tuesday, September 3, 2019 2:05 PM

All replies

  • Hi,

    How do you migrate public folders?

    Do you have a hybrid environment? Can you provide more details about your environment? 

    Please make sure your Exchange version is Exchange 2010 SP3 RU8 or later, and here is a document about migrating public folders to Exchange Online, hope these steps work for you: Use batch migration to migrate legacy public folders to Office 365 and Exchange Online

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 4, 2019 6:54 AM
    Moderator
  • Yes a hybrid is in place, all user mailboxes have been migrated. There is a single Exchange server and it is later than RU8.

    The migration is being done using the batch method, we see the first error I posted in the mailbox migration batch status.

    Wednesday, September 4, 2019 7:58 AM
  • Hi,

    You can use the following command to check the migration with more details:

    Get-MigrationBatch -Identity "<Migration Batch name>" -IncludeReport

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 6, 2019 9:51 AM
    Moderator
  • Use batch migration to migrate Exchange 2010 public folders.

    Through a process known as batch migration, you can move some or all of your Exchange 2010 public folders to Office 365 Groups. Groups is a new collaboration offering from Microsoft that offers certain advantages over public folders.

    - The Exchange 2010 server needs to be running Exchange 2010 SP3 RU8 or later.
    - In Exchange Online, you need to be a member of the Organization Management role group. This role group is different from the permissions assigned to you when you subscribe to Office 365 or Exchange Online. For details about how to enable the Organization Management role group.
    - Only public folders of type calendar and mail can be migrated to Office 365 Groups at this time; migration of other types of public folders is not supported. Also, the target groups in Office 365 are expected to be created prior to the migration.
    - The batch migration process only copies messages and calendar items from public folders for migration to Office 365 Groups. It doesn't copy other entities of public folders like policies, rules and permissions.
    - You must use a single migration batch to migrate all of your public folder data. Exchange allows creating only one migration batch at a time. If you attempt to create more than one migration batch simultaneously, the result will be an error.

    --
    Jon

    Friday, September 6, 2019 11:50 AM
  • I have already got that report, it gives less detail the you can see the portal. The only error is 

    Transient error MapiExceptionBadValue has occurred

    Friday, September 6, 2019 2:36 PM
  • Does anyone have any ideas about what this error means?

    MapiExceptionBadValue: Unable to synchronize manifest. ‎(hr=0x80040301, ec=-2147220735)‎ 

    Monday, September 9, 2019 9:51 AM
  • If it's convenient for you, you can post the screenshot or copy the report in the reply, and please don't forget to cover your personal information. 

    You also can check the Event Viewer. Some related event logs may be generated.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 11, 2019 10:05 AM
    Moderator
  • As mentioned in my first post, we see this error in the event log

    Event ID 8533
    MSExchangeIS Mailbox Store
    A problem occurred while getting the properties for the automatic reply message from <NULL>, Error code: -2147221233
    Try to clear the rules or run ISINTEG to check for any problem in the database "Public Folder Database"

    This is the full text from the error, the report does not give any more detail

    Error: MigrationMRSPermanentException: Error: The job encountered too many transient failures ?(601)? and is quitting. The most common failure is MapiExceptionBadValue with the hit count 60. --> 
    MapiExceptionBadValue: Unable to synchronize manifest. ?(hr=0x80040301, ec=-2147220735)? 
    Diagnostic context: 
    Lid: 35250 
    Lid: 36674 dwParam: 0x9C 
    Lid: 61250 dwParam: 0x0 
    Lid: 45378 dwParam: 0x2 
    Lid: 44866 dwParam: 0xD 
    Lid: 40487 
    EMSMDBMT.EcDoRpcExt2 called [length=49] 
    Lid: 56871 EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=4726][latency=867] 
    Lid: 52176 ClientVersion: 15.20.2073.0 
    Lid: 50032 ServerVersion: 14.3.419.0 
    Lid: 35180 
    Lid: 23226 
    --- ROP Parse Start --- 
    Lid: 27962 ROP: ropFXSrcGetBufferEx [156] 
    Lid: 31418 
    --- ROP Parse Done --- 
    Lid: 30945 
    Lid: 35180 
    Lid: 23226 
    --- ROP Parse Start --- 
    Lid: 27962 
    ROP: ropFXSrcGetBufferEx [156] 
    Lid: 31418 
    --- ROP Parse Done --- 
    Lid: 30945 
    Lid: 35180 
    Lid: 23226 
    --- ROP Parse Start --- 
    Lid: 27962 ROP: ropFXSrcGetBufferEx [156] 
    Lid: 17082 
    ROP Error: 0x80040301 
    Lid: 23137 
    Lid: 21921 StoreEc: 0x80040301 
    Lid: 27962 ROP: ropExtendedError [250] 
    Lid: 1494 
    ---- Remote Context Beg ---- 
    Lid: 1238 Remote Context Overflow 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x3FE884B0 
    Lid: 31473 StoreEc: 0x8004010F 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x65E00102 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x65E00102 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x65E20102 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x65E30102 
    Lid: 14164 StoreEc: 0xFFFFFA1D PropTag: 0x67300014 
    Lid: 8660 StoreEc: 0x8004010F PropTag: 0x67300014 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67300014 
    Lid: 1635 StoreEc: 0x8004010F 
    Lid: 23921 StoreEc: 0x3EC 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 
    Lid: 23921 StoreEc: 0x3EC 
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x66C40003 
    Lid: 14164 StoreEc: 0xFFFFFA1D PropTag: 0x67300014
    Lid: 8660 StoreEc: 0x8004010F PropTag: 0x67300014
    Lid: 14164 StoreEc: 0xFFFFFA1D PropTag: 0xE080003
    Lid: 8660 StoreEc: 0x8004010F PropTag: 0xE080003
    Lid: 49605 StoreEc: 0x3EE
    Lid: 14164 StoreEc: 0xFFFFFA1D PropTag: 0x360A000B
    Lid: 8660 StoreEc: 0x8004010F PropTag: 0x360A000B
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67600003
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67A90002
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67A90002
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x65EE0102
    Lid: 43747 dwParam: 0x4A
    Lid: 55653 StoreEc: 0x8004010F
    Lid: 18208 StoreEc: 0x8004010F
    Lid: 6432 StoreEc: 0x80040301
    Lid: 7008 StoreEc: 0x80040301
    Lid: 7183 StoreEc: 0x80040301
    Lid: 22208
    Lid: 24320 StoreEc: 0x80040301
    Lid: 22384
    Lid: 2238 StoreEc: 0x80040301
    Lid: 20888
    Lid: 24504 StoreEc: 0x80040301
    Lid: 24148 StoreEc: 0x80040301
    Lid: 23796
    Lid: 2478 StoreEc: 0x80040301
    Lid: 1750 ---- Remote Context End ----
    Lid: 31418 --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817 ROP Failure: 0x80040301
    Lid: 32758
    Lid: 16586 StoreEc: 0x80040301
    Lid: 22518
    Lid: 28874 StoreEc: 0x80040301
    Lid: 29516
    Lid: 31820 StoreEc: 0x80040301


    Wednesday, September 11, 2019 11:33 AM
  • What error did you get when run ISINTEG to check and fix the public folder database?

    How large is your public folder?

    If the public folder hierarchy is not greater than 30 GB, you can use Outlook's PST export feature to migrate public folders to Exchange Online. For reference: Migrate Public Folders to Office 365 by using Outlook PST export

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 13, 2019 9:11 AM
    Moderator
  • The public folders are 160Gb in total, but no folder is over 6Gb.

    The error I get when I try and run ISINTEG is 

    Faulting application name: store.exe, version: 14.3.442.0, time stamp: 0x5c3d0d7e

    Faulting module name: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea1bbd
    Exception code: 0xc0000005
    Fault offset: 0x000000000001e293
    Faulting process id: 0x6d0
    Faulting application start time: 0x01d55f37cfbcd025
    Faulting application path: C:\Program Files\Microsoft\Exchange Server\V14\bin\store.exe
    Faulting module path: C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_08e793bfa83a89b5\MSVCR90.dll
    Report Id: 321f2e10-cb2c-11e9-80c1-000d3a287473
    Faulting package full name: 
    Faulting package-relative application ID: 

    Friday, September 13, 2019 12:45 PM
  • Did any users create rules in public folders?

    It should be checked and cleaned at first. Right click the public folder > Properties > Folder Assistant:

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 18, 2019 11:03 AM
    Moderator
  • There are 8000 folders, how would I find any rules without doing that for every public folder?
    Wednesday, September 18, 2019 11:17 AM
  • You can check with the following command to make sure where the rules are set:

    Get-PublicFolder -recurse -Identity \ -resultsize unlimited | where-Object {$_.HasRules -eq "True"}| fl Name, HasRules

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 20, 2019 9:37 AM
    Moderator
  • Finally, this is what I have been after since this case started. I have run that, it identified 5 folders with rules. I then looked at the folder assistant properties and there aren't any rules. Can I just change the HasRules property with PowerShell?
    Monday, September 23, 2019 9:55 AM
  • Looks like I can't clear with PowerShell and I have tried using ExFolders to change the value and also to clear PR_RULES_DATA but I don't seen to be able to. How can I change these values?

    thanks

    Monday, September 23, 2019 12:12 PM
  • Hi,

    Try to use MFCMAPI tool to find and delete the hide rule in public folders. Find the IPM.Rule.Message object and delete it. You can check this blog for detailed steps: How to delete corrupted hidden Exchange inbox rules using MFCMAPI

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, September 26, 2019 8:56 AM
    Moderator
  • Does MFCMAPI tool work for you?

    If there is anything else we can do for you, please feel free to post in the forum.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, October 3, 2019 8:57 AM
    Moderator
  • We gave up on trying to fix the corruption and the MS batch migration process. We just migrated the folders using PST export and import instead.
    Thursday, October 3, 2019 11:29 AM
  • That's OK. Thanks for your sharing.

    Anyway, it's great that you have migrated the public folders. If you have any other issues, please feel free to post in our forum.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, October 4, 2019 12:54 AM
    Moderator