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.

Similar Messages

"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.

<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!

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]

Sound fails when opening new sound "sources" quickly after one another

I hava a problem when the sound on Arch running XFCE.
At first, there was no sound. I searched for a solution, and found one that seemingly did help. I created .asoundrc in ~ with this text:
pcm.!default {
type plug
slave.pcm {
@func getenv
vars [ ALSAPCM ]
default "hw:PCH"
This should set the default sound card (as my motherboard have both PCH and HDMI sound card).
Now there is sound, but it fails when i switch from different sound "sources" (like different YouTube-videoes). For the sound to work again, I have to refresh the page, and generally wait some 20 seconds.
My motherboard is MSI GAMING 3 Z97, and I don't have more sound card than what is on that card.
So I was hoping for some help. It's not a big problem, but a bit irritating. :)

I'm going to go out on a limb and guess that you've got a custom timecode field somewhere in your production and/or asset metadata group(s), right? And I'm going to further guess that this timecode field has dashes in it like this --:--:--:--, right? If so, try this: Click the arrow next to the timecode field and adjust the timecode so that it has a number (it doesn't matter what the number is as long it's not dashes - "00:00:00:00" is fine). Then Save this asset, close it and then reopen it and see if the beeping madness has vanished. Then, to make this change permanent for all of your new assets, make sure to edit the default value of any custom timecode fields to put zeros (or some other numeric default value) into them when a new asset is generated. If the asset still beeps when you open it, check the other metadata groups in your set to see if there isn't another empty timecode field lurking in the shadows.
Jason

Error after a move mailbox

Exchange 2010 sp3, 2 hubs, 2 mbs
i'm moving several mailboxes to a lower db size limit and have encountered the following error:
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)
so far, I have three mailboxes that gave that error. all of them returned 100% completed but with warning.
should I continue the move of mailboxes?

Exchange 2010 sp3, 2 hubs, 2 mbs
i'm moving several mailboxes to a lower db size limit and have encountered the following error:
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)
so far, I have three mailboxes that gave that error. all of them returned 100% completed but with warning.
should I continue the move of mailboxes?
I have seen that many times in Exchange 2010.
If the mailbox is successfully moved and users can connect to the new mailbox, I would continue.
You should be able to see the source mailbox as disconnected on the source database:
http://technet.microsoft.com/en-us/library/bb232039(v=exchg.150).aspx
Disconnected Mailboxes
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

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

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

Couldn't Connect to the source mailbox - New-MailboxRestoreRequest

Having major issues with recovering a mailbox for a user, we have created a recovery mailbox db and it's mounted fine and not in a dirty shutdown state, but when I try any variations of 'New-MailboxRestoreRequest' I get the below message:
New-MailboxRestoreRequest -SourceDatabase "RDB18" -SourceStoreMailbox "roger Hodges" -TargetMailbox otest -AllowLegacyDNMismatch
Couldn't connect to the source mailbox.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxRestoreRequest], RemotePermanentException
    + FullyQualifiedErrorId : 3E0814F2,Microsoft.Exchange.Management.RecipientTasks.NewMailboxRestoreRequest
I've tried Restore-Mailbox also and get the below error:
Restore-Mailbox -Identity "otest" -RecoveryDatabase "RDB18" -RecoveryMailbox "Roger Hodges" -TargetFolder Recovery
Confirm
Are you sure you want to perform this action?
Recovering mailbox content from mailbox 'Roger Hodges' in the recovery database 'RDB18' to the mailbox for 'OWA Test
([email protected])'. This operation may take a long time to complete.
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
Error was found for OWA Test ([email protected]) because: Error occurred in the step: Opening source mailbox.
Failed to open mailbox by GUID with error: An unknown error has occurred., error code: -1056749260
    + CategoryInfo          : InvalidOperation: (0:Int32) [Restore-Mailbox], RecipientTaskException
    + FullyQualifiedErrorId : A9E3B394,Microsoft.Exchange.Management.RecipientTasks.RestoreMailbox

