locked
MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)__ RRS feed

  • Question

  • Hi to all,

    I have an Exchange 2010 sp2 Rollup3 was recently migrated from Exchange 2003. Exchange 2003 has already been removed, now when I try to make moves between bases the error below is displayed:

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

    I have to manually run the cleanup to clear the mailbox database .

    Has anyone got this problem? thanks for any help

    Wednesday, June 27, 2012 2:07 PM

All replies

  • Hi ,

    Please try to do the following steps:

    Ran Get-Mailbox –Aribtration

    If the the arbitration mailboxes still on Exchange 2003, we need to move them to Exchange 2010.

    Ran Set-ADServerSettings -ViewEntireForest $True

    Do you removed database in Exchange 2003 ?

    
    
    Set-AdServerSettings:
    http://technet.microsoft.com/en-us/library/dd298063.aspx
    
    

    
    

    Wendy Liu

    TechNet Community Support


    • Edited by wendy_liu Thursday, June 28, 2012 10:44 AM
    Thursday, June 28, 2012 10:43 AM
  • HY Wendy,

    Thank you for replay. Yes, I removed the Exchange 2003 from organization, I ran the command but no success.  Below some part of move log:

    

    Falha ao limpar a caixa de correio de origem 'Primário (8c566269-8645-42cd-b0ad-a7105ec24f0c)' após a movimentação. Tentativa 6/6.
    Detalhes do erro: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

       em Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       em Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags)
       em Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags)
       em Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29()
       em Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       em Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags)
       em Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b()
       em Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    29/06/2012 20:37:17 [] Solicitação concluída.

    Friday, June 29, 2012 11:46 PM
  • 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 5, 2012 6:29 PM
  • Also worth noting, the move request performed before disabling the mailbox shows the following inconsistency:

    Source version: Version 14.2 (Build 309.0)
    Target version: Version 14.2 (Build 247.0)

    This is a single server environment so there should be no version differences.

    Also noted here:

    http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/e12a58ce-5b93-4129-b998-b8f06588ebc6


    • Edited by BGCTNV Thursday, July 5, 2012 6:43 PM
    Thursday, July 5, 2012 6:39 PM
  • Hmm... I'm running into the same exact issue, with Ex2010 SP2, with UR 3 installed (the error text being the same as the above posters -- "Warning: Failed to clean up the source mailbox after the move.
    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)").

    We are currently in the middle of a Exchange 2007-to-2010 migration, but this error occurs even when attempting to move a brand new Exchange 2010 mailbox. On my move request (to a different database on the same Ex2010 server), I see that my Source version is also Version 14.2 (Build 309.0), with Target version:  Version 14.2 (Build 247.0).

    Anyone have any ideas on this one?


    Monday, July 23, 2012 6:18 PM
  • Hi All,

    anyone have solved this issue? I have same problem move request completed with warning ("Warning: Failed to clean up the source mailbox after the move.
    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)"); Source version is Version 14.2 (Build 309.0), with Target version:  Version 14.2 (Build 247.0).

    Best regards,

    Max

    Tuesday, July 24, 2012 7:56 PM
  • I'm also having this issue. Moving a user between databases on the same server? Exchange 2010 SP2 Update3 installed. Also having the Database version mismatch problem.

    To correct I just set the database to delete old mailboxes after 1 day, next day they were cleaned up. But I know this should not be happening in the first place.

    • Edited by CanadianMade Friday, August 3, 2012 1:41 AM added more info
    Tuesday, July 31, 2012 9:01 PM
  • Hi,

    I am seeing the exact same issues with build numbers and the move completed with warnings; has anyone got an update on this?

    Any help much appreciated.

    Thursday, August 2, 2012 3:27 PM
  • I also have this issue:

    Mailbox move to another DB on the same server with newly created databases (E2K10 SP2 UR4) gives warning/error:

    The Microsoft Exchange Mailbox Replication service completed request <mailbox> with warnings.
    Warning: Failed to clean up the source mailbox after the move.
    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

    The mailbox has been moved and can be accessed. I think this is a bug which MS should solve.

    Anyone more news? 

    Martijn

    Monday, August 27, 2012 6:13 PM
  • Same issue here..

    E2010 SP2 RU4

    Wednesday, August 29, 2012 11:24 PM
  • Same issue here.

    All servers are patched to SP2 RU4. I went from SP2 with no RU straight to RU4 and any other patches available for the servers. I experienced this issue on the first mailbox moves after the updates. Does anyone have an idea which RU this started with?

    Thursday, August 30, 2012 4:37 PM
  • Same issue here...

    I'm running 2010 SP2 RU3.  I can move from Exchange 2007 SP3 to 2010 without errors but I receive the error moving between 2010 databases.

    rudif

    Thursday, August 30, 2012 5:04 PM
  • Hi,

    We are facing the same issue, while moving mailboxes from 2010 to 2010. I am able to move mailboxes from 2007 to 2010 successfully. I have checked we are running all the servers at same RU level.

    Looking for a solutions.....

    Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

    Tuesday, September 11, 2012 1:34 PM
  • Mbx move to another DB on same server in my test environment with Exchange 2010 SP2 UR4:

    • Mbc move of 10 MB mbx takes 3 minutes; seems to be a little long
    • Mbx move gets completed but with Event Viewer warnings: 9660 Warning:failed to sign in because their mailbox is in the process of being moved. Is this warning normal behavior? User is not logged on or connected with OL client.

    So, I can't yet reproduce the MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) error.

    Martijn

    Wednesday, September 12, 2012 7:04 AM
  • I am getting the same error after going from Exchange 2010 SP2 RU2 to RU4

    Everything was fine when running on RU2

    Monday, September 17, 2012 6:50 PM
  • 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


    ExchangeGeek (MCITP,Enterprise Messaging Administrator)

    ***Don't forget to mark helpful or answer***

    • Proposed as answer by Karl Ernstzen Friday, September 21, 2012 11:24 AM
    Monday, September 17, 2012 7:15 PM
  • That is a useful command. Thank you.

    I am wondering why this has started happening after applying the latest RU patch  :-/

    Monday, September 17, 2012 7:25 PM
  • 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
  • I would caution against running the Remove-StoreMailbox command against the disconnected mailboxes unless you really want to purge them. Doing that will bypass your built-in deleted mailbox retention time

    The source mailbox should be in a soft-deleted, diconnected state after a mailbox move, that is by design (http://technet.microsoft.com/en-us/library/bb232039.aspx)

    Other than the error you see when moving the mailbox, is there any other issues or problem seen?

    (P.S. I would open a case with Microsoft Suppport)


    Friday, September 21, 2012 11:17 AM
  • If you have Ops Man in your environment, the mailboxes might be Quarantined

    , check this: http://blogs.technet.com/b/exchange/archive/2012/06/28/mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

    See brief on Quaranitne: http://support.microsoft.com/kb/2603736#appliesto

    and fix to remove Quarantine (Exch 2010 and below) :   http://technet.microsoft.com/en-us/library/bb331958.aspx

    Make sure you do reg backup, and reg edits on the box where the mailboxes (databases) are mounted.

    For Exchange 2013 see: http://technet.microsoft.com/en-us/library/jj218650(v=exchg.150).aspx

    Hope this helps

    • Proposed as answer by Karl Ernstzen Wednesday, September 26, 2012 12:12 PM
    • Unproposed as answer by Karl Ernstzen Wednesday, September 26, 2012 12:26 PM
    Friday, September 21, 2012 12:07 PM
  • Please get a case with us opened to track this, and  do not mess with quarantine or the soft delete mailboxes.


    Cheers,

    Rhoderick

    Microsoft Premier Field Engineer, Exchange

    Blog: http://blogs.technet.com/rmilne  Twitter:     LinkedIn:

    Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Friday, September 21, 2012 1:22 PM
  • Hello,

    Did you manage to get a fix for this? I'm currently running Exchange 2010 SP2 RU4 and experiencing the exact same issue as you.

    Many thanks,
    Joanne

    Monday, September 24, 2012 2:52 PM
  • I haven't found a fix yet and am still getting this error. Once I have verified the mailbox has been successfully moved to the target I clean up the old one by running this command:

    Remove-StoreMailbox -Database db_name -Identity "User name" -MailboxState Softdeleted

    Monday, September 24, 2012 3:00 PM

  • Ok, thanks for getting back to me and for the work around but i'm just away to do a mass mailbox migration from Exchange 2007 to Exchange 2010 and i'm not keen on manually cleaning up every mailbox afterwards.

    I'll give Microsoft support a call and see if they have a fix for this yet.

    Monday, September 24, 2012 3:06 PM
  • If you do find a fix for this please post it here  :-)

    Thanks

    Monday, September 24, 2012 3:13 PM

  • Unfortunately there is no fix for this yet, Microsoft are still working on it!

    I've been given the following work around in the meantime -

    To Speed up the move request:
    On ALL CAS Servers
    Edit C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config
    --Find the following counter: “maxCleanupRetries”
    --The default value is 5. Change to 1.
    Restart MSExchangeMailboxReplication Service
     
    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}

    Tuesday, September 25, 2012 3:25 PM
  • Thanks for the update and helpful tips Jo
    Tuesday, September 25, 2012 3:39 PM
  • I am having the same problem. Should I do a soft delete or not?

    Bill


    • Edited by BowlingSS Tuesday, October 16, 2012 7:18 PM
    Tuesday, October 16, 2012 7:18 PM
  • I am having the same problem. Should I do a soft delete or not?

    Bill



    I have been soft deleting any mailboxes that I moved with this error and have had no problems.
    Tuesday, October 16, 2012 7:35 PM
  • Jo,

    Are you still working with Microsoft on this?  Have you been giving a fix for it yet or are you still using the workaround?

    Friday, October 19, 2012 12:50 PM
  • Maybe this is fixed with Exchange 2010 SP2 UR5. However, MS removed UR5 from their websiste because of problems :-(

    Martijn

    Wednesday, November 21, 2012 1:18 PM
  • Unfortunately I can't see a fix for this issue in "Update Rollup 5 for Exchange Server 2010 SP2" - http://support.microsoft.com/?kbid=2582113

    I'll contact the Microsoft engineer that i previously spoke to and see if he has an update.

    Jo

    Wednesday, November 28, 2012 11:42 AM
  • That link is for for Exchange 2010 SP1.  Rollup 5 for SP2 was pulled due to having bugs in it causing issues with DAGs a week or so ago.
    Thursday, November 29, 2012 10:24 PM
  • I'm having this issue as well, we just upgraded to Exchange 2010 SP2 RU4. I see this in the details for mailbox move requests:

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

    Thursday, December 6, 2012 10:20 PM
  • Just finished updating all our servers to RU4 v2 and we are getting the same errors.  QA is slipping.
    Saturday, December 8, 2012 9:16 AM
  • Hey Guys,

    to summerize the threads.

    a. A move in a DAG Cluster Ex 2010 Sp2 RU4v2 will end in an errror that the source mailbox cannot cleaned up.

    b. MS has no solution for that.

    c. You can do Remove-StoreMailbox -Database db_name -Identity "User name" -MailboxState Softdeleted to remove source mailbox

    d. You can move all Mailboxes from source DB into new DB and delete the hole source DB, wich will do the same.

    Correct

    Regards Timo


    MCSE / MCSA on Windwos 2000 / 2003

    Tuesday, December 18, 2012 8:36 PM
  • Yes...

    No fix yet from MS.


    Om

    **My posts are provided “AS IS” without warranty of any kind**

    Wednesday, December 19, 2012 2:56 AM
  • Checked now in my eviornment:

    Move from a DB to another DB hosted on the same server / or DAG Node will result in the error we talk about.

    Move from a DB of Server A to DB of Server B, in my case from one DAG Node to another Node, will succeed without any error.

    Regards Timo


    MCSE / MCSA on Windwos 2000 / 2003

    Wednesday, December 19, 2012 8:27 PM
  • Hi,

    had the same Problem on one of my servers. Tried to apply RU5 V2 which ended in an error due to installed WMF 3.0. After uninstalling WMF 3.0 from the server the Mailbox move ended without any errors.

    Here is an article from the product Team in which they recommend to uninstall WMF 3.0 if installed.

    http://blogs.msdn.com/b/powershell/archive/2012/12/20/windows-management-framework-3-0-compatibility-update.aspx

    I have written an blog article (german) about that problem here:

    http://www.groeby.net/?p=67

    Greetings

    Christian


    Christian Groebner MVP Forefront

    Monday, January 7, 2013 11:01 PM
  • All,

    I'm seeing the same, we recently applied RollUp 5v2 on exchange 2010 SP2. 2 Node DAG.

    --Brian

    Wednesday, January 30, 2013 9:21 PM
  • Same issue here.  Exchange 2010 SP2 2-node DAG.  Move mailboxes from one DB01 to DB02.

    Mailboxes do not show as soft deleted.

    Details:

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

    Log:

    2/26/2013 3:51:01 PM [exc02] Connected to target mailbox 'Primary (82409418-b95c-4681-9a48-a8687713a5c7)', database 'DB02', Mailbox server 'EXC01.madonna.local' Version 14.2 (Build 247.0).
    2/26/2013 3:51:01 PM [exc02] Connected to source mailbox 'Primary (82409418-b95c-4681-9a48-a8687713a5c7)', database 'DB01', Mailbox server 'EXC01.madonna.local' Version 14.2 (Build 328.0).


    • Edited by tjcarst Tuesday, February 26, 2013 10:43 PM
    Tuesday, February 26, 2013 10:41 PM
  • I saw the same issue with RU5v2 and Exchange 2010 SP2. I did see one thing - when the mailbox was in move, I had failed the database from one node to the other and thats when i came across this error for those mailbox moves.
    Thursday, March 14, 2013 7:35 PM
  • Has a solution for this ever been found?

    I'm running a fresh exchange 2010 SP3 environment and am having this issue.


    Systems Administrator

    Tuesday, April 2, 2013 7:28 PM
  • Did you call into support Sean ?

    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Tuesday, April 2, 2013 8:58 PM
  • Hi

    Same issue on my newly upgraded 2010 SP3 boxes ... Any fixes/workarounds avalilable?

    Weird ... seems to have been a problem since SP2 RU3 ... rather annoying that MS hasn't been presented a fix for this yet!

    BR


    System Consultant

    Friday, May 10, 2013 9:20 AM
  • Hi All,

    I have a fresh 2010 SP3 environment and i am migrating Mailboxes from 2003, but it also happens for local moves 2010 to 2010.

    Come on MS sort this out!

    Matt

    Tuesday, May 21, 2013 2:10 PM
  • Bump.

    I just installed SP3 RU1 and still not fixed.

    Anyone heard anything from MS?

    Friday, July 19, 2013 5:38 AM
  • Hi

    Same problem here.

    I have a new install of Exchange 2010 SP3 with RU2.

    Moving a mailbox from one database to another local on the 2010.

    But we don't get the warning when we move a mailbox from our 2007 to the 2010. It's only when we move between databases on the 2010 server.

    It also says.
    Source Version: 14.3 (Build 158.0)

    Target Version: 14.3 (Build 123.0)

    Come on Microsoft!

    /Casper

    Friday, September 20, 2013 10:25 AM
  • Yes same here,

    I had this problem om SP2 UR 7 and when doing some digging and reading change logs i decided to upgrade to SP3 UR2

    The problem still persists !

    Warning failed to cleanup the source mailbox after the move. error detailed: Mapi ExceptionUnexpectedMailboxState: Unable to delete mailbox.

    (hr=0x80004005, ec=2634)

    Saturday, October 5, 2013 8:10 AM
  • Same issue here. Fresh Exchange 2010 DAG Installation. No Migration from previous Exchange versions.

    Hase someone any news from microsoft?

    Tuesday, November 19, 2013 3:21 PM
  • We have 2010 SP3 RU4 installed and this still happens with mailboxes moved from one 2010 database to another.  It doesn't happen with all moves, though, like it did with SP2 RU3+.

    Wednesday, January 15, 2014 3:00 PM
  • Hi together,

    the moved Mailbox with the warning:

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

    appear under disconected Mailboxes. So in my opinion they should be deleted automaticly after the keep deleted mailboxes for x days is reached.

    Best Regards

    Claudius


    Gruß Claudius

    Thursday, January 30, 2014 2:28 PM
  • This worked for me. 

    http://www.blackforce.co.uk/2013/04/06/exchange-move-request-error-failed-to-clean-up-the-source-mailbox-after-the-move

    Get-MailboxStatistics –Database | Where-Object {$_.DisconnectReason –eq “Softdeleted”} | ForEach {Remove-StoreMailbox –Database $_.database –identity $_.mailboxguid –MailboxState Softdeleted}
    Thursday, February 13, 2014 9:11 PM
  • is there any hotfix or update for this error ? My environment is Exchange 2010 SP3 RU2.

    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. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter: @ikrisna

    Monday, June 16, 2014 6:02 AM
  • Wow! Some many people with the same error/issue during a long period of time and Microsoft fails to get it fixed?

    You can also add me to the "same issue here" list. 

    We are in the process of moving from exchange 2003 -> exchange 2010. Mailbox move withing the exchange 2010 stores are giving me the exact same warning. Maybe this is fixed in exchange 2013, as we will move to 2013 as soon as every 2003 server is removed.

    Thursday, July 31, 2014 10:50 PM
  • I just run soft delete and clean-mailboxdatabase. This resolve my issue.


    Tuesday, July 7, 2015 12:50 PM
  • can someone tell me what is the outage or end user impact due to this warning message?

    If this warning message has no impact to end users , why are we worried about this warning, we can leave it to the default, so that the DB maintainance would delete these mailbox's from the disconnected mailbox container.

    Monday, August 24, 2015 12:24 AM