locked
Failed to cleanup the source mailbox after the move. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    When migrating users from Exchange 2003 to Exchange 2010 I recieve the following warning after the move complets:

    Warning: Failed to cleanup the source mailbox after the move.
    Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)

    It appears that my mailbox exists on both servers and in both stores.  If I delete the mailbox from the 2003 store it also deletes the mailbox from the 2010 database as they are still "linked".  How do I properly complete this migration?

    Regards,

    Eric
    Tuesday, September 29, 2009 1:57 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Smeade, The source mailbox beeing left behind is not too dangerous. It becomes a disconnected mailbox, which will be cleaned up by the store after a while (in E14, the default is 30 days, not sure about 2003). The only bad side effect of this is that there’s a short period of time when the source store does not yet see the homeMDB change in AD (due to AD replication delays), so it will allow email deliveries into the old mailbox, in case transport is also seeing stale AD data and attempts to deliver into the old mailbox. This condition clears up as soon as homeMDB change replicates everywhere and the caches are cleared.

    • Proposed as answer by WiRall Friday, February 19, 2010 5:56 AM
    Tuesday, September 29, 2009 8:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    There is a known issue with Exchange 2003 and needed to install a hotfix KB940012 so try after installing it...

    Move mailbox issue: disconnected mailbox remains on source mailbox Store

    For already moved mailboxes, you may need to move back and forth to delete orphan mailbox in Exchange 2003 database...

    Amit Tank | MVP – Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

    • Proposed as answer by WiRall Friday, February 19, 2010 5:56 AM
    Wednesday, September 30, 2009 6:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Amit,

    I'm seeing this with mailboxes migrating from 2003 to 2010. Do you know if this hotfix actually fixes the issue? The KB states:..Note This hotfix does not resolve the stub mailbox issue. It adds additional events in the application logs that indicate that there was a failure during the move mailbox operation. For more information, see the "After you apply the hotfix" section.

    Thanks
    Tuesday, October 27, 2009 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same problems, I have co-existence of Exchange 2003 and 2010 and at the stage of migrating user mailboxes from one server to the other. The first mailbox I tried was my own and ended up with the same error message:-

    Warning: Failed to cleanup the source mailbox after the move.
    Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)

    The mailbox still exists on the Exchange 2003 server with no items but has a few bytes. I purged this mailbox and guess what, my mailbox was deleted from both servers. Had to recover items from local ost file to get it all back. I tried manually running the cleanup agent before purging but that made no difference whatsoever.

    I have since migrated a few more mailboxes with no issues, but now have come across one that is giving me the same error message. Is there a fix for this?

    Thanks
    Mark


    Monday, February 1, 2010 8:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm also having the same problem moving boxes from 2003 to 2010. About 90% of them fails. I have applyed hotfix KB940012 but it dos not help.
    Tryed to move boxes back to 2003, moved them from one store to other in 2003 and then moved to 2010..same problem.

    Anyone out there solved this issu?

    Thx

    Håkan
    Friday, February 12, 2010 4:40 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    We saw this with some users as well with moves from 2003 to both 2007 and 2010, but so far it has always proven to be a benign issue. As Amit points out the mailbox turns into a stub and is garbage collected after your configured time interval.
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Enterprise Server 2010, Configuration
    MCITP: Enterprise Messaging Administrator 2010
    LMNOP
    • Proposed as answer by Scott Hine Wednesday, February 24, 2010 6:11 AM
    Friday, February 12, 2010 5:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    I am in the middle of a migration of around 4000 mailbox, the first mailboxes moved with this issue, we are testing the hotfix and moving the mailbox again back to 2003, are there any solid solution for that?
    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    Saturday, February 13, 2010 12:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    As long as AD was updated correctly, Outlook repointed for the users,  and you see the mailboxes as stubs with the red circle and X over them in 2003 (you may have to manually run the cleanup wizard after AD replicates the moves) then there really is no reason to redo it all over again. :)
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Enterprise Server 2010, Configuration
    MCITP: Enterprise Messaging Administrator 2010
    LMNOP
    • Proposed as answer by Daham Perera Sunday, April 15, 2012 1:33 AM
    Saturday, February 13, 2010 3:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks mate,
    applying the hotfix resolved the issue and now move around 500 users and things works smoothly.

    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    Saturday, February 13, 2010 8:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    and also make sure that Exhcange 2010 RU1 is applied
    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    • Proposed as answer by bhifi Tuesday, June 25, 2013 6:12 PM
    Saturday, February 13, 2010 8:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Brian,

         I am also in the middle of a 2003 to 2007 migration - I just ran the mailbox cleanup wizard and still see the stubs. I have not applied the hotfix as it was stated that it only adds event logs - we are going to decommission the mailbox server that these stubs remain on to reclaim the space - this reclaimed space will be used for the next new mailbox server - I am wondering if there is another way to remove the stubs. Or do we just continue with the decommissioning of the server and that will do the trick.

    Thanks
    Monday, February 15, 2010 4:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    one additional question would using the Command Shell with the SourceMailboxCleanupOptions instead of the gui clear this?
    Monday, February 15, 2010 4:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Brian,

         I am also in the middle of a 2003 to 2007 migration - I just ran the mailbox cleanup wizard and still see the stubs. I have not applied the hotfix as it was stated that it only adds event logs - we are going to decommission the mailbox server that these stubs remain on to reclaim the space - this reclaimed space will be used for the next new mailbox server - I am wondering if there is another way to remove the stubs. Or do we just continue with the decommissioning of the server and that will do the trick.

    Thanks

    Keep in mind the Exchange 2003 cleanup wizard only marks them as disconnected mailboxes and it does not purge them. Once they are marked as disconnected the purge timer starts (30 days by default unless you changed it) before they are purged by the online maintenance. You can also right-click a disconnected mailbox manually and purge it if you want to for some reason. If you have moved all active mailboxes off of the server and are decomissioning the server anyways then there really isn't any need to reclaim the space unless it is on a SAN and you need to repurpose it for some other project. The stubs on the 2003 server aren't hurting anything.
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Enterprise Server 2010, Configuration
    MCITP: Enterprise Messaging Administrator 2010
    LMNOP
    Monday, February 15, 2010 5:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same issue, although i cannot purge my stubs as they state that they have been reconnected with an exisitng user, yet its still got the red X next to it.

    I'm wondering whether this is caused by mail coming into the mailbox while moving?

    And also anotehr question, when we decommsion the old store will it allow us to uninstall exchange when there are "Exisiting mailboxes/Stubs" still in the store?

    I've had my old store down and i can still access my mailbox on the new store, i'm starting wonder if i'm worrying about this a bit too much.

    Cheers


    Friday, February 19, 2010 11:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Scott,
    you will have to solve this issue, otherwise you will have mailbox acces issues,
    apply the hotfix above, in my case applying the hotfix solved the issue but it repeated again, further checking revealed that there was a firewall between the Exchange 2010 and Exchange 2003, placing the servers in the same security zone solved the issue and mails was moved successfully.
    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    Saturday, February 20, 2010 10:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same issue, although i cannot purge my stubs as they state that they have been reconnected with an exisitng user, yet its still got the red X next to it.
    .
    .
    .
    And also anotehr question, when we decommsion the old store will it allow us to uninstall exchange when there are "Exisiting mailboxes/Stubs" still in the store?


    If they're claiming to be connected to someone then you'll have to manually fix that. If you go to the database through ADSIEdit you'll see a line that lists all connected users to that DB. Once those are removed you should be able to uninstall Exchange because it won't let you until no users are on there.
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Enterprise Server 2010, Configuration
    MCITP: Enterprise Messaging Administrator 2010
    LMNOP
    Saturday, February 20, 2010 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    OK!!!! heres the deal.

    After i got this error i proceeded to load the hotfix which states that its ONLY laods extra error info into windows blah blah.  I then became concern that my stubs that i left behind would cause me grief when i go to uninstall exchange.  I did it again in the weekend and found that the problem still occured, all mail was transfering properly and mailboxes were working BUT they were leaving stubs behind.

    I thought well stuff this i'll use me as a guinea pig, so i proceed to try and purge my stub (this didnt work) i then tried reconnecting to antoher user (this didnt work), i then thought well whats left, set the deleted mailbox retension period to 2 days.

    My stub has now been deleted by the system and my mailbox works fine (crossing fingers).

    So although i couldnt purge my old mailbox myself the system could so i'm waiting for the other ones to purge and i should be able to carry on with decommsioning exchange 2003 :)

    Cheers
    Monday, February 22, 2010 8:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am just moving from one store to another in the same storage group on 2003 and getting the stubs. 

    I just want to be sure that I don't lose any data when I remove the stubs.  Even deleted Items that they may want to recover.

    I read that what is left behind is actually just the folder structure and no data.  Is that true?



    Thanks everyone!
    Thursday, February 25, 2010 2:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Brian,

    I have just started a 2003 -> 2010 migration and ran into this issue after about 30 successful moves.

    AD shows the target database correctly, but if I look on the 2003 server, it is NOT a stub... it is a very small database with a small number of items (the actual mailbox was large). It is as if it has left some items behind.

    Elsewhere someone suggested running ISINTEG to fix this. What can you suggest? All of your comments seem to apply to the situation where the source server has a stub mailbox and I don't seem to have that.

    Cheers, Andrew

    Thursday, May 13, 2010 12:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Correction to above... I ran the cleanup agent and now it shows a little red cross... so I am picking that I don't have to worry about this. Do I have to get it to go away before I can decommision the source server, or can I just decommision with the 'stub' sitting there?

    - Andrew

    Thursday, May 13, 2010 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    Have just hit this issue with the first mailbox I tried moving (my own).  As others have found, all seems to work fine and I have the small stub left behind with the red cross against it.

    What I'm more concerned about is that my mailbox on the Exchange 2010 server looks as if the move is still in progress.  The mailbox icon still has the green arrow on it and there's still an entry in the Move Request folder.  This entry says "Completed with warning" and the detail has the above warning issue.

    Should this entry still be there?  Should I use the context menu option to clear it or will this delete stuff?

    Toby
    Wednesday, May 26, 2010 10:41 AM
  • Question
    Sign in to vote
    7
    Sign in to vote

    Team,

    Here is the solution:

    1. Open ESM on Exchange 2003 and navigate to the MAILBOX STORE

    2. Right-click the MAILBOX STORE -> PROPERTIES -> LIMIT tab


    3. Set the KEEP DELETED for ITEMS and MAILBOX to 0 and apply the changes


    4. Now, navigate to the MAILBOX folder below the MAILBOX STORE. Right-click the MAILBOX folder and run the cleanup agent. This will SAFELY delete the mailbox stubs without affecting the migrated mailboxes on Exchange 2007 or 2010

     

    Enjoy!

     

    IntelliSuite Team

     

    • Proposed as answer by IntelliSuite Thursday, July 8, 2010 5:44 AM
    Thursday, July 8, 2010 5:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That worked for me!  Thanks!
    Wednesday, July 28, 2010 8:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Set the KEEP DELETED for ITEMS and MAILBOX to 0 and apply the changes then ran the cleanup agent and the mailbox now has a red X.  Is it safe to purge this mail now ?

     

    Regards

    • Proposed as answer by hankosky Saturday, October 23, 2010 6:45 PM
    Thursday, July 29, 2010 9:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is what i did to get this issue resolved.

     

    Once all the mail box moves were complete,

    1 - Clear the Move Requests in Exchange 2010 EMC.

    2 - Right click on the Data Store in Exchange 2003 and go to the Properties

    3 - Go to the limits tab.

    4 - set the Keep deleted items for and the keep deleted mailboxs to "0"

    5 - Unchecked Do Not Perminatly Delete.

    6 - Click Apply, OK

    7 - Right Click Mailbox's Folder under the datastore and click run cleanup agent.

     

    They all all now gone.

     

     

    • Proposed as answer by hankosky Saturday, October 23, 2010 6:48 PM
    Saturday, October 23, 2010 6:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i have the same problem

    i moved the mailboxes to exchange 2010 and some moves were completed with exceptions.

     

    i set the keep items to 0 as instructed but still nothing. i applied all hotfixes etc and restarted all exchange services.

    also in adsiedit.msc under the database properties, the entry homeMDBBL does not list those mailboxes there.

     

    did not try removing exchagnge features purge and then connect the mailbox

    • Proposed as answer by scriven_j Monday, November 7, 2011 12:45 PM
    • Unproposed as answer by scriven_j Monday, November 7, 2011 12:55 PM
    Saturday, January 29, 2011 7:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you ever resolve this?

     

    I have a similar problem and none of the suggestions above have helped either.

     

    Did you get the mailbox removed and if so, do you remember how?

     

    User was migrated over 6 weeks ago and none of the automated or manual processes I have tried have managed to delete them yet.

     

    I am worried that I will not be able to uninstall Exchange properly at the end if I don't resolve this.

    Monday, November 7, 2011 12:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Think I'll probably give ISINTEG a go as suggested here if no-one has any other ideas:-

    http://blog.brainlitter.com/2010/04/27/exchange-2010-mailbox-migration-resolution-for-mapiexceptionnotfound-unable-to-delete-mailbox/

     


    • Edited by scriven_j Monday, November 7, 2011 12:55 PM
    Monday, November 7, 2011 12:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello all,

    I had the same problem except my "left behind mailbox" was not disabled, even though it was not used.  Since it happened to a test mailbox too, I tried moving the test mailbox back to the source server ans you know what ? The move stopped with error "A duplicate mailbox was found due to problems during a Move Mailbox procedure. The duplicate mailbox has been deleted. Try again later."

    And in fact, the source mailbox which was a leftover mbx was deleted. 

    So maybe if you try a move back to the source server, it will delete those left being mailboxes without actually moving the mbx.

    Let me know !

    Tuesday, November 15, 2011 9:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I've found that when a "stub" is left behind on the original server, go to the destination server and tell exchange to transfer it back to the source server where the corrupt stub is.

    It will refuse to do it, displaying an error message saying that the mailbox already exists on the source server. It will also delete the corrupt stub from the original server.

    After you've closed the wizzard, go back to the original server which has the corrupt stub on it, right click the mail box and select purge.

    Works very nicely.

    Tuesday, January 3, 2012 2:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If all mailboxes are out of the database you are migrating from, you can also change the Deletion settings Limits on the database you migrated from, down to 0 or 1 day, and wait a day, then run the cleanup agent.
    Friday, February 17, 2012 10:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've tried all these things.

    None of them have worked.  ISINTEG is the only option I seem to have.

    • Proposed as answer by supportwiz Thursday, April 12, 2012 6:18 PM
    Friday, February 17, 2012 12:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This solution worked for me

    1. Open ESM on Exchange 2003 and navigate to the MAILBOX STORE

    2. Right-click the MAILBOX STORE -> PROPERTIES -> LIMIT tab


    3. Set the KEEP DELETED for ITEMS and MAILBOX to 0 and apply the changes

    4. Now, navigate to the MAILBOX folder below the MAILBOX STORE. Right-click the MAILBOX folder and run the cleanup agent. This will SAFELY delete the mailbox stubs without affecting the migrated mailboxes on Exchange 2007 or 2010

    Just need sometime for cleanup agent to complete the job. be patient. :-)

    Thanks a lot IntelliSuite Technologies for the post.

    Chris

    • Proposed as answer by supportwiz Thursday, April 12, 2012 6:33 PM
    Thursday, April 12, 2012 6:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It worked like a charm.....!!!!
    Sunday, April 15, 2012 1:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This solution worked for me

    1. Open ESM on Exchange 2003 and navigate to the MAILBOX STORE

    2. Right-click the MAILBOX STORE -> PROPERTIES -> LIMIT tab


    3. Set the KEEP DELETED for ITEMS and MAILBOX to 0 and apply the changes

    4. Now, navigate to the MAILBOX folder below the MAILBOX STORE. Right-click the MAILBOX folder and run the cleanup agent. This will SAFELY delete the mailbox stubs without affecting the migrated mailboxes on Exchange 2007 or 2010

    Just need sometime for cleanup agent to complete the job. be patient. :-)

    Thanks a lot IntelliSuite Technologies for the post.

    Chris


    Thanks that worked with immediate effect.
    Thursday, October 25, 2012 11:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Funny thing is I always miss the easy stuff. After hunting for answers, hot fixes & pulling my hair out.... 

    1. Open ESM on Exchange 2003 and navigate to the MAILBOX STORE

    2. Right-click the MAILBOX STORE -> PROPERTIES -> LIMIT tab


    3. Set the KEEP DELETED for ITEMS and MAILBOX to 0 and apply the changes

    4. Now, navigate to the MAILBOX folder below the MAILBOX STORE. Right-click the MAILBOX folder and run the cleanup agent. This will SAFELY delete the mailbox stubs without affecting the migrated mailboxes on Exchange 2007 or 2010

    Enjoy!

    IntelliSuite Team

    .......

    Thanks guys for the post !!!

    Saturday, November 29, 2014 7:36 AM