Hi,
Please try the following command to check this issue:
New-MailboxRestoreRequest -SourceDatabase "RDB18" -SourceStoreMailbox "roger Hodges" -TargetMailbox otest -
TargetRootFolder “folder name” –AllowLegacyDNMismatch
In addition, when running this cmdlet, the source mailbox in the recovery database needs to be identified using one of three possible values: the
DisplayName,
MailboxGUID, or
LegacyExchangeDN values. Keep in mind that you cannot reference the source mailbox using the Exchange Alias when performing a restore. You can use
Get-MailboxStatistics cmdlet to find this information.
Best Regards.

Hi, after installing Adobe CC I tried opening Adobe Photoshop. This failed. I get the opening window where it says installing plugins searching etc, after which PS opens in full screen. Just moments after that there's a fail warning, no code number, only

Hi, after installing Adobe CC I tried opening Adobe Photoshop. This failed.
I get the opening window where it says installing plugins searching etc, after which PS opens in full screen.
Just moments after that there's a failure warning, no code number, only the warning that PS failed to open and PS will close.
I tried downloading it for a second time, but this did'nt solve the problem.
Befor the CC version I used a one year student version of Adobe CS6.
What can I do?

Regarding the Flash Player problem, disable Hardware Acceleration to circumvent driver incompatibilities.
Regarding the Flash Pro installation problems, post in the Flash forums or http://forums.adobe.com/community/download_install_setup

WARNING: Failed to validate the xml content

Hi,
We notice this error when we start the web logic admin console and also in many of Hyperion log files. There are many instances of this error and everything is pointing to different lines in this file “jps-config.xml”.
WARNING: Failed to validate the xml content. cvc-complex-type.2.4.a: Invalid content was found starting with element 'serviceInstance'. One of '{"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd":serviceInstance}' is expected.
Location: line 378 column 91 of file:/D:/Oracle/Middleware/user_projects/domains/EPMSystem/config/fmwconfig/mbeans/../jps-config.xml.
Oct 16, 2012 4:21:56 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
Any ideas?
Regards,
Ragav.
Edited by: ragavhere on Oct 17, 2012 2:04 PM

Hi,
can you please provide more details on your application?
Which version of ADF are you using and which server. Are you trying to deploy on GlassFish server?
Which IDE are you using?
Perhaps this will be useful:
https://blogs.oracle.com/shay/entry/deploying_oracle_adf_applications_to
Regards,
Dimitrios.

Restoring to an Alternate Mailbox - Couldn't connect to the source mailbox

I am trying to restore a deleted mailbox from a couple years ago and the AD User Object no longer exists. I restore from tape and create a recovery database. I use the command
"New-MailboxRestoreRequest -SourceDatabase RecoveryDB -SourceStoreMailbox 'User name' -TargetMailbox administrator -TargetRootFolder Restore -AllowLegacyDNMismatch"
and I receive error "Couldn't connect to the source mailbox".

Hi
I got result in mail box & i can sow the mail box. I successful recover existing mailbox , But can not recover to AD User Objects are not mailboxes

Excel Source - Opening a rowset for "EFT$" failed. Check that the object exists in the database.

