locked
move mailbox with 80004005-0000-00000000 and Error code: 0x4ed.

    Question

  • Hey Folks,

    I tried to move (migrate) a mailbox from 2k3 SP2 to 2010 SP3 but I couldn't because MAPI error.
    Right, I tried to move that mailbox from the original store to another store on the same
    2k3 SP2 server but I got these errors in this order:

    Event Type:    Error
    Event Source:    MSExchangeIS Mailbox Store
    Event Category:    Move Mailbox
    Event ID:    8505
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
    Unable to move mailbox [mailbox name].
     A problem occurred while getting the properties for a folder.
     Folder name: Inbox; Error code: 0x4ed.
     Run ISINTEG to check for any problem in the database "[Store name]".

    Event Type:    Error
    Event Source:    MSExchangeIS Mailbox Store
    Event Category:    Move Mailbox
    Event ID:    8507
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
    Unable to move mailbox [mailbox name].
     A problem occurred while getting the properties for a message.
     Parent folder name: Views; Message subject: Messages; Error code: 0x4ed.
     Run ISINTEG to check for any problem in the database "[Store name]".

    Event Type:    Error
    Event Source:    MSExchangeIS Mailbox Store
    Event Category:    Move Mailbox
    Event ID:    8505
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
    Unable to move mailbox [mailbox name].
     A problem occurred while getting the properties for a folder.
     Folder name: Inbox; Error code: 0x4ed.
     Run ISINTEG to check for any problem in the database "[Store name]".

    Event Type:    Error
    Event Source:    MSExchangeIS Mailbox Store
    Event Category:    Move Mailbox
    Event ID:    8507
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
    Unable to move mailbox [mailbox name].
     A problem occurred while getting the properties for a message.
     Parent folder name: Views; Message subject: Messages; Error code: 0x4ed.
     Run ISINTEG to check for any problem in the database "[Store name]".

    Event Type:    Error
    Event Source:    MSExchangeAdmin
    Event Category:    Move Mailbox
    Event ID:    9172
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
     Failed to copy messages to the destination mailbox store.
     Error: The MAPI call failed.
     MAPI or an unspecified service provider.
     ID no: 80004005-0000-00000000

    Event Type:    Error
    Event Source:    MSExchangeAdmin
    Event Category:    Move Mailbox
    Event ID:    1008
    Date:        5/9/2013
    Time:        17:55:52 PM
    User:        N/A
    Computer:    [Server name]
    Description:
     Unable to move mailbox '[mailbox name]'.
     Error: The MAPI call failed.
     MAPI or an unspecified service provider.
     ID no: 80004005-0000-00000000

    and in the Security log I found these events every time when the mailbox move was failed:
    Event Type:    Failure Audit
    Event Source:    Security
    Event Category:    Object Access
    Event ID:    565
    Date:        5/9/2013
    Time:        17:55:30 PM
    User:        [Domain name]\administrator
    Computer:    [Server name]
    Description:
    Object Open:
         Object Server:    Microsoft Exchange
         Object Type:    Microsoft Exchange Logon
         Object Name:    /o=Office/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=[Server name]/cn=Microsoft System Attendant
         New Handle ID:    -
         Operation ID:    {0,2017480}
         Process ID:    1544
         Primary User Name:    [Server name]$
         Primary Domain:    [Domain name]
         Primary Logon ID:    (0x0,0x3E7)
         Client User Name:    administrator
         Client Domain:    [Domain name]
         Client Logon ID:    (0x0,0x17523)
         Accesses        Unknown specific access (bit 0)
         Privileges        -
         Properties:

    Event Type:    Failure Audit
    Event Source:    Security
    Event Category:    Object Access
    Event ID:    565
    Date:        5/9/2013
    Time:        17:55:32 PM
    User:        [Domain name]\administrator
    Computer:    [Server name]
    Description:
    Object Open:
         Object Server:    Microsoft Exchange
         Object Type:    Microsoft Exchange Logon
         Object Name:    /o=Office/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=[Server name]/cn=Microsoft System Attendant
         New Handle ID:    -
         Operation ID:    {0,2018374}
         Process ID:    1544
         Primary User Name:    [Server name]$
         Primary Domain:    [Domain name]
         Primary Logon ID:    (0x0,0x3E7)
         Client User Name:    administrator
         Client Domain:    [Domain name]
         Client Logon ID:    (0x0,0x17523)
         Accesses        Unknown specific access (bit 0)
         Privileges        -
         Properties:

    I gave every rights I remember to administrator and I unchecked the denieds at Office level.
    I ran eseutil and checked the integrity but there was now error. I ran eseutil repair without error, and then I ran the isinteg -s [server name] -verbose -fix -test alltests command without error as well.
    I checked the mailbox with the mdbvu32 but there was no corrupt message.
    I tried to export it with exmerge and then import it, and then I tried to import an empty exported mailbox but after I experienced the same error.

    I checked the mailbox DACLs with the PFDAVAdmin as well and DACL state everywhere is Good.

    I tried to move a few other mailboxes and it was succesfully.
    2k3 server is a single server, not cluster node.
    There is no antivirus software.

    Tha MAPI clients are Outlook 2003 and 2007.

    I found few articles on Internet but they can't help me.
    (for example:
    http://www.exchangeserverhelp.com/showthread.php/8823-Can-t-move-mailbox
    http://support.microsoft.com/kb/828875
    http://support.microsoft.com/kb/836883
    http://support.microsoft.com/kb/289492?wa=wsignin1.0
    http://support.microsoft.com/kb/264733
    http://support.microsoft.com/kb/195985
    http://runebelune.blogspot.hu/2010/11/mapiexceptionnosupport.html
    ...
    )

    Anybody could help me how I can find out which folder properties are missing?
    I can set them manualy with the mdbvu32.
    Is there any Power Shell trick to find out and solve this situation?
    Or any solution to copy or backup all of the Exchange attributes (this mailbox is a special mailbox with more then 100 smtp mail addresses) and restore it?
    How can I debug what Exch2k3 Exchange System Manager does when move a mailbox from a store to another? How can I increase the logging level? (I set Diagnostic Logging\MSExchangeIS\System\Move Mailbox to Maximum already.)

    The Exchange 2k3 server is upgraded from Exchange 2k.
    The operating system for Exchange 2k3 is Windows 2k SP4.

    I spent hours for finding a solution so I see I need your help. :)

    Thanks.
    Csaba Marosi

    Csaba Marosi

    Thursday, May 9, 2013 5:20 PM

