none
"Failed to clean up source mailbox after move" Error

    Question

  • I'm getting the following error after attempting a three mailbox move from one Exchange 2010 SP2 database to another on the same server.  All the similar errors I've seen while searching are between 2010 and 2003 or 2007.

    Warning: Failed to clean up the source mailbox after the move.
    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

    The move shows "Completed with warnings" as status, and I don't know how to clean the failed cleanup up.

    I HAVE been able to move mailboxes from one mailbox database before on this server.

    The log of move move shows the following, notice at one point the log says the cleanup is done, but then throws a "failed" flag and attempts cleanup 5 more times.  This server has NOT had RU 3 applied.

    6/25/2012 4:58:01 PM [HUB_Server] Move has completed and final clean up has started.
    6/25/2012 4:58:01 PM [HUB_Server] Source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' was successfully cleaned up after the move.
    6/25/2012 4:58:01 PM [HUB_Server] Relinquishing job.
    6/25/2012 4:58:06 PM [HUB_Server] The Microsoft Exchange Mailbox Replication service 'GATE5.evergreen.edu' (14.2.297.0 caps:07) is examining the request.
    6/25/2012 4:58:06 PM [HUB_Server] Connected to target mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)', database 'NoQuotasDtoF', Mailbox server '<Mailbox_Server>' Version 14.2 (Build 247.0).
    6/25/2012 4:58:06 PM [HUB_Server] Mailbox move is already finished.
    6/25/2012 4:58:06 PM [HUB_Server] Move has completed and final clean up has started.
    6/25/2012 4:58:06 PM [HUB_Server] Failed to clean up the source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' after the move. Attempt 1/6.
    Error details: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b()
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    6/25/2012 4:58:06 PM [HUB_Server] Target mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' was successfully reset after the move.
    6/25/2012 4:58:07 PM [HUB_Server] Post-move cleanup failed. The operation will try again in 30 seconds (1/6).
    6/25/2012 4:58:37 PM [HUB_Server] Failed to clean up the source mailbox 'Primary (58a48cb1-ff66-4893-a352-436ecd328504)' after the move. Attempt 2/6.


    ~bc

    Tuesday, June 26, 2012 4:34 PM

Answers

