"Failed to clean up source mailbox after move" Error

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

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!

Similar Messages

  • Failed to clean up source mailbox after move

    Last year, we upgraded from Exchange 2007 to Exchange 2010 SP3. We moved mailboxes without issue.
    Today, I'm running Exchange 2010 SP3 rollup 6, and when I attempt to move any mailbox (existing or newly created ones), I have the exact same problem that is described in this article
    http://blogs.msdn.com/b/aacallo/archive/2013/03/20/error-with-moving-mailbox-in-exchange-2010-sp2-ru3.aspx
    The article references 2010 SP2, which I never had. I've always been 2010 SP3.  I followed the steps in the article to resolve, but is this a known issue with Exchange 2010 SP3?
    Sorry for posting in the 2013 forum, I couldn't find the 2010 forum

    Hello,
    Are you able to see the value of 'Message' property as the same error message while running the following cmdlets?
    (Get-MailboxStatistics -Identity "name" -IncludeMoveHistory).MoveHistory
    List all softdeleted mailboxes:
    $Mailboxes = Get-MailboxStatistics -Database DB01 | where {$_.DisconnectReason -eq "SoftDeleted"}
    Remove the store mailboxes
    $Mailboxes | foreach {Remove-StoreMailbox -Database $_.database -Identity $_.mailboxguid -MailboxState SoftDeleted}
    Finally check if you can still find such mailboxes
    Get-MailboxStatistics -Database DB01 | fl DisplayName,DisconnectReason
    Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

  • Warning: Failed to clean up the source mailbox after the move

    Hi!
    After moving a mailbox between databases (EMC or EMS), there is a warning: Warning: Failed to clean up the source mailbox after the move. Erro details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634).
    Users can successfully access mailboxes, but these mailboxes stay in disconected mailbox node on EMC, and it is shown on EMS afer command [PS] C:\> Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} and their databases are
    the old ones.
    We have recently upgraded from SP2 to SP2 RU4, but we´re not sure when this problem started.
    Our Environment:
    Windows Server 2008 R2 Enterprise SP1
    Windows Roles: File Services, Web Server (IIS)
    Exchange Server 14.02.0318.001 (Build 247.5) Roles MBX, DAG with one more MBX identical Server
    Antivirus: Forefront Endpoint Protection Version: 2.1.1116.0
    Virtualization: Yes – Hyper-V
    Applications: Backup Agent CA, SCCM Agent, SCOM Agent, HP Management Tools
    Any idea?
    Thankyou in advance!
    Fabio Martins MCDST/MCSA Brasil!!!

    I recently upgraded our Exchange 2010 servers (CAS/HUB and MBX) from SP1 to SP3 RU6 and now I'm encountering this issue when doing mailbox moves. I opened a support case with Microsoft and it appears that they are aware that SP 3 RU1 doesn't fix
    the issue in all cases. Below is the response I received from the support engineer.
    =====
    Based on my research and case experience, we have several customers report that even if they are running Exchange 2010 SP3 RU1 or later version(for example, one of customer is running Exchange 2010 SP3 RU4 and another is also in CU6 environment), they also
    have such issue. When they move mailbox, it completed with warning message that source mailbox can’t be cleaned up after the mailbox move operation. This issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox.
    Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move
    process when you move many mailboxes at the same time.
    Currently, the workaround is to remove the “SoftDeleted” mailboxes manually after move the mailbox using the command you shared to us.
    ==========================================
    1.    List all disconnected mailboxes in a database and display DisconnectReason if its SoftDeleted or Disabled
    Get-MailboxStatistics -Database "DB9" | Where-Object {$_.DisconnectDate -Notlike $NULL} | Format-Table DisplayName, DisconnectDate, MailboxGuid, DisconnectReason –Wrap
    2.    Remove a specific softdeleted mailbox
    Remove-StoreMailbox -database “DB9” -identity “User Alias here” -MailboxState SoftDeleted
    ==========================================
    And as I know, it has no impact on the mailbox usage, so we can ignore the warning message currently. Please rest assured that once we got more information about the issue, we will inform you ASAP.

  • Mailbox move completes but get "Failed to reset the target mailbox after the move" 481/481

     
    moving a mailbox from exchange 2013 to exchange 2010: it completes but the process tries to reset the target mailbox as a final step about 481 times then gives permanent exception error:
    Failed to reset the target mailbox after the move. Attempt 481/481. Error: SuitabilityDirectoryException
    Target mailbox reset operation was not replicated. Error: TargetMailboxConnectionWasLostPermanentException
    Anand_N

    I have tried moving several different accounts, none of them admin accounts, all getting the same error. I am logged in as domain admin with full rights to exchange. The issue occurs when moving mailboxes from exchange 2013 to exchange 2010.
    1/30/2014 7:24:56 AM [e1] Move has completed and final clean up has started.
    1/30/2014 7:24:57 AM [e1] Source mailbox 'Primary (4bfda0fd-c991-4d40-8f0f-394411ef6848)' was successfully cleaned up after the move.
    1/30/2014 7:24:57 AM [e1] Failed to reset the target mailbox after the move. Attempt 1/481. Error: CouldNotFindDCHavingUmmUpdateTransientException.
    1/30/2014 7:24:57 AM [e1] Post-move cleanup failed. The operation will try again in 30 seconds (1/481).
    1/30/2014 7:25:32 AM [e1] Failed to reset the target mailbox after the move. Attempt 2/481. Error: SuitabilityDirectoryException.
    1/30/2014 7:25:32 AM [e1] Post-move cleanup failed. The operation will try again in 30 seconds (2/481).
    This is four hour wait period. before getting the error :
    Target mailbox reset operation was not replicated. Error: TargetMailboxConnectionWasLostPermanentException
    Anand_N

  • Exchange 2010 SP3 Move Mailbox fails on every mailbox with Fatal error MapiExceptionJetErrorIndexNotFound has occurred

    We are currently running Small Business Server 2003 with Exchange 2003 SP2 and are migrating to Server 2008 R2 with Exchange 2010 SP3 as an interim before moving to Server 2012 R2 with Exchange 2013 SP1. The mailbox move reaches 95% before failing with the
    message "Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
    Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetPropsSpecific [7]
        Lid: 21921   StoreEc: 0x40380   
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetReceiveFolderTable [104]
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetAllPerUserLtids [125]
        Lid: 17082   ROP Error: 0xFFFFFA84
        Lid: 29793  
        Lid: 21921   StoreEc: 0xFFFFFA84
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753  
        Lid: 21817   ROP Failure: 0xFFFFFA84
        Lid: 25738  
        Lid: 18570   StoreEc: 0xFFFFFA84
        Lid: 23370   StoreEc: 0xFFFFFA84
        Lid: 24302  
        Lid: 32494   StoreEc: 0xFFFFFA84
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
       at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
       at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
       at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: ISourceMailbox.CopyTo
    OperationSide: Source"
    This is happening on every mailbox we attempt to move. Any help would be appreciated

    Thanks for responding
    I'm already using BadItemLimit of 50. The largest corrupt message that was skipped is 10.
    We're on Small Business Server Standard Edition which only permits one mailbox store. I should mention that the interim machine (where Exchange 2010 is installed) is a Hyper V virtual machine
    Here is the entire message from the log:
    11/28/2014 7:18:07 PM [VRTL-SVR2008] 'PeacePresbyterianChurch.local/MyBusiness/Users/SBSUsers/Dev Mathura' created move request.
    11/28/2014 7:18:27 PM [VRTL-SVR2008] The Microsoft Exchange Mailbox Replication service 'VRTL-SVR2008.PeacePresbyterianChurch.local' (14.3.123.2 caps:07) is examining the request.
    11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to target mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'Mailbox Database 0224662151', Mailbox server 'VRTL-SVR2008.PeacePresbyterianChurch.local' Version 14.3 (Build 123.0).
    11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to source mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'PEACE-SERVER\First Storage Group\Mailbox Store (PEACE-SERVER)', Mailbox server 'peace-server.PeacePresbyterianChurch.local' Version
    6.0 (Build 7654.0).
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Request processing started.
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Mailbox signature will not be preserved for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)'. Outlook clients will need to restart to access the moved mailbox.
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Source mailbox information before the move:
    Regular Items: 20, 1.906 MB (1,998,818 bytes)
    Regular Deleted Items: 3, 7.803 KB (7,990 bytes)
    FAI Items: 20, 0 B (0 bytes)
    FAI Deleted Items: 0, 0 B (0 bytes)
    11/28/2014 7:18:39 PM [VRTL-SVR2008] Initializing folder hierarchy in mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Folder hierarchy initialized for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: LoadingMessages. Percent complete: 20.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)' contains 3 soft-deleted items (7.803 KB (7,990 bytes)). They won't be migrated.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CopyingMessages. Percent complete: 25.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Copy progress: 0/38 messages, 0 B (0 bytes)/1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:41 PM [VRTL-SVR2008] Messages have been enumerated successfully. 38 items loaded. Total size: 1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:43 PM [VRTL-SVR2008] Initial seeding completed, 38 items copied, total size 1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:44 PM [VRTL-SVR2008] Final sync has started.
    11/28/2014 7:18:45 PM [VRTL-SVR2008] Stage: FinalIncrementalSync. Percent complete: 95.
    11/28/2014 7:18:46 PM [VRTL-SVR2008] Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
    Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetPropsSpecific [7]
        Lid: 21921   StoreEc: 0x40380  
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetReceiveFolderTable [104]
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetAllPerUserLtids [125]
        Lid: 17082   ROP Error: 0xFFFFFA84
        Lid: 29793 
        Lid: 21921   StoreEc: 0xFFFFFA84
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753 
        Lid: 21817   ROP Failure: 0xFFFFFA84
        Lid: 25738 
        Lid: 18570   StoreEc: 0xFFFFFA84
        Lid: 23370   StoreEc: 0xFFFFFA84
        Lid: 24302 
        Lid: 32494   StoreEc: 0xFFFFFA84
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
       at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
       at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
       at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: ISourceMailbox.CopyTo
    OperationSide: Source
    Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)
    PropTags: [ContainerHierarchy; ContainerContents]
    11/28/2014 7:18:46 PM [VRTL-SVR2008] Relinquishing job.

  • Clean remote Mailbox after migration

    Hello ,
    I am Migrating mailbox users form Exchange 2007 to Exchange 2010 SP3 some users after Migration there Mailbox still in exchange 2007 as mailbox user instated of mail user  and in exchange 2010 as mail box user  .
    but its for some users .
    can you help me please why it happen

    Hi,
    Do you mean the mailbox in the original mailbox change to the soft-deleted state?
    If so, I recommend you check MAS's suggestions.
    When mailboxes are moved from an Exchange 2010 SP1 database to any other database, Exchange doesn't fully delete the mailbox from the source database immediately upon completion of the move. Instead, the mailbox in the source mailbox database is switched
    to a soft-deleted state. For more details about this, you can refer to the following article.
    http://technet.microsoft.com/en-gb/library/dd298174(v=exchg.141).aspx#SoftDel
    Hope this is helpful to you.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Mailbox in 2 databases after Move

    Exchange 2010-SP3, Rollup7. Running on vSphere, Server 2008-R2
    On September 26, 2014 I moved 2 mailboxes from MB1 to MB2 as a test.  The next day I moved the mailboxes back from MB2 to MB1.  I ran this PS script:
    Get-MailboxStatistics -Database "MB01" | Sort totalitemsize -desc | select Database, DisplayName, TotalItemSize
    Get-MailboxStatistics -Database "MB02" | Sort totalitemsize -desc | select Database, DisplayName, TotalItemSize
    The users mailbox shows up in both Databases.
    My Questions:
    1. Will the mailboxes under MB02 delete once the retention period has expired?
    2. If the mailbox is on Litigation Hold, will the retention be ignored, thus leaving the mailbox in 2 databases indefinitely?
    Thanks.

    That is by design:
    http://technet.microsoft.com/en-us/library/bb232039(v=exchg.141).aspx
    Soft-deleted mailboxes   When mailboxes are moved from a Microsoft Exchange Server 2010 Service Pack 1 (SP1) 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. For more information, see
    Restore a Soft-Deleted Mailbox.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • MailBox Move Error With Exchange 2010 sp3

    I initiated a mailbox move for a specific mailbox and let it run all night. The next day, the user stated he cannot log into is mailbox and the error stated "mailbox is moving, check back later".
    Exchange stated the status of the move is "CompletedWithError". I noticed that the mailbox is still in the old database.
    I tried to remove the move request and received an error "couldn't find a move request that corresponds to this identity".
    I rebooted the exchange server.
    Exchange still shows the user in the old database
    There is no move requests in exchange
    The user is still experiencing the same error "You weren't able ti sign in because the mailbox is being move"
    I tried to initiated another move and received:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    John, Doe
    Failed
    Error:
    Couldn't switch the mailbox into Sync Source mode.
    This could be because of one of the following reasons:
      Another administrator is currently moving the mailbox.
      The mailbox is locked.
      The Microsoft Exchange Mailbox Replication service (MRS) doesn't have the correct permissions.
      Network errors are preventing MRS from cleanly closing its session with the Mailbox server. If this is the case, MRS may continue to encounter this error for up to 2 hours - this duration is controlled by the TCP KeepAlive settings on the Mailbox server.
    Wait for the mailbox to be released before attempting to move this mailbox again.
    MapiExceptionMailboxInTransit: Unable to open message store. (hr=0x80004005, ec=1292)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=163]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=264][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x50C     
        Lid: 26937  
        Lid: 21921   StoreEc: 0x50C     
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22787   Error: 0x0
        Lid: 13032   StoreEc: 0x8004010F
        Lid: 25848  
        Lid: 7588    StoreEc: 0x8004010F
        Lid: 25840  
        Lid: 6564    StoreEc: 0x8004010F
        Lid: 50999  
        Lid: 2567    StoreEc: 0x50C     
        Lid: 19452  
        Lid: 2199    StoreEc: 0x50C     
        Lid: 56415  
        Lid: 48223   StoreEc: 0x50C     
        Lid: 17097   StoreEc: 0x50C     
        Lid: 8620    StoreEc: 0x50C     
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x50C     
        Lid: 26297  
        Lid: 16585   StoreEc: 0x50C     
        Lid: 32441  
        Lid: 1706    StoreEc: 0x50C     
        Lid: 24761  
        Lid: 20665   StoreEc: 0x50C     
        Lid: 25785  
        Lid: 29881   StoreEc: 0x50C     
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.3.224.2&t=exchgf1&e=ms.exch.err.Ex7E66C2
    Exchange Management Shell command attempted:
    'ab.ad/CD/Users/doe, john' | New-MoveRequest -TargetDatabase 'Carlsbad_Mailbox'
    Elapsed Time: 00:00:00
    At this point, when trying to access the mailbox, exchange states its being moved... when trying to remove the move... Exchange does not see the move.
    any help is appreciated,

    Hi Cudflyn,
    Base on my search, you can try to increase the TCP Keep Alive Time for the servers involved in the move.You can refer to the following
    article to increase it:
    Mailbox Move Error - 'Couldn't switch the mailbox into Sync Source mode'
    Note: Just REMEMBER to DELETE the registry entry when the mailbox moves are compete!
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • I'm trying to clean up my mailbox and when I delete an item(s) I get a message that say's "operation could not be completed- file exists. Further, when I do this one message is copied (not deleted) to the trash folder. Can someone help me through this?

    I'm trying to clean my mailbox and when I click on delete or highlight and move to trash I get a message that says "operation could not be completed - file exists. Further, when I select a message or group of messages, one of them is copied (not deleted) to the trash folder. Can someone help me through this?
    Thanks.

    It's a POP account. I decided to clean up my mailbox today after noticing the computer was real slow after USA Today started sending their daily top stories with new graphics. Also before I noticed the problem with mail deletion - two things happened. 1) I updated security sofware as prompted by Apple and 2) downloaded Mackeeper and went throught some preliminary scans but did not buy their package. Thanks forn nstaying with me.

  • Clear out old messages in Exchange 2010 journal mailbox after messages are archived to .PST Getting Error on Date

    # THIS IS THE FIRST COMMAND THAT I RUN IN A SEPARATE .PS1 FILE. THIS SEEMS TO WORK FINE:
    New-MailboxExportRequest JournalMailbox -FilePath '\\dfsdr.dc.pud\PowershellEmailArchive\Journal.pst'
    # NEXT I AM TRYING TO CLEAN OUT EVERYTHING ELSE UP UNTIL 1-2 DAYS AGO BUT GETTING THIS ERROR:
    [PS] C:\scripts>.\CleanOutOldMsg.ps1
    Please adjust the date time. Make sure it is in the correct format.
        + CategoryInfo          : InvalidArgument: (:) [], ParserException
        + FullyQualifiedErrorId : 44F6D37F
    # HERE'S WHAT I'VE DONE:
    $global:startDate = (Get-Date).AddDays(-31).ToString('MM/dd/yyy')
    $global:endDate = (get-date).AddDays(-1).ToString('MM/dd/yyy')
    # HAVE TRIE THIS DATE FORMAT TOO:
    $endDate = (Get-Date).AddDays(-1).ToShortDateString()
    $startDate = (Get-Date).AddDays(-31).ToShortDateString()
    # AND ALSO THIS DATE FORMAT:
    # $endDate = Get-Date -Day 2 "00:00:00"
    # $startDate = $endDate.AddDays(-30)
    # $endDate = $endDate.ToShortDateString()
    # $startDate = $startDate.ToShortDateString()
    # THIS COMMAND GIVES DATE ERRORS:
    Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:'${startDate}'..'${endDate}'" -DeleteContent -Force
    # THIS COMMAND GIVES DATE ERRORS TOO:
    Get-Mailbox -Identity "JournalMailbox" | Search-Mailbox -SearchQuery "Received:'${startDate}'..'${endDate}'" -DeleteContent -Force
    # THIS WORKS:
    Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:02/07/2014..03/07/2014" -DeleteContent -Force
    # I FOUND SOME OF THE INFORMATION HERE:
    https://serverfault.com/questions/511610/how-can-i-move-exchange-items-to-a-pst-using-powershell
    Thanks in advance! Jim
    Sorry if I wasn't as clear as I could have been.  I'm trying to clean out the Journal mailbox after exporting the messages to a .PST file.  I've tried formatting the date different ways and when I check it the format seems OK. For some reason I'm
    still getting the same error.  I've tried this which was suggested and I received the same error listed above:
    Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:'${$startDate}'..'${$endDate}'" -DeleteContent -Force
    For some reason the -SearchQuery is not accepting the variable.
    Thanks,  Jim

    Thank You Yan Li!   I ran commands both ways and still received errors.  Here's the first command and the error message: 
    Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:"$startDate".."$endDate"" -DeleteContent -Force
    Error: 
    [PS] C:\scripts>.\CleanOutOldMsg.ps1
    A positional parameter cannot be found that accepts argument '02/10/2014..03/12/2014'.
        + CategoryInfo          : InvalidArgument: (:) [Search-Mailbox], ParameterBindingException
        + FullyQualifiedErrorId : PositionalParameterNotFound,Search-Mailbox
    Here's the result of the following command which is formatted a bit different per your suggestion:
    Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -searchQuery "Received:>$startDate and Recieved:< $enddate" -DeleteContent -Force
    [PS] C:\scripts>.\CleanOutOldMsg.ps1
    The property keyword isn't supported.
        + CategoryInfo          : InvalidArgument: (:) [], ParserException
        + FullyQualifiedErrorId : 34A6B2A1
    Would you happen to have any other suggestions?  Thanks in advance!  Jim

  • Export -mailbox to move emails older than 400 days to pst file

    i have written the below script
    $date = get-date
    $MailboxList = get-content "E:\del_users.txt"
    ForEach ($Mailbox in $MailboxList) {
    Export-Mailbox -Identity $Mailbox -PSTFolderPath E:\pstfiles\$mailbox.pst -BadItemLimit 1000000 -StartDate $date.adddays(-450).ToString('MM/dd/yyyy') -DeleteContent
    my target is to move all emails older than 450 days to a pst file. i ran this on one user and noticed his emails from today to 450th day from today was moved out.
    In simple terms, i want to move all emails in all sub-folders that are older than 01-January-2014. Once this is done and when he logs to owa or outlook he must be only be able to see emails from 01-Jan-2014 to 17-Mar-2015.
    how can i achieve this with the above script?
    cheers

    We are facing this error with few mailboxes which are exclusively in one DB under one Storage Group & the mailbox is on EX001 with Exchange 2007 SP1
    We have 2 exchange servers:
    EX001 - Exchange 2007 SP1
    EX002 - Exchange 2007 SP3 (fully updated)
    I have setup a Windows 8.1 32bit machine with Outlook 2013 for running the export-mailbox cmdlet to export mails to a PST file
    We are facing this error with few mailboxes which are exclusively in one DB under one Storage Group & the mailbox is on EX001 with Exchange 2007 SP1
    We I run the below script, 
    $date = get-date
    $MailboxList = get-content "E:\del_users.txt"
    ForEach ($Mailbox in $MailboxList) {
    Export-Mailbox -Identity $Mailbox -PSTFolderPath E:\pstfiles\$mailbox.pst -BadItemLimit 1000000 -StartDate “01/01/2005" -EndDate “12/31/2013" -DeleteContent
    I get the below error, only from some users and not all users.
    Error was found for User ([email protected]) because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: 
    MAPI or an unspecified service provider.
    error code: -1056749164
    I went through the link: https://social.technet.microsoft.com/Forums/en-US/3c75a6db-74a4-484c-a7f4-5b411900d09b/exchange-2007-exportmailbox-error-message-on-only-certain-mailbox?forum=exchangesvrdeploylegacy 
    I understand this is a permission issue and i have tried all of the below
    1. The user doing the export is a member of local administrator group in both source and target machine.
    2. the user doing the export is granted the exchange administrator role on EMC in both the source and target machine.
    3. Given full access permission to the username moving the mailbox to PST
    4. given receive-as permission to the username moving the mailbox to pst
    5. Given genericall access to the DB
    6. Create a New User account (EX: ExportAdmin)
    Add this account to a Exchange Server Administrator Permission Both Source and Target Exchange Mailbox Server
    Add this account to Local Administrators Group Member Both Source and Target Exchange Mailbox Server
    Make sure this account DO NOT HAVE ANY Domain Admin/Exterprise Admin permission(Just keep Domain User group permission)
    Assign Mailbox Full Access to this account by follow Cmdlet
    Get-Mailbox -Server "EX-CCR" | Add-MailboxPermission -User ExportAdmin -AccessRights FullAccess
    Runas with ExportAdmin account (Open EMC)
    Get-Mailbox -Server "EX-CCR" | Export-Mailbox -PSTFolderPath
    Done
    7. On the DB, we set the retention to 0
    however none of the above has helped me resolve my issue.
    Please help me correct this

  • Sent mail does not appear in sent mailbox after sending

    Sent mail does not appear in sent mailbox after sending

    From reports on this site, Yahoo mail doesn't work reliably with Mail. The following steps may help.
    Quit Mail. Force quit if necessary.
    Back up all data. That means you know you can restore the Mail database, no matter what happens.
    Triple-click the line below on this page to select it:
    ~/Library/Mail/V2/MailData/Envelope Index
    Copy the selected text to the Clipboard (command-C). In the Finder, select
    Go ▹ Go to Folder
    from the menu bar. Paste into the box that opens (command-V), then press return.
    A Finder window will open with a file selected. Move the selected file to the Desktop, leaving the window open. Other files in the folder may have names that begin with "Envelope Index". Move those files, if any, to the Trash.
    Log out and log back in. Relaunch Mail. It should prompt you to re-import your messages. You may get a warning that the index is corrupt and that Mail has to quit. Click OK.
    Test. If Mail now works as expected, you can delete the file you moved to the Desktop. Otherwise, post your results.

  • Empty mailboxes after importing from panther to tiger - can't solve

    Dear all,
    I have been happily using my ibook G3 300mhz for seven years now, running system nine first then jaguar then panther (currently 10.3.9).
    I have nearly all my emails from 98 onwards, which I first imported from eudora to eudora (8600 to ibook) and then from eudora on ibook to mail on ibook. I have a pop account and a mac account with an alias (.mac and IMAP therefore). I probably have about 10.000 emails scattered in many folders and subfolders. Some of my mac mails are even saved in folders belonging to my pop account (thus located on my mac).
    I've been waiting for the new macbook for a couple of months, had it for FOUR days now and seem unable to transfer my mail from my ibook to my macbook. I have tried both copying the whole mail folder and importing mailboxes from within mail.
    With the first option when I open mail it says it needs to import my messages and is then stuck on message 659. May be a corrupt message but I have no way of knowing which one it is and delete it from the library. With the second options it imports all boxes alright, even displaying a numebr of messages whcih appears realistic, but I get the usual "You need to take this account online in order to download it" message. The only messages I can actually see are those in my inbox for my .mac account and those still on the server for my pop account. Any and all messages in any of the other mailboxes (even the .mac ones which are definitely on the server) seem to have disappeared.
    I have even tried backing up from the ibook with mac backup and then restoring to the macbook (has worked for preferences, itunes playlist etc) the result is the same: boxes are there but appear empty.
    I think I have read all threads concerning similar problems but don't seem to find a suitable solution. I was so looking forward to getting my new computer and being able to use mail 2 and now I've been stuck for days, with a huge waste of time. Why can't my intel core duo with tiger do what my little ibook with panther did so successfully and faithfully, albeit admittetly really slowly?
    Needless to say I need to have all my messages exactly in the same mailboxes as I have them on my old comp, I certainly can't throw them into one huge box and sort them from there!
    Any help will be greatly appreciated. I am even willing to spend a few bucks on any conversion program that can do the job (although after just purchasing the macbook I shouldn't have to spend anything more) just to avoid this incredible waste of time.
    A faithful apple user who is getting kind of frustrated
    Diana

    Hello, Diana.
    I think I have read all threads concerning similar problems
    Have you read this in particular?
    Help! "You need to take this account online in order to download it."
    You won't find the solution to your problem there, but it should let you better understand it. In particular, if using Mail on the iBook under Mac OS X 10.3.9 is still an option, you may want to try to clean up your mailboxes there first, using the following article as a guidance:
    Overstuffed mailbox is unexpectedly empty
    Before start troubleshooting this, you should make a backup copy of the ~/Library/Mail folder, just in case.
    Post back with your observations.

  • DPM 2012 R2 - Failed to clean up data

    Hi,
    I'm hoping someone might be able to help me.
    I've recently been getting an error on one of our backup jobs, I've tried searching around for solutions but no-one seems to have had the exact same issue that I'm experiencing.
    The backup job is a shadow copy file backup of a complete volume.
    It's been working for the past few weeks but I'm now getting the error below when I try to run a consistency check. 
    People have reported issues similar which suggest executing the pruneshadowcopiesdpm2010.ps1 which I've tried but this seems to make no difference.
    The protection group is short term disk protection with a retention period of 14 days with file recovery points created at 11am, 1.30pm, 3.30pm and 8pm.  The job is currently reporting 32 recovery points which leads me to believe it shouldn't need to
    clean up any yet anyway.
    Any suggestions would be very much appreciated.
    Type: Consistency check
    Status: Failed
    Description: DPM failed to clean up data of old incremental backups on the replica for Volume D:\ on nas01.nwhs.local. Synchronization will fail until the replica cleanup succeeds. (ID 30134 Details: Cannot create a file when that file already exists (0x800700B7))
     More information
    End time: 29/04/2014 18:48:03
    Start time: 29/04/2014 18:48:02
    Time elapsed: 00:00:01
    Data transferred: 0 MB
    Cluster node -
    Source details: D:\
    Protection group: User Data
    Items scanned: 0
    Items fixed: 0

    RIS,
    The access denied can come if there is already a lock on the file( like Antivirus). 
    Can you let me know what version of DPM2012R2?   if you goto about DPM you it will give you exact version 4.x.xxxx.x.  You stated you had AV exclusions set
    "We do run Sophos Antivirus but it does have exceptions set and the volumes that are being protected do not store any Sophos related data."
    I want to ensure all are set from -
    http://technet.microsoft.com/en-us/library/hh757911.aspx - if you can test disabling AV that may help.
    Can you check the event logs on DPM server and PS during the failure to see if there is anything else running that may lock the files?
    There may also be a "failedfiles.dat" that may due to unsupported files see link below for assistance troubleshooting that -
    http://social.technet.microsoft.com/Forums/en-US/f7de60cd-841f-4d22-862e-aaf3723717c7/dpm-could-not-log-files-that-were-skipped-during-backup-to-volumexxxxxfailedfilesdat-id?forum=dataprotectionmanager
    How to read failedfiles.dat if there is one -
    http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/27c48816-dabb-41a0-b800-6e1ac2fc1ed5
    Also what is the OS version of the DPM server?  Are you doing any dedupe\ODX\Thin provisioning on the protected server? 
    Ultimately we may need a ticket to determine what is locking out the file during the failure but please let me know the answers to the above and I will see if that helps.  Thanks
    Regards, A.Nadar, This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights.

Maybe you are looking for