All replies

  • Hello,

    From your description, you have repaired your databse. And there is no AV software.

    I suggest you check your network connectivity and DNS Lookup

    Here are the blog and KB for your reference.

    http://blogs.msdn.com/b/anthonw/archive/2005/05/21/420794.aspx

    http://support.microsoft.com/kb/318726

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Friday, May 10, 2013 1:59 AM
    Moderator
  • Hey Cara, thank you for your advice.

    I can move other mailboxes without any problem. In this case I can't move that mailbox in same server from a store to another store.

    At this weekend I will install a new Exchange 2003 server in a test environment and I will attach this store db and I will try to move this mailbox to an other store. I will be back with the result. If you have any other suggestion just write here, thanks.

    Update:

    What a surprise! I created an exactly same environment and copied the store there. I tried to move the mailbox but I can't, the error was same as before. Then I deleted everything from that mailbox so the Exchange System Manager showed the mailbox Size is 0 KB and the Total Items is 0 as well (I used mdbvu32.exe). And then I tried to move that mailbox but I got exactly the same error messages as before.


    Csaba Marosi


    Friday, May 10, 2013 8:26 AM
  • Hello,

    From your description, the issue only occurs on a mailbox.

    So I suggest you recreate the mailbox and check the result. (Note: Before you recreate the mailbox, please export your mailbox to pst files)

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Monday, May 13, 2013 1:53 AM
    Moderator
  • Hey, yes I wanted to avoid this way. As I wrote this is a special mailbox with more than hundred smtp addresses, dozens of rules and thousands of mail settings. So if I delete the mailbox I have to organize very carefully and very well this process instead of simply moving the mailbox.

    So if you have any idea how I can find out which mailbox properties are expected to the move process it would be more than helpful for me. I'm looking for any debug tools or special registry settings what can give me more detailed error messages. I have maximum 2 days to solve this situation without deleting and recreating the whole mailbox. I can test these tools and suggestions in a test environment before I apply it in a production environment.

    Thank you for your time and help.

    Csaba Marosi

    Monday, May 13, 2013 10:28 AM
  • Hello,

    At present, I have the idea to suggest you recreate the mailbox, but this is a special mailbox for you.

    So I suggest you contact microsoft support. Maybe you can get better ways to solve your issue.

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Tuesday, May 14, 2013 7:03 AM
    Moderator
  • Hello,

    Is there any update?

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Monday, May 20, 2013 8:03 AM
    Moderator
  • Can you attempt the move again and get the output file that has the move mailbox statistis saved in the xml file? Check in that file to see if there is anything specific about the move which may have failed.

    When you say you attempted to move the mailbox to exchange 2010, did we use -BadItemLimit Int32 and -AcceptLargeDataLoss Switches? when you moved from exchange 2003 to exchange 2010 ?

    Check the move request statistics on exchange 2010 server for this mailbox:

    Get-MoveRequest "Mailbox" | Get-MoveRequestStatistics -IncludeReport >C:\FailedMove.txt


    M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!!


    • Edited by PK M Wednesday, May 22, 2013 8:36 AM
    Wednesday, May 22, 2013 8:33 AM
  • I also received the same error message when trying to move a mailbox via active directory exchange tasks option on a workstation.

    I resolved my issue with simply replacing the existing mapi32.dll in my machine's C:Windows\System32 with the mapi32.dll from a machine that did not have the issue. I closed all programs like Outlook, and with my admin credentials, I renamed the machine's mapi32.dll to OLDmapi32.dll before copying the other machine's mapi32.dll from the other machine.

    I don't know if this will resolve your issue but it certainly resolved mine.

    Joseph Moran

    Friday, October 11, 2013 3:15 PM
  • "Run ISINTEG to check for any problem in the database "[Store name]". " kinda tells you what to do, doesn't it?

    Assuming you have a usable backup of the database, dismount it and run ISINTEG against it using "all tests".

    If that doesn't fix your problem, dismount the database and run ESEUTIL /D on the database, followed by at least two passes of ISINTEG (more may be needed if isinteg continues to find and fix errors). If ISINTEG no longer is able to find and fix warnings and errors then there's no need to run it again -- go ahead and mount the database.

    If, after all that, you still can't move the mailbox it's time to accept a large data loss during the move. You can try exporting the mailbox to a PST first, but I don't think that'll be any more successful.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Friday, October 11, 2013 9:53 PM