Why oh why do I sometimes get this error when defining my Excel Source and then sometimes I do not?
Am I doing something wrong here???
The error is...
Exception from HRESULT: 0xC02020E8
Error at Data Flow Task [[Excel Source[27]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
Error at Data Flow Task [Excel Source [27}}: Opening a rowset for "EFT$" failed. Check that the object exists in the database.
I know the Worksheet "EFT" exists because I defined this previously for the same Excel spreadsheet.
Thanks for your review and am hopeful for a reply.
PSULionRP

A reply from CozyRoc must be hitting the nail on the head
sheet name contains $
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ce0fbff5-f5f1-4a4a-9c29-6adc32b0fd79/using-excel-file-as-source-in-data-flow-task-of-ssis-bi-2005-need-example-of-sheetnamecellrange?forum=sqlintegrationservices
Arthur My Blog

Couldn't connect to the source mailbox when running - New-PublicFolderMigrationRequest

Hi all,
I'm migrating my public Folders from Exchange 2010 SP3 to Exchange 2013 Cu1.
I've created the two required CSV's and and a new public folder using the holdformigration switch.
When I run New-PublicFolderMigrationRequest I recieve "Couldn't connect to the source mailbox"
any ideas what the problem could be?
Gil Gross | Project Manager & Technical Consultant | G-Net Network Solutions | www.g-net.co.il

Hello,
Please check if your steps are right as the following article.
Migrate Public Folders to Exchange 2013 From Previous Versions
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Please check if there is any error in application log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

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 "AS IS" with no warranties, and confers no rights.

WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

I have couple of VMs Server 2012 R2 RTM on Hyper-v Host running the same OS.
All machines including host and VM that is not in domain have an error in Windowsupdate.log:
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
FW and UAC are off on all. There are posts on web discussing the same error but most of them connect this to WSUS or Config Manager. And it is clear because we are touching Windowsupdate.log when troubleshooting WSUS. And because WSUS on 2012 is BUGGY this
error confuses too.
Finally, as mentioned earlier I deployed NEW server 2012 not from SYSPREP and did not place it to the domain. Updated the machine from MS update. Everything is OK beside the same error about COST :).
So now it is clear it has nothing to do with WSUS or Configuration manager. It indicates to some Network issue. But there is no clear answer. Some suggest just to ignore the error if everything is OK. But I would like to have a clean log. And it is just
interesting what could cause the problem. Is it Hyper-V stuff or Server 2012 itself. Anyway I guess I am doing right by posting a question on HV forum since here are people that should know 2012 .
Thanks.
see the log below
2013-12-16 20:32:03:610 752 b44 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-12-16 20:32:04:047 752 b44 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-12-16 20:32:04:047 752 b44 PT   + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2013-12-16 20:32:04:047 752 b44 Agent Reading cached app categories using lifetime 604800 seconds
2013-12-16 20:32:04:047 752 b44 Agent Read 1 cached app categories
2013-12-16 20:32:05:016 752 b44 PT   + SyncUpdates round trips: 2
2013-12-16 20:32:06:422 752 b44 Agent   * Found 0 updates and 14 categories in search; evaluated appl. rules of 449 out of 701 deployed entities
2013-12-16 20:32:06:422 752 b44 Agent *********
2013-12-16 20:32:06:422 752 b44 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 2]
2013-12-16 20:32:06:422 752 b44 Agent *************
2013-12-16 20:32:06:422 752 b44 IdleTmr WU operation (CSearchCall::Init ID 2, operation # 20) stopped; does use network; is not at background priority
2013-12-16 20:32:06:422 752 b44 IdleTmr Decremented PDC RefCount for Network to 0
2013-12-16 20:32:06:422 752 b44 IdleTmr Decremented idle timer priority operation counter to 1
2013-12-16 20:32:06:422 752 ba0 AU >>## RESUMED ## AU: Search for updates [CallId = {5393115A-5840-4CB4-9C66-F68034E75DF8} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2013-12-16 20:32:06:422 752 ba0 AU   # 0 updates detected
2013-12-16 20:32:06:422 752 ba0 AU #########
2013-12-16 20:32:06:422 752 ba0 AU ## END ## AU: Search for updates [CallId = {5393115A-5840-4CB4-9C66-F68034E75DF8} ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}]
2013-12-16 20:32:06:422 752 ba0 AU #############
2013-12-16 20:32:06:422 752 ba0 AU All AU searches complete.
2013-12-16 20:32:06:422 752 ba0 AU AU setting next detection timeout to 2013-12-17 22:55:28
2013-12-16 20:32:06:422 752 ba0 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2013-12-16 20:32:06:422 752 ba0 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Hi pob579,
Sorry for the late .
I want to know if your network connection indicates " unidentified network ".
If that is the case , you can try the step below :
    open the "local group policy"
    expand local computer policy -->computer configuration -->windows settings -->security settings
--> network list manager policies
    in the right pane you will see Unidentified Networks , double click it , then you can configure the
Location Type when the network connection is unidentified
    If there is domain , you need to change the same entry in "Domain Policy"
    after that please restart your computer
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

Similar Messages

Maybe you are looking for