locked
Exchange 2003 to 2010 Migration Error RRS feed

  • Question

  • I've successfully moved about 150 mailboxes from a 2003 Exchange Server to a DAG Mailbox Database under 2010.  Although there were occasional challenges to getting this completed, we managed to get all mailboxes moved with the exception of one.  The error we're receiving is shown below and apparently does not have anything to do with the normal corrupted items that are encountered often.

    I've searched throughout the net with no lock in finding this particular error. 

    Does anyone have an idea of how to resolve this?  (short of simply exporting the mailbox and recreating it under 2010.)

    Thanks,

    Jim

     

    5/28/2011 11:32:06 AM [BUREX01] Stage: LoadingMessages. Percent complete: 20.
    5/28/2011 11:32:07 AM [BUREX01] Fatal error MapiExceptionNotFound has occurred.
    Error details: MapiExceptionNotFound: Unable to query table rows. (hr=0x8004010f, ec=-2147221233)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=88]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=69][latency=15]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetContentsTable [5]
        Lid: 27962   ROP: ropSetColumns [18]
        Lid: 27962   ROP: ropQueryRows [21]
        Lid: 17082   ROP Error: 0x8004010F
        Lid: 17153 
        Lid: 21921   StoreEc: 0x8004010F
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753 
        Lid: 21817   ROP Failure: 0x8004010F
        Lid: 28414 
        Lid: 32510   StoreEc: 0x8004010F
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiTable.QueryRows(Int32 crows, QueryRowsFlags flags)
       at Microsoft.Mapi.MapiTable.QueryAllRows(Restriction restriction, ICollection`1 propTags)
       at Microsoft.Exchange.MailboxReplicationService.LocalFolder.<>c__DisplayClass3.<Microsoft.Exchange.MailboxReplicationService.IFolder.EnumerateMessages>b__0()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.LocalFolder.Microsoft.Exchange.MailboxReplicationService.IFolder.EnumerateMessages(EnumerateMessagesFlags emFlags, PropTag[] additionalPtagsToLoad)
       at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.IFolder.EnumerateMessages>b__6()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.Microsoft.Exchange.MailboxReplicationService.IFolder.EnumerateMessages(EnumerateMessagesFlags emFlags, PropTag[] additionalPtagsToLoad)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass41.<LoadFolderMessages>b__40()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.LoadFolderMessages(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: MapiFolder.GetContentsTable
    Flags: DeferredErrors
    --------
    Operation: IFolder.EnumerateMessages
    OperationSide: Source
    Primary (afcf12ff-66b5-44e6-8130-c7ec300ac1d8)
    Flags: AllMessages, IncludeExtendedData
    PropTags: (null)
    --------
    Mailbox: Primary (afcf12ff-66b5-44e6-8130-c7ec300ac1d8)
    Folder: '/Top of Information Store/Drafts', entryId [len=46, data=0000000091881EBA92A6D311862500A0C9E7EF6E0100C86B158C25A4D21185F700A0C9E7EF6E000001F997C30000], parentId [len=46, data=0000000091881EBA92A6D311862500A0C9E7EF6E0100C86B158C25A4D21185F700A0C9E7EF6E000001FA89380000]
    5/28/2011 11:32:07 AM [BUREX01] Removing target mailbox 'Primary (afcf12ff-66b5-44e6-8130-c7ec300ac1d8)' due to an offline move failure.
    5/28/2011 11:32:07 AM [BUREX01] Relinquishing job.

     

    Tuesday, May 31, 2011 10:14 PM

Answers

  • Hi,

    This error could be caused by the corrupted database in the mailbox.

    Please try the following steps:

    1. Grant the full access permission of this special mailbox for your account.

    2. In exchange 2003, create a temp database, move this mailbox to this new database. Then move it to exchange 2010.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT
    • Marked as answer by Jim in IT Friday, June 3, 2011 12:59 AM
    Thursday, June 2, 2011 7:27 AM

All replies

  • When you are getting this error? When moving the Mailbox or Exporting the Mailbox?

    Restart MS Exchange System Attendant Service and try again.

    If it happens on Move Mailbox, than is it happening to one user only or multiple?


    Gulab | MCITP: Exchange 2010 | MCITP: Exchange 2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    Wednesday, June 1, 2011 6:16 AM
  • Hi Gulab, 

    Thanks for the reply.  The error is occurring at 20% through the move of the mailbox although the exception message is not clear on exactly what it is doing at the time of the error.

    The error occurs only on one mailbox.  It is actually the only mailbox left to be moved - the rest have been successfully moved to 2010.

    - Jim

    Wednesday, June 1, 2011 9:28 PM
  • Have you tried to select "skip the corrupted messages" option in the moving mailbox wizard? Give that a go and let us know.
    Thursday, June 2, 2011 12:23 AM
  • Hi,

    This error could be caused by the corrupted database in the mailbox.

    Please try the following steps:

    1. Grant the full access permission of this special mailbox for your account.

    2. In exchange 2003, create a temp database, move this mailbox to this new database. Then move it to exchange 2010.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT
    • Marked as answer by Jim in IT Friday, June 3, 2011 12:59 AM
    Thursday, June 2, 2011 7:27 AM
  • Hi Gen,

      Thanks for the suggestion.  I'll give it a try and post the results.  Should this not resolve it, I'll simply export the mailbox, delete it on 2003, create a new one on 2010 and import the mail.

     - Jim


    Best, Jim
    Thursday, June 2, 2011 5:39 PM
  • Hi Michael,

    Yes, I have set the "Skip Corrupted Message" flag and set the limit to 35.  The error does not appear to be originating from corrupted messages since there are none logged in the log file.

     

    - Jim

     

     


    Best, Jim
    Thursday, June 2, 2011 5:41 PM
  • Hi Gen,

    Thanks for the suggestion of moving to another store in Exchange 2003.  Although I did not create a new temporary store, by moving the mailbox to another store under 2003 then moving it to 2010, it worked!

     

    Thanks for your help!

     


    Best, Jim
    Friday, June 3, 2011 1:01 AM