none
FAILING EX2007 Mailbox to EX2010 database EVENT ID 1100 - Single Mailbox

    Question

  • Hello all,<o:p></o:p>

    I have a single mailbox thus far that is failing migration.  The error below mentions deleted items, I deleted all items in the deleted items and in the dumpster yet still get this error, any ideas?  She has no rules and used skip corrupted messages which she did have.

    Request 'xxxxxxx.xxx/xxx Users and Computers/User Accounts/xxxx/Username Here' (e0037727-1b24-4cae-a1ea-7c2f6d87184e) failed.
    Error code: -2147024809
    MapiExceptionInvalidParameter: Unable to modify table. (hr=0x80070057, ec=-2147024809)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=192]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=660][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropModifyRules [65]
        Lid: 17082   ROP Error: 0x80070057
        Lid: 27745  
        Lid: 21921   StoreEc: 0x80070057
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 1238    Remote Context Overflow
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67870102
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67F60040
        Lid: 48851  
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67F60040
        Lid: 51077   dwParam: 0x80000000
        Lid: 65267  
        Lid: 40691  
        Lid: 5559    StoreEc: 0x80070057
        Lid: 65015  
        Lid: 65439  
        Lid: 4302    StoreEc: 0x80070057
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x80070057
        Lid: 29150  
        Lid: 20446   StoreEc: 0x80070057
    Context:
    --------
    Operation: IDestinationFolder.SetRules
    OperationSide: Target
    Primary (e0037727-1b24-4cae-a1ea-7c2f6d87184e)
    Rules: [Rule: Condition: none; Actions: [RuleAction: OOFREPLY TemplateEID:[len=70, data=00000000EC994D5FA176CC44B53C81E9B9D2BC7407002C7B7A4D7DE62A46BC2EFB70D3ABF93200000083D24F00002C7B7A4D7DE62A46BC2EFB70D3ABF9320000008588B50000], TemplateGuid:3479ea57-ca6b-4330-b5c6-57b8969c1ddd, Flags:0]; Name ''; Provider: 'MSFT:TDX OOF Rules'; ProviderData: ; ExecutionSequence: 50; Level: 0; StateFlags: 13; UserFlags: 2; IsExtended: False]
    --------
    Folder: '/Top of Information Store/Deleted Items', entryId [len=46, data=00000000EC994D5FA176CC44B53C81E9B9D2BC7401002C7B7A4D7DE62A46BC2EFB70D3ABF93200000083D2520000], parentId [len=46, data=00000000EC994D5FA176CC44B53C81E9B9D2BC7401002C7B7A4D7DE62A46BC2EFB70D3ABF93200000083D24C0000]

    Tuesday, June 12, 2012 12:16 PM

Answers

  • 1.Usually these problems comes from a light corruption within user mailbox, mainly due to Out of Office or Mailbox rules corruption. In several cases if mailbox is moved to other database problem corruption is fixed during this movement process but Exchange 2010 could not allow that movement. Please, try to move these mailboxes to a different Exchange 2007 database and then move it again to Exchange 2010 Mailbox Server.  If problem is other than rule corruption then we can check database integrity with ISINTEG tool.

    2.Based on my research, the movement might be interrupted by some corrupted or hidden rules in this user’s mailbox. So we need to delete corrupted and hidden rules before move it. For detailed steps, please refer to following KB article:
    ==========
    How to delete corrupted and hidden rules from a single mailbox in Outlook 2003
    http://support.microsoft.com/kb/924297

    • Marked as answer by GabooN Wednesday, June 13, 2012 1:26 PM
    Tuesday, June 12, 2012 5:56 PM

All replies

  • 1.Usually these problems comes from a light corruption within user mailbox, mainly due to Out of Office or Mailbox rules corruption. In several cases if mailbox is moved to other database problem corruption is fixed during this movement process but Exchange 2010 could not allow that movement. Please, try to move these mailboxes to a different Exchange 2007 database and then move it again to Exchange 2010 Mailbox Server.  If problem is other than rule corruption then we can check database integrity with ISINTEG tool.

    2.Based on my research, the movement might be interrupted by some corrupted or hidden rules in this user’s mailbox. So we need to delete corrupted and hidden rules before move it. For detailed steps, please refer to following KB article:
    ==========
    How to delete corrupted and hidden rules from a single mailbox in Outlook 2003
    http://support.microsoft.com/kb/924297

    • Marked as answer by GabooN Wednesday, June 13, 2012 1:26 PM
    Tuesday, June 12, 2012 5:56 PM
  • Hi GabooN

    Mohammed is correct, it is caused by OOF rule.

    As the link he provided above, it suggest us using MFCMAPI to delete this user’s OOF rule. Please confirm that

    • Use an Administrative account with "Edit" permissions on all mailboxes.
    • Make sure that the Outlook Profile you use is set for 'On Line Mode'
    • Obtain the latest MFCMAPI version from HTTP://www.codeplex.com/mfcmapi

    Then follow Mohammed's KB link and your issue might be solved.

    Cheers


    Zi Feng

    TechNet Community Support

    Wednesday, June 13, 2012 7:59 AM
    Moderator
  • 1.Usually these problems comes from a light corruption within user mailbox, mainly due to Out of Office or Mailbox rules corruption. In several cases if mailbox is moved to other database problem corruption is fixed during this movement process but Exchange 2010 could not allow that movement. Please, try to move these mailboxes to a different Exchange 2007 database and then move it again to Exchange 2010 Mailbox Server.  If problem is other than rule corruption then we can check database integrity with ISINTEG tool.

    2.Based on my research, the movement might be interrupted by some corrupted or hidden rules in this user’s mailbox. So we need to delete corrupted and hidden rules before move it. For detailed steps, please refer to following KB article:
    ==========
    How to delete corrupted and hidden rules from a single mailbox in Outlook 2003
    http://support.microsoft.com/kb/924297

    I read another post about this and it didn't fix that person's issue so I didn't try it, however in my case it did work.

    THANKS!

    Wednesday, June 13, 2012 1:27 PM