To fix it use this article http://certsclub.wordpress.com/2013/02/01/fail-to-clean-up-the-source-mailbox-after-the-mailbox-move/ Go to Solution 1 Participant Amit LVL 41 Exchange38 1 Comment LVL 41 Overall: Level 41 Exchange 38 Message Active today Accepted Solution Reply Aaron Calloway says: April 10, 2013 at 7:13 pm How about your Exchange 2007 version? As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try Although the move did complete, it "Completed with Warnings" showing the following error in the move request details: Warning: Failed to clean up the source mailbox after the move. navigate here
Thursday, September 20, 2012 8:46 PM Reply | Quote Answers 1 Sign in to vote Hi Fabio, You are right, the expected behavior is disconnected state without a warning message, and Believe me, I've looked at alternatives, but for a couple reasons they are the only game in town that does everything we need. I think this particular problem is mentioned in the RU1 release notes under issues fixed. Any advice?? https://social.technet.microsoft.com/Forums/exchange/en-US/ff2258f0-af8c-4c7b-91d0-2cf377a501d9/warning-failed-to-clean-up-the-source-mailbox-after-the-move?forum=exchange2010
Please rest assured that once we got more information about the issue, we will inform you ASAP. Thanks Mark Feb 1, 2010 Flag Post #5 Share Kelderon Guest I'm also having the same problem moving boxes from 2003 to 2010. Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) We don't want to leave data behind on that volume. Edited by Andrey Podlesnykh Friday, September 27, 2013 5:22 AM Friday, September 27, 2013 5:19 AM Reply | Quote 0 Sign in to vote Horrible.
The easy solution would be to increase the size which I end up doing any ways. Remove-StoreMailbox –Database
Fabio Martins MCDST/MCSA Brasil!!! Exchange 2010 Version Numbers Register Login Posting Guidelines | Contact Moderators Ars Technica > Forums > Operating Systems & Software > Windows Technical Mojo Jump to: Select a forum ------------------ Hardware & Tweaking Audio/Visual I opened a support case with Microsoft and it appears that they are aware that SP 3RU1 doesn't fix the issue in all cases. imp source MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Ask a Question
If you're users are happily connected to the relocated mailbox, then you could reduce your retention period to clean up the old disconnected copy. After the move, I got this warning. On closer examination under the Details tab we get the error : Warning: Failed to clean up the source mailbox after the move. But today when I moved that user from the default database to the newly created one it completed with a warning about:Warning: Failed to clean up the source mailbox after the
Take Survey Question has a verified solution. check over here I was running out of hard drive space on the virtual Hard drives that contained the Exchange databases. Refer to: http://technet.microsoft.com/en-us/library/dd298174.aspxFiona Liao TechNet Community SupportMarked as answer by Fabio Martins . Since your users are working fine with the moved mailboxes, I think we can ignore this irror, and wait for the retention period expires.
Question has a verified solution. Rick25 Ars Tribunus Militum Registered: Jun 24, 2000Posts: 2405 Posted: Fri Mar 29, 2013 10:50 am Fair enough, thanks for popping into the thread. 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. his comment is here so please give me any idea how to clear this issue.
does the same server hold all roles ? - Rancy 0 Message Author Comment by:FreshExpress ID: 383871282012-09-11 Thanks Rancy, just the Mailbox role on that server. 0 Message Author By doing this I noticed there are also a lot of 'disabled' mailboxes, think I'm gonna do a SUM of them all to see the total size we can gain... You canprevent this issue from happening in the futureby upgrading to Exchange 2010 SP3.
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 I purged this mailbox and guess what, my mailbox was deleted from both servers. http://netfiscal.com/exchange-2010/exchange-2010-move-request-unable-to-delete-mailbox.html Search Certification Club Calendar Club Officers Follow Blog via Email Enter your email address to follow this blog and receive notifications of new posts by email.
Tuesday, October 21, 2014 4:14 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site. I have applyed hotfix KB940012 but it dos not help. The implementation though is sloppy and quality is poor. I mean, it can't be that, every time you move a mailbox to another dag, the mailbox remains also in the source...?
Wednesday, September 18, 2013 3:18 PM Reply | Quote 0 Sign in to vote I am on RU2 and I just got the error this morning. Move mailbox issue: disconnected mailbox remains on source mailbox Store http://exchangepedia.com/blog/2007/07/move-mailbox-issue-disconnected-mailbox.html For already moved mailboxes, you may need to move back and forth to delete orphan mailbox in Exchange 2003 database... This may affect other disconnected mailboxes from the same database though. Warning: Failed to clean up the source mailbox after the move.
The mailbox in the source database should remain in a disconnected state. Regards, Eric Sep 29, 2009 Flag Post #1 Share Blackuke Guest Hi Smeade, The source mailbox beeing left behind is not too dangerous. This condition clears up as soon as homeMDB change replicates everywhere and the caches are cleared.