All replies

  • Hi

    Is the message "completing with warnings" for few users or all the users?

    Could these user access mailbox via OWA?

    What RU is your SP2? Did it upgrade to RU3?

    Also I Found a thread Failed to cleanup the source mailbox after the move

    http://social.technet.microsoft.com/Forums/en/exchange2010/thread/43c11f0e-450e-4ff1-9163-2cb801e2e1e0

    And it mentioned that it is a known issue with Exchange 2003 and a hotfix KB940012 could help

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

    Please have a try

    Cheers


    Zi Feng

    TechNet Community Support

    Wednesday, June 27, 2012 9:46 AM
    Moderator
  • I am having this issue as well after installing Rollup 3 for Exchange 2010 SP2.  We have never had Exchange 2003 in our environment so the older solutions do not apply.

    Warning: Failed to clean up the source mailbox after the move.
    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

    7/5/2012 1:17:35 PM [SERVER] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
    7/5/2012 1:18:06 PM [SERVER] Failed to clean up the source mailbox 'Primary (35cbb3c7-afed-459f-9fb7-55edf7c4cdc2)' after the move. Attempt 6/6.
    Error details: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b()
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    7/5/2012 1:18:06 PM [SERVER] Request is complete.

    Thursday, July 05, 2012 6:30 PM
  • This is for SP2 RU 3. 

    The failure is for a few mailboxes, not all of them. 

    Yes, the users can access their mailboxes, it is just I'm left with a "failure to cleanup" after moving. 

    Again, this happens when moving mailboxes from one database to another ON THE SAME SERVER (Exchange 2003 is NOT involved).


    ~bc

    Friday, July 06, 2012 5:43 PM
  • I have same problem as you, after installing RU3, in move request log:

    Post-move cleanup failed. The operation will try again in 30 seconds - it appears 3times or 4times.

    I must move 4500 mbxes, most of them with zero or small data, but "completing" status blocked processing of next local move requests for 2 or 3 minutes.

    Only one option for me was modification of MSExchangeMailboxReplication.exe.config

    see here:

    http://social.technet.microsoft.com/Forums/en-us/exchange2010/thread/027afd76-0be0-4ff7-aa09-64f17b872285

    Move requests was between two Ex2010SP2 servers only.

    Hard to say how to repair :-(

    On Exchange 2010 SP2 without any RU it was fast and easy to move such huge amount of mailboxes without problem in few hours.

    I am not able to found how to change retry time 30 seconds for post-move clean-up.

    Thursday, July 12, 2012 11:41 AM
  • We are running Exchange 2010 SP2 UR3 and also have the same issue.

    I'm moving about 125 mailboxes from DB1 to a new DB01 (DAG - but active copies are both on the same server).

    Error in Move Request Log:

    7/11/2012 12:10:49 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (1/6).
    7/11/2012 12:11:19 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (2/6).
    7/11/2012 12:11:50 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (3/6).
    7/11/2012 12:12:21 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (4/6).
    7/11/2012 12:12:52 PM [CAVTMASE131] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
    7/11/2012 12:13:23 PM [CAVTMASE131] Request is complete.

    Each outlook client disconnects for about 2 minutes when the move is at approximately 95%, but they are completing and functionality seems to be OK.


    DQ

    Thursday, July 12, 2012 8:38 PM
  • Hi,

    Does anyone have a fix for this? I am currently moving from Exchange 2003 to 2010 and before I installed SP2 RU3 the mailboxes moved fine. I was hoping RU4 release yesterday would fix this issue but it didn't

    I would like to have a fix ASAP as I have 100+ mailboxes and at 6 extra minutes per mailbox that's around 10 extra hours just in waiting.

    Our setup is very simple with one Exchange 2003 standard SP2 machine moving to one Exchange 2010 box.

    Thanks,

    Ken

    Wednesday, August 15, 2012 8:33 PM
  • We are seeing the same issue in an Exchange 2010 SP2 RU3 environment with 15,000 mailboxes.  We didn't see it before RU3 but we did RU3 and SP2 over the same weekend.  The impact is that it breaks online mailbox moves for Ex2010 to Ex2010 moves....   We're seeing clients loss contact with the mailbox during the retries...
    Thursday, August 16, 2012 3:30 PM
  • Hi All

    Has anyone managed to resolve this ? or find a fix

    We are experiancing the same issue with exchange 2010 SP2 RU2

    It was working fine with SP1

    Lee


    IT Team Leader Zycko LTD.

    Friday, August 24, 2012 8:55 AM
  • I haven't.  I'm just deleting them as I go.  I'd suggest you create a new post as I think this one is fairly dead.

    ~bc

    Friday, August 24, 2012 10:33 PM
  • We are experiencing the same issue now, after installed SP2 & RU4, when moving mailboxes from one DB to another on the same Exchange 2010.

    So far no problems when moving mailboxes from Exchange 2007 into this new DB of E2010.  And there were no problems a few months back (before SP2 RU4 installed) moving mailboxes on the same server between other two DBs.

    And the mailboxes which have "completed with warning" look like disconnected on the source DB side.

    Does anyone have a fix?

    Thanks,

    Eric 

    Friday, September 07, 2012 9:18 PM
  • Same here... SP2 RU4 and had two out of 85 mailboxes finish with the same error... Anybody??? Bueller???
    Saturday, September 08, 2012 12:03 AM
  • I don't think anyone but me is reading this tread.  Your best bet is to start a new one.

    ~bc

    Tuesday, September 11, 2012 5:51 PM
  • I think I found a workaround to the issue. It looks like this is a bug with sp2 ru4

    To workaround the issue please follow the below:

    To Clean up a Soft Deleted Mailbox on a database:

    Get-MailboxStatistics -Database <MAILBOXDATABASE> | Where { $_.DisconnectReason -eq "SoftDeleted" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason

    Remove-StoreMailbox –Database <MAILBOXDATABASE> –Identity <MAILBOXGUID> –MailboxState Softdeleted

    To Clean up all Soft Deleted Mailboxes on a database:

    Get-MailboxStatistics –Database <MAILBOXDATABASE> | Where-Object {$_.DisconnectReason –eq “Softdeleted”} | ForEach {Remove-StoreMailbox –Database $_.database –identity $_.mailboxguid –MailboxState Softdeleted}


    IT Team Leader Zycko LTD.

    • Proposed as answer by Maddas69 Friday, September 14, 2012 10:26 AM
    Wednesday, September 12, 2012 8:18 AM
  • Hi.

    I also have this problem at a customer that is doing a migration from Exchange 2007 to Exchange 2010. All Exchange 2010 servers with SP2 and the last Rollup patch.

    When do you run this powershell commands? When the move-mailbox says "Completing"? Or after all the mailbox move says Completed?

    //Glenn

    Monday, September 17, 2012 8:58 AM
  • Just wanted to chime in and advise I am seeing the same problem. 2010 SP1 to 2010 SP2 RU4. Created a new DB and moving the mailboxes across does exactly the same thing - sits at 6 attempts to clean up the old database. Could this be a problem moving between databases created in Exchange PRE-SP2 and if I recreate all my mailbox databases in SP2 it will go away?

    I am in the process of doing this anyway (we need SP2 to fix a whitespace issue) so am moving all mailboxes to new databases. I will report back if moving between native SP2 databases gives the same error.

    Does anyone know what the mailbox cleanup post move actually does? Even mailboxes that show as "completed" and not "completed with warnings" still appear in the disconnected mailbox so it isn't removing soft deleted mailboxes if that is what it is meant to do?

    Wednesday, September 19, 2012 3:05 AM
  • Do you guys have the option "Don't permanently delete items until the database is backed up" selected on the source database settings by any chance?  I have unticked this and don't seem to get the failure now.  I still see " Post-move cleanup failed. The operation will try again in 30 seconds" but not the failure about deleting the source mailbox?

    EDIT: Scratch that - it still does it randomly so must have had a lucky streak!!

    • Edited by Douggly Wednesday, September 19, 2012 4:25 AM
    Wednesday, September 19, 2012 4:12 AM
  • You run the command when the status of the Move Request status is "Completed with warning"
    Wednesday, September 19, 2012 1:28 PM
  • From Experts-Exchange:

    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27860728.html#a38404595

    Excerpt:

    Soft-deleted mailboxes - When mailboxes are moved from a Microsoft Exchange Server 2010 database to any other database, Exchange doesn't fully delete the mailbox from the source database upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state. With soft-deleted mailboxes, you can use the MailboxRestoreRequest cmdlet set to access mailbox data during a mailbox restore operation. Soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or until the Remove-StoreMailbox cmdlet is used to purge the mailbox

    The command seems to be doing the same as a good, old Exchange 2003 Purge command (remember when deleted mailboxes had a red X and you could right-click and purge them from the database before the retention time did it automatically for you?) :-)
    • Edited by Maddas69 Wednesday, September 19, 2012 1:38 PM
    Wednesday, September 19, 2012 1:32 PM
  • Yeah but even mailboxes marked as "completed" and not with warnings still appear in disconnected mailboxes so aren't purged!  I'm not too bothered about the old mailboxes that sit in a disconnected state on the old database as that is how it worked in SP1 and they will be cleaned up eventually automatically, the problem I have is the large number of mailboxes that need to be moved which will now take hours and hours longer than before (due to retrying every 30 seconds for 6 tries that is at least 3 minutes per mailbox even if they are empty which adds 300 minutes per 100 mailboxes or 5 hours!).
    Wednesday, September 19, 2012 9:10 PM
  • Have you tried applying RU5 ?<o:p></o:p>

    Microsoft have confirmed this as a bug with ru4 which causes the failed clean-up issue

    Lee


    IT Team Leader Zycko LTD.

    Thursday, September 20, 2012 7:55 AM
  • Have you tried applying RU5 ?<o:p></o:p>

    Microsoft have confirmed this as a bug with ru4 which causes the failed clean-up issue

    Lee


    IT Team Leader Zycko LTD.


    Have MS really confirmed this is a bug?  Is there a link to the KB so I can see if there is a hotfix available?  It stops a new deployment as migrating mailboxes over to 2010 SP2 will take too long during the outage window increasing the project time.
    Thursday, September 20, 2012 11:55 PM
  • I confirmed
    this is an active bug with MS support team about a week ago. Unfortunately I don’t
    have a KB for it<o:p></o:p>

    I think
    this was broken in RU4 so maybe try RU3 instead ?<o:p></o:p>

    Lee<o:p></o:p>



    IT Team Leader Zycko LTD.

    Monday, September 24, 2012 11:11 AM
  • Same problem in RU3 but works fine with SP2 with no rollup-packs installed.
    Monday, September 24, 2012 12:34 PM
  • Started having this issue after installing RU4.
    Monday, September 24, 2012 8:13 PM
  • I rolled back to SP2 RU2 from SP2 RU4 and the problem went away.  This won't be a widespread issue as it only affects mailbox moves, but if you have to do migrations (like I have to!) then it is going to prove a problem as this increases mailbox move times significantly having to wait 3 minutes extra for each mailbox.  I would assume the only way to get round this when migrating from Exchange 2003 is to install SP2 RU2, migrate mailboxes to 2010 and THEN install the RU4?
    Thursday, October 11, 2012 2:57 AM
  • Is there an RU5 for Exchange 2010?

    Bill

    Tuesday, October 16, 2012 7:52 PM
  • Is there an RU5 for Exchange 2010?

    Bill


    No, not for SP2 yet.  Hopefully this is fixed in SP2 RU5 but who knows.
    Thursday, October 18, 2012 9:25 PM
  • We are at Exchange 2010 SP2 UR4 and it's still a problem.

    Hopefully Microsoft is looking into it. Even though everything seems to work, it adds a few minutes to each migration, and takes away the transparent moves, as outlook disconnects during the final 5% and doesn't re-connect until it hits 99%. Those few minutes are enough to bug our users.


    DQ

    Friday, October 19, 2012 10:06 PM
  • It seems to be an issue with SP2 RU3, rolling back to RU2 should resolve the issue. However to speed up the move request: Do this on all CAS boxes:

    • C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config
    • Find “maxCleanupRetries”
    • Change it to 1, Default value is 5.
    • Restart MSExchangeMailboxReplication Service

    To Clean up a Soft Deleted Mailbox on a database:

    • Get-MailboxStatistics -Database <DatabaseName> | Where { $_.DisconnectReason -eq "SoftDeleted" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason
    • Remove-StoreMailbox –Database <DatabaseName> –Identity <MAILBOXGUID> –MailboxState Softdeleted
    • To Clean up all Soft Deleted Mailboxes on a database:
    • Get-MailboxStatistics –Database <DatabaseName> | Where-Object {$_.DisconnectReason –eq “Softdeleted”} | ForEach {Remove-StoreMailbox –Database $_.database –identity $_.mailboxguid –MailboxState Softdeleted}

    • Edited by prakp [MSFT] Monday, October 22, 2012 5:56 AM
    • Proposed as answer by prakp [MSFT] Tuesday, October 30, 2012 12:43 PM
    Monday, October 22, 2012 5:54 AM
  • same problem here, sp 2 ru 3, moving mailboxes from ex 2003 to 2010
    Thursday, October 25, 2012 9:49 AM
  • Although this is the best answer I've received from MS Support, it still leaves my clients disconnected for a minute and a half before prompting user to close and reopen Outlook after local move request completes with warnings. Thank you to PrakashPanchal for sharing the work around with us.

    Keith


    Wednesday, October 31, 2012 1:58 AM
  • Although this is the best answer I've received from MS Support, it still leaves my clients disconnected for a minute and a half before prompting user to close and reopen Outlook after local move request completes with warnings. Thank you to PrakashPanchal for sharing the work around with us.

    Keith

    Did you speak to MS support and did they mention the same work around that Prakash mentions?  I'm still hopeful this will be fixed in UR5 (it surely has to be!) but am worried about what new bugs UR5 introduces as ever since SP1 it seems every update rollup is two steps forward and one backwards with new bugs introduced :(

    If it is a confirmed problem I am also suprised to not see a KB article about it.
    • Edited by Douggly Friday, November 09, 2012 12:07 AM
    Friday, November 09, 2012 12:06 AM
  • Exchange 2010 SP2 UR5 is out.  Is this issue fixed?
    Sunday, November 18, 2012 9:35 PM
  • Just confirming that I have this same issue since RU4 was installed.

    I have an error that appears regarding AD, however the error must be wrong, the LDAP server *IS* available becuase every other task / command works against this server with no issues whatsoever.

    I have logged a case with MS to see if they can suggest anything.

     
     
     
    22/11/2012 10:57:27 [HQ-HUB1] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
    22/11/2012 10:57:59 [HQ-HUB1] Failed to reset the target mailbox after the move. Attempt 6/6.
    Error details: SuitabilityDirectoryException An Active Directory error 0x51 occurred when trying to check the suitability of server 'DC1.domain.uk'. Error: 'Active directory response: The LDAP server is unavailable.' --> The LDAP server is unavailable. 



    • Edited by Jon __R Thursday, November 22, 2012 5:01 PM
    Thursday, November 22, 2012 11:31 AM
  • Exchange 2010 SP2 UR5 is out.  Is this issue fixed?

    RU5 was pulled when last I checked so probably not.

    Steve

    Thursday, November 22, 2012 5:59 PM
  • Thankfully I didn't download or apply UR5 before it was pulled - have learnt to wait these days!

    Jon_R - Did you hear back from MS support?  I am still not sure whether to deploy anything past UR2 as there are 3000 mailboxes to migrate and this will cause problems moving them from 2003

    Wednesday, November 28, 2012 12:59 AM
  • Hello

    Still ongoing with Microsoft, they have suggested installing Version 2 of Rollup 4 for Service Pack 2.
    http://www.microsoft.com/en-gb/download/details.aspx?id=34956

    In the meantime, as a workaround, I have set the following values in MSExchangeMailboxReplicaton.exe.config on each hub / cas server, and then restarted the mailbox replication service.

     <!-- Mailbox Replication Service configuration 
        MaxCleanupRetries - 1, 0, 100


    <MRSConfiguration 
        MaxCleanupRetries = "1"


    These changes make the delay when the mailbox is disconnected "only" take a minute instead of 5 minutes as it doesn't keep retrying. It's not ideal but as we have many mailboxes to move it's better than nothing.

    Will update again when / if we have a proper fix.



    • Edited by Jon __R Wednesday, November 28, 2012 9:48 AM
    Wednesday, November 28, 2012 9:46 AM
  • Thanks, I have marked your reply as useful as I need some fixes from UR4 so have no choice but to install it :(  It's a shame an interim hotfix has not been released as MS are aware of the problem.  I'll apply the workaround when the task of moving 3000 mailboxes from 2003 to 2010 begins!  Even a one minute delay will add 3000 minutes to the task (50 hours), but that is much better than what happens at the moment with a few minutes delay per mailbox which would lead to a 150 hours (3 working weeks) delay in the task even though most of the mailboxes are small.
    Thursday, November 29, 2012 3:06 AM
  • Sorry for the late reply.

    Having worked on the support call with Microsoft, long story short was that it was a "known issue", and that I could try installing v2 of Rollup 4, in some cases it has fixed this issue.

    I've spent today doing this and unfortunately it hasn't made a single bit of difference.

    Microsoft said on the phone there wasn't anything else they could do and hopefully would be in a future rollup / service pack.

    I'll have to resort to doing user moves during quiet times (we have no down time being 24hr), so will have to make it a "known issue" of our own that when users are moved, they become disconnected for several minutes.

    Monday, December 10, 2012 4:29 PM
  • I can confirm that Rollup 4v2 makes no difference at all here either.  This affects lab environments too which are fresh installs.  Have you tried Rollup 5 (again v2 after the original was pulled).  I am holding off on Rollup 5 incase v3 gets released as has happened with some previous rollups.
    Tuesday, December 18, 2012 10:25 PM
  • I can confirm that Rollup 4v2 makes no difference at all here either.  This affects lab environments too which are fresh installs.  Have you tried Rollup 5 (again v2 after the original was pulled).  I am holding off on Rollup 5 incase v3 gets released as has happened with some previous rollups.

    No I haven't instaled Rollup 5v2. I'm not going to either to be honest, I'm not impressed with the release and subsequent withdrawl of the last few rollups. I'm going to hold off for something hopefully more stable, i.e. Service Pack 3 (unless this is confirmed as fixed in an upcoming rollup (if there is another one) and I see evidence of it actually being fixed)

    Wednesday, December 19, 2012 11:35 AM
  • My two pence.  I'm migrating from Exchange 2007 (UR8v2) to 2010 (UR5v2) and have this problem with mailbox moves from 2010 to 2010 (same server, different database) and also 2010 to 2007.  Only 2007 to 2010 completes with no warnings.


    • Edited by Ross Aveling Thursday, December 20, 2012 12:35 PM
    Thursday, December 20, 2012 12:35 PM
  • It isnt fixed in 5v2.
    Friday, December 21, 2012 7:04 PM
  • i can confirm this issue persists on Exchange 2010 SP2 RU5-v2

    strange enough i still have an Exchange 2010 SP1 RU7-v2 console and if i initiate the local move requests from it - they throw a strange error in the GUI but all the move requests complete with no warnings

    very strange!

    Thursday, January 03, 2013 3:18 PM
  • upon further queries and testing:

    i have concluded:

    Exchange 2010 SP2 tries to automatically remove softdeleted mailboxes (type of disconnected) and when it can't (probably because it is trying to use the incorrect powershell syntax above - you will get an error about concurrent pipes running the code as is - but even the code in the get-help remove-storemailbox doesn't work)

    From the Exchange 2010 SP1 console move requests were giving a status of fully completed but when i ran:

    Get-MailboxStatistics –Database "MBXDB_NAME" | Where-Object {$_.DisconnectReason –eq “Softdeleted”} | select *

    i noticed that all my completed move requests still had lingering softdeleted move requests as well.

    basically there is no difference between them - it looks like with SP2 they tried to introduce one step in the process and that step is not working.

    but because of this i now have a manual way of removing softdeleted mailboxes, which immediately frees up the mailbox database whitespace!

    Thursday, January 03, 2013 4:31 PM
  • Known bug. Scheduled to be fixed in E2010 SP3 RU1. See here for more info.

    • Proposed as answer by James Feary Tuesday, March 05, 2013 3:32 AM
    Monday, January 07, 2013 7:11 AM
  • I was having this issue as well.  The client had imported in 2003 PST's.  What ending up fixing it was doing an offline defrag.  It restructured the data.  I didn't read it anywhere just a hunch I had based on this. http://technet.microsoft.com/en-us/library/bb331958.aspx

    All the MB's moved to my new EX2010 store with no problems.  It also fixed the errors I was getting adding a copy to the other DAG members.  You might give it a shot.

    Tuesday, March 05, 2013 3:35 AM
  • Hi All,

    I am also having issues with this bug.

    I have Ex2003SP2 and Exchange 2010 SP3.

    21/05/2013 11:14:14 [SERVER] Move has completed and final clean up has started.
    21/05/2013 11:14:14 [SERVER] Source mailbox 'Primary (3d30c844-91f7-472f-b0e0-de28d5acd48b)' was successfully cleaned up after the move.
    21/05/2013 11:14:14 [SERVER] Failed to reset the target mailbox after the move. Attempt 1/6.
    Error details: MapiExceptionWrongServer MapiExceptionWrongServer: Unable to open mailbox "/o=ORGNAME/ou=First Administrative Group/cn=Recipients/cn=mseymour1" on server "SERVERNAME". (hr=0x80004005, ec=1144)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, WindowsIdentity windowsIdentity, String applicationId, TimeSpan connectionTimeout)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.CreateStoreConnection(String serverLegDN, String serverFQDN, OpenStoreFlag additionalOpenStoreFlags, MailboxConnectFlags mailboxConnectFlags)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass19.<Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect>b__18()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass65.<PostMoveCleanupTargetMailbox>b__63()
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)

    I have read that this will get fixed in CU1 for SP3 any news on this?

    Matt

    Tuesday, May 21, 2013 1:43 PM
  • Hi All,

    I am also having issues with this bug.

    I have Ex2003SP2 and Exchange 2010 SP3.

    21/05/2013 11:14:14 [SERVER] Move has completed and final clean up has started.
    21/05/2013 11:14:14 [SERVER] Source mailbox 'Primary (3d30c844-91f7-472f-b0e0-de28d5acd48b)' was successfully cleaned up after the move.
    21/05/2013 11:14:14 [SERVER] Failed to reset the target mailbox after the move. Attempt 1/6.
    Error details: MapiExceptionWrongServer MapiExceptionWrongServer: Unable to open mailbox "/o=ORGNAME/ou=First Administrative Group/cn=Recipients/cn=mseymour1" on server "SERVERNAME". (hr=0x80004005, ec=1144)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, WindowsIdentity windowsIdentity, String applicationId, TimeSpan connectionTimeout)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.CreateStoreConnection(String serverLegDN, String serverFQDN, OpenStoreFlag additionalOpenStoreFlags, MailboxConnectFlags mailboxConnectFlags)
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass19.<Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect>b__18()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.Connect(MailboxConnectFlags connectFlags)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass65.<PostMoveCleanupTargetMailbox>b__63()
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)

    I have read that this will get fixed in CU1 for SP3 any news on this?

    Matt

    I am having exact same issue of moving mailboxes between two databases on the same server.  No problems moving them between servers.  

    All of my exchange servers are Version 14.3 (Build 123.4) so latest SP3 is already installed and was supposed to be fixed!!

    Lucky I am moving all the mailboxes to the new databases anyway to keep the database fresh and for my DAGs.  So once it's moved over I will delete the old databases.  I don't know if I need to do softdelete reset before deleting the database but probably not necessary.

    Wednesday, June 19, 2013 3:39 AM
  • Hi have now found the solution to this issue.

    The KB http://support.microsoft.com/kb/2763065 resolves the issue.

    It comes as part of SP3 Rollup 1 which came out at the end of May 13.

    I have installed this update and the problem goes away

    Matt

    • Proposed as answer by matt_isda_bomb Wednesday, June 19, 2013 10:44 AM
    Wednesday, June 19, 2013 10:44 AM
  • Hi have now found the solution to this issue.

    The KB http://support.microsoft.com/kb/2763065 resolves the issue.

    It comes as part of SP3 Rollup 1 which came out at the end of May 13.

    I have installed this update and the problem goes away

    Matt

    Unfortunately I just installed that rollup last night and it has not alleviated the problem.
    Friday, June 21, 2013 3:15 PM
  • Hi,

    Have you installed on all 2010 servers in the company and rebooted them for good measure? :)

    Matt

    Friday, June 21, 2013 3:32 PM
  • Unfortunately I just installed that rollup last night and it has not alleviated the problem.

    Same here. Installed Service Pack 3, then SP3 Rollup Update 1 and a restart of each server, and I still have the problem moving mailboxes.


    EDIT : Re-installed Rollup 1 onto all servers and also restarted all servers and it still doesn't work. Will put in another support call with microsoft.

    • Edited by Jon __R Thursday, June 27, 2013 11:33 AM more info
    Thursday, June 27, 2013 9:35 AM
  • Jon__R, did you get any answers from your call to MS support?
    Tuesday, July 02, 2013 6:22 PM
  • Unfortunately I just installed that rollup last night and it has not alleviated the problem.

    Same here. Installed Service Pack 3, then SP3 Rollup Update 1 and a restart of each server, and I still have the problem moving mailboxes.


    EDIT : Re-installed Rollup 1 onto all servers and also restarted all servers and it still doesn't work. Will put in another support call with microsoft.


    Jon__R: Any updates on this? I am in the same scenario. Installed SP3 UR1 on all CASHUB and Mailbox Servers. Issue still present.

    I have a support call in with Microsoft (again) I'll post back here with a resolution if we get one.

    FOr now I have set the retries in MSExchangeMailboxReplication.exe.config to 0 so it doesn't bother to retry. THis has the same effect as a "successful" move in terms of time but still completes with warning. I'm not suggesting you should do this, it depends on your setup, but I had an urgent need to move 4,500 users in 3 days, I had to make the change or it would have taken much longer.

    Tuesday, July 02, 2013 9:59 PM
  • I have the same behavior after Exchange SP3 installation.

    If we do a new-moverequest on an old database everything is fine.

    If we do a a move to a newly created database (created after the Sp3 installation) then we got error at move request, and it adds 180 seconds delay for the move by mailbox moved :

    on server "SERVER1". (hr=0x80004005, ec=1144)

    03/07/2013 18:21:59 [SERVER1] L'opération s'est effectuée et le nettoyage final a commencé.
    03/07/2013 18:22:00 [SERVER1] Une fois le déplacement effectué, la boîte aux lettres source 'Primaire (xxxxx)' a été correctement nettoyée.
    03/07/2013 18:22:00 [SERVER1] Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminé. Tentative 1/6.
    Détails de l'erreur : MapiExceptionWrongServer MapiExceptionWrongServer: Unable to open mailbox "/o=xxx/ou=xxx/cn=xxx/cn=xxx" on server "SERVER1". (hr=0x80004005, ec=1144)

    03/07/2013 18:22:00 [SERVER1] Échec de l'opération de nettoyage postérieure au déplacement. Une nouvelle tentative sera effectuée dans 30 secondes (1/6).
    03/07/2013 18:22:30 [SERVER1] Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminé. Tentative 2/6.

    03/07/2013 18:22:30 [SERVER1] Échec de l'opération de nettoyage postérieure au déplacement. Une nouvelle tentative sera effectuée dans 30 secondes (2/6).
    03/07/2013 18:23:01 [SERVER1] Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminé. Tentative 3/6.

    03/07/2013 18:23:01 [SERVER1] Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminé. Tentative 3/6.

    03/07/2013 18:23:01 [SERVER1] Échec de l'opération de nettoyage postérieure au déplacement. Une nouvelle tentative sera effectuée dans 30 secondes (3/6).

    ...

    03/07/2013 18:24:32 [SERVER1]Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminé. Tentative 6/6.

    i opened a case, this delay is huge if we have 1000 move mailbox to run.


    fcnet

    Friday, July 05, 2013 10:09 AM
  • fcnet

    I had the same issue as I had 4,500 users to move. I did the following as a workaround. USE AT YOUR RISK.

    On each server involved in the move, so CAS and MAIL:
    1. Make a copy of Exchange\Bin\MSExchangeMailboxReplication.exe.config and keep it somewhere seperate and safe
    2. In the live copy of MSExchangeMailboxReplication.exe.config, change entries for cleanup attempts and retry delay to the below. Note that I have also increased the number of moves per DB from 2 to 10, this is environment dependant.

    <!-- Mailbox Replication Service configuration

        Setting Name - Default, MinValue, MaxValue
       
        MaxRetries - 60, 0, 1000
        MaxCleanupRetries - 0, 0, 100
        RetryDelay - 00:00:10, 00:00:10, 00:10:00
        MaxMoveHistoryLength - 2, 0, 100
        MaxActiveMovesPerSourceMDB - 10, 0, 100
        MaxActiveMovesPerTargetMDB - 10, 0, 100
        MaxActiveMovesPerSourceServer - 50, 0, 1000
        MaxActiveMovesPerTargetServer - 10, 0, 1000
        MaxTotalMovesPerMRS - 100, 0, 1024
        FullScanMoveJobsPollingPeriod - 00:10:00, 00:03:00, 1.00:00:00
        MinimumTimeBeforePickingJobsFromSameDatabase - 00:00:04, 00:00:00, 01:00:00
        ServerCountsNotOlderThan - 00:10:00, 00:00:00, 01:00:00
        MRSAbandonedMoveJobDetectionTime - 01:00:00, 01:00:00, 12:00:00
        BackoffIntervalForProxyConnectionLimitReached - 00:30:00, 00:00:30, 1.00:00:00
        DataGuaranteeCheckPeriod - 00:00:10, 00:00:01, 02:00:00
        DataGuaranteeTimeout = 00:30:00, 00:00:00, 12:00:00
        DataGuaranteeLogRollDelay = 00:01:00, 00:00:00, 12:00:00
        EnableDataGuaranteeCheck = false, false, true
        DisableMrsProxyCompression = false, false, true
        DisableMrsProxyBuffering = false, false, true
        MRSProxyLongOperationTimeout = 00:20:00, 00:01:00, 02:00:00
        MinBatchSize = 100, 2, 1000
        MinBatchSizeKB = 256, 16, 16384
      -->
     
      <MRSConfiguration
        MaxRetries = "60"
        MaxCleanupRetries = "0"
        MaxStallRetryPeriod = "00:15:00"
        RetryDelay = "00:00:10"
        MaxMoveHistoryLength = "2"
        MaxActiveMovesPerSourceMDB = "10"
        MaxActiveMovesPerTargetMDB = "10"
        MaxActiveMovesPerSourceServer = "50"
        MaxActiveMovesPerTargetServer = "10"
        MaxTotalMovesPerMRS = "100"
        FullScanMoveJobsPollingPeriod = "00:10:00"
        MinimumTimeBeforePickingJobsFromSameDatabase = "00:00:04"
        ServerCountsNotOlderThan = "00:10:00"
        MRSAbandonedMoveJobDetectionTime = "01:00:00"
        BackoffIntervalForProxyConnectionLimitReached = "00:30:00"
        DataGuaranteeCheckPeriod = "00:00:10"
        DataGuaranteeTimeout = "00:30:00"
        DataGuaranteeLogRollDelay = "00:01:00"
        EnableDataGuaranteeCheck = "true"
        DisableMrsProxyCompression = "false"
        DisableMrsProxyBuffering = "false"
        MRSProxyLongOperationTimeout = "00:20:00"
        MinBatchSize = "100"
        MinBatchSizeKB = "256" />
    </configuration>


    3. On MAIL servers restart Exchange Replication Service


    This now means that mailbox moves will complete with warning still, but there is no retry, and no delays.

    I too have an open case with Microsoft as this is meant to be fixed, I'm waiting on a proper solution from them and I'll update again when I have it!

    • Edited by Jon __R Friday, July 05, 2013 10:38 AM edit
    Friday, July 05, 2013 10:35 AM
  • Thanks for this suggestion :) we can't apply yet the RU1 so this solution as a workaround is a good one :)

    fcnet

    Friday, July 05, 2013 3:07 PM
  • Thanks for this suggestion :) we can't apply yet the RU1 so this solution as a workaround is a good one :)

    fcnet


    Rollup one didn't fix it for us anyway even though it was meant to.
    Monday, July 08, 2013 9:54 AM
  • Rollup 1 for Exchange 2010 SP3 fixed the problem for me.

    I've been trying to migrate users from exchange 2003 sp2, to exchange 2010 sp3, but was getting the:

    07/08/2013 14:20:09 [server] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).

    type delays/errors.

    The Ex2003 hotfix 940012 made no difference for me, but after the rollup1 update the server no longer waits 2.5 mins after each mailbox move before continuing.

    Next problem to work on, is to import more than 2 mailboxes at once :)

    thanks

    Wednesday, August 07, 2013 2:45 PM
  • Next problem to work on, is to import more than 2 mailboxes at once :)

    Change the values in MSExchangeMailboxReplication.exe.config as shown on all CAS and MAIL servers involved in moving, and restart Mailbox Replication service on MAIL servers.


    <!--Mailbox Replication Service Configuration

     MaxActiveMovesPerSourceMDB - 10, 0, 100
    MaxActiveMovesPerTargetMDB - 10, 0, 100
    MaxActiveMovesPerSourceServer - 50, 0, 1000
    MaxActiveMovesPerTargetServer - 10, 0, 1000

    <MRSConfiguration
        MaxMoveHistoryLength = "10"
        MaxActiveMovesPerSourceMDB = "10"
        MaxActiveMovesPerTargetMDB = "10"
        MaxActiveMovesPerSourceServer = "50"
        MaxActiveMovesPerTargetServer = "10"

    In my values above, I wanted to move 10 mailboxes at a time, change your values accordingly.

    • Edited by Jon __R Wednesday, August 07, 2013 3:04 PM
    Wednesday, August 07, 2013 2:57 PM
  • I've ended my other support call with Microsoft, I gave up.

    The previous instances this was meant to be fixed are not fixed, it still isn't fixed in Rollup 1 for SP3.

    I'll stick with the manual workaround of leaving MRS configured for no cleanup attempts, and will manually clean the databases after running some mailbox moves.

    Wednesday, August 07, 2013 3:05 PM
  • still exist in RU2 for SP3....

    Viele Grüsse Georg

    Thursday, September 05, 2013 6:16 AM
  • I just checked, and now that we are on SP3 RU2 it's no longer an issue for us.

    First time I've had a move complete without these"Post-move cleanup failed. The operation will try again in 30 seconds.." in a long time.


    DQ

    Wednesday, October 23, 2013 9:44 PM
  • we are on 2010 SP3 RU5, and i'm still having this issue.   just opened a ticket with MS to see what to do to about this and clean it up...   sigh.   so frustrating...

    • Edited by detrichw Friday, May 16, 2014 8:44 PM
    Friday, May 16, 2014 8:38 PM
  • I encounter the same with 2010 SP3 with CU5, that should have solve this problem, but this is not the case, this problem is still there :

    Avertissement : Échec de réinitialisation de la boîte aux lettres cible une fois l'opération de déplacement terminée.

    Détails de l'erreur : MapiExceptionWrongServer: Unable to open mailbox "/o=XXXXX/ou=Exchange Administrative Group (XXXXXXXXX)/cn=Recipients/cn=userff7aa50d" on server "XXXXXXX". (hr=0x80004005, ec=1144)


    fcnet

    Wednesday, June 04, 2014 10:10 AM
  • Exchange 2010 sp3 with whatever latest updates

    still happening. same error after moving mailboxes.

    BUMP!

    Sunday, July 06, 2014 5:27 AM
  • Exchange 2010 sp3 with whatever latest updates

    still happening. same error after moving mailboxes.

    BUMP!


    Same problem here.  Does anyone know if SP3 RU6 fixes this?  If not hopefully RU7 will
    Thursday, August 14, 2014 1:34 AM
  • Doesn't look like it is fixed in RU6.  Seeing the issue on a new install of SP3 with RU6.
    Monday, September 08, 2014 3:25 PM