Mailbox move stuck

Hello,
I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?
Thanks.
Memento Mori

Have increased diagnostic logging for mailbox move:
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Mailbox Move" -level high
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Service
" -level high
Getting the following exception:
2014-01-05T03:07:29.678Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5739226, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:34.732Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:35.372Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5744619, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:40.427Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:41.066Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.589772, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:46.136Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Error,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","MigrationJobItem.SetTransientError: job a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing, at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String
commandString, Exception ex) at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand
command, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't find a move request that corresponds to the specified identity
'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData
optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession, IConfigDataProvider
globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate
errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]",Set TransientError: Syncing:1/5/2014 2:41:56 AM:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.
--> Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.: count 10 original time 01/05/2014 02:41:56
2014-01-05T03:07:46.760Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","NotifyOfTransientException: at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)
at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1
ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)|transient error occurred for job items:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException:
Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID,
OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession,
IConfigDataProvider globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate
logHandler, ErrorLoggerDelegate errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
Memento Mori

Similar Messages

Mailbox Move stuck on StatusDetail Relinquished

Hi,
I am trying to do mailbox moves from Exchange 2010 SP3 to Exchange 2013 CU5. This morning they were working great for a few users with no issues. Mailboxes were about 1GB.
Now when I move a mailbox it goes into a StatusDetail of Relinguished and does not proceed past 0%
What does this status mean? Should i restart the Mailbox Replication Service? I was not sure about restarting the service as I have live users and dont want to disconnect them from their mailboxes..
Please help..

Hi,
Per my known, online mailbox moves are supported between Exchange 2010 databases and between Exchange 2007 SP3 and Exchange 2010 databases.
If you move mailbox in Exchange 2013, users can't access their mailboxes during mailbox move. I recommend you migrate mailbox off business hours.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Mailbox move during DAG failover is stuck

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you
At some point they should resume.
What does get-moverequeststatistics show for the status?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

User Move stuck.....

I have a user that I moved from a post office I am consolidating. It is stuck in the process right now, currently at the retry mailbox item retrieval.
I did, before the move, a standard content/structure gwcheck before, then did one with deldupfolder, then back to standard (if duplicate folders were found) until none were found and not issues....then a gwcheck with attclip..
When requesting pending items, it lists over a 100 items, with the first being a internal search folder, listed as To-Do.
I am sure there are more than a 100.
I have tried to simply skip the next item in the list, once, to see if it was a single item holding up.
I have tried retrying the last step of the move.
I have tried restarting the entire mailbox move.
Now, my log files are showing this for MANY MANY items, when I do mailbox retry....
02:24:54 578D (TRACKMOVE) Could not '_NgwrepFixItem' (53511 0x0000d107): paynej (egw) (paynej)
Only thing that I have found as a possible solution, would be to cancel the move...by moving the account BACK to the original post office, and then attempting again after running some additional gwchecks.
Thanks for any assistance you may be able to offer.

I did a rebuild on the involved domains and postoffices
I recreated wpcsin wpcsout mslocal
On the netware server I put the in nodca in the startupfile for the
postoffice..
And now the user moves works..
"gregamy" <[email protected]> skrev i meddelandet
news:[email protected]..
>
> If you did not do checks, are *any *items coming over at all? Or are
> they all just stuck at the initial phases?
>
> If you did not do checks, and if the process started and a lot of items
> came over, and you don't do normally-scheduled checks, then it could
> just be you have some bad, stuck items. Those can be cleared easily.
>
>
> --
> Greg Amy
> GroupWise Admin
> Hartford (CT) Hospital
> ------------------------------------------------------------------------
> gregamy's Profile: http://forums.novell.com/member.php?userid=12509
> View this thread: http://forums.novell.com/showthread.php?t=438046
>

Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013

G'Day All,
Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007. I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
etc, but non of them is clear of how does it work having Exchange 2007 source.
Thanks in advance.

Hi Atonal,
Could you please take a look at this technet blog that has been well elaborated about your concern :
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013.

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
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

Multiple eventlog errors after mailbox-move to Exchange SP1

After a mailbox move completes on a Exchange 2013 SP1 server, multiple errors are logged in the eventlog. I opened a ticket with MS Support and they confirm this is a bug in SP1, but the moves itself aren't affected. They state the errors can be ignored.
About 10 error per move are being logged.
These are the errors occurring after completion of a mailbox move:
Event 1003:
An asynchronous Microsoft Exchange Server Information Store task has not handled an Exception gracefully. Exception text is (Microsoft.Exchange.Server.Storage.Common.StoreException: ErrorCode: NotSupported, LID: 43296 - Invalid counter range allocation at
this time.
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)).
Event 1050:
Global counter allocation in mailbox 3add23e8-7a32-4fb5-bc32-f5b1eae7f98c on database 0afbb5dc-b967-4ebd-acb0-15f85b8bad53 by source MailboxTask during operation 28 on call stack at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context
context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64&
globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, MailboxTaskQueue mailboxTaskQueue, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.Common.Task`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.SingleExecutionTask`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.Task`1.<Worker>b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)
at Microsoft.Exchange.Server.Storage.Common.WatsonOnUnhandledException.Guard(IExecutionDiagnostics executionDiagnostics, TryDelegate body)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
is temporary not allowed.

Here's the technical descpription from MS support:
Description of problem: “During the mailbox move finalization stage the Store move is finalized followed by MRS move. In this state MRS executes MRS specific functionality. The state might take
a pretty long time in some cases. During this state the destination mailbox cannot be changed. The defensive code on the global counters depicts that the task with task ID 28: TaskTypeId.PropertyPromotionBootstrap is trying to allocate new global counter values
as seen in the event below.”
This is not a critical issue, and the production team also suggest safely ignore this warning, also they are now making progress to fix this issue, hoping to release the solution in the next CU or SP.
Frank.

Exchange 2013 shell mailbox move requests showing up on 2010 hub server

We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
server roles have changed.
Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
If the local move request is done in the EAC the batch(es) show up just fine.
The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
any ideas?

Are you running ex2013SP1 CU6? Can you try to update n check?
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Messages sent from secondary mailboxes getting stuck in Outbox.

I have two users who recently began having a problem with messages sent from secondary mailboxes getting stuck in their Outbox.
The details:
We're using Exchange Server 2010 version 14.03.0224.002
Windows 7 Professional Service Pack 1
Office 2010 version 14.0.7140.5002 (32-bit)
The user in question whom I will call Jane has full rights and send as rights to the department's mailbox (which I will call "Common"), however, the Outlook profile on her computer is setup so that Common is the default mailbox
and Jane is a secondary mailbox.
The problem is that in the last few weeks messages send from Jane get stuck in the Outbox. We have recreated Jane's Outlook profile on her computer which resolves the problem, but only for a day or two before it begins to happen again.
Additional info: Jane logs into her computer and her email as herself. As stated above she has full rights and send as rights to Common. Common also has full rights and send as rights to Jane's email.
We have used this setup successfully for many years for several of our users. The problem started with one user a few weeks ago and now a second user who accesses a different Common mailbox is having the same problem. Both systems have been
thoroughly checked for viruses and malware, etc.
Anybody got any ideas?

The same thing happens to me. Really irritating. However, even after rebooting, the mail is sometimes stuck in the outbox. Anybody have a solution?

Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013

Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman

Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman
Does simply recycling the ActiveSync app pool speed things up?
Also, I would recommend installing CU6 instead of SP1.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

I have a movie stuck in the Itunes que, how do I remove it?

I have a movie stuck in the Itunes que, how do I remove it. Repeated requests to continue with the download fail.

Try a reset. Press and hold both the home and power buttons 10-15 seconds till the Apple logo appears. Release both buttons. Wait 15-20 seconds till your iPhone starts on it's own.

Should cancelled mailbox moves result in any moved mail data removed from target server?

I was moving mailboxes from 1 DB to another. 3 out of 120 were left running for 12 hours; they were the biggest ones and it was very slow to process the items. There were also reports of slowness on the server so I had no choice but to cancel the moves.
My question is should cancelled mailbox moves result in any moved mail data being removed from the target database? It doesn't appear that my disk as increased in space again so I'm wondering if it's there as whitespace maybe? There is an event logged to say
the mailbox has been deleted from the target.
Would appreciate if someone can clear this up and possibly explain exactly what occurs during this type of scenario.
Thanks.

Hi,
Thank you for your kindly remind.
In Exchange 2000, 2003 and 2007 mailboxes become unavailable during movement, when a mailbox move takes place, the mailbox isn't actually moved, it's just copied to the destination location. Once that copy has finished, AD is updated to point to the new location
and the old mailbox is deleted from the source EDB file.
The most different between Exchange 2010 and legacy version in move mailbox is that allows end-users to be online in their email accounts. On completing the move users just needs to reopen their Outlook clients.
Mailbox Move Requests are a new feature set of Exchange 2010 and requires running a series of Cmdlets to perform asynchronous online mailbox moves with the help of a service agent called Mailbox Replication Service (MRS). MRS is available on all Exchange 2010
Client Access Servers.
Best Regards,
Allen Wang

Mailbox Move ForceOffline Parameter

Hell all,
scenario: Exchange 2013 RTM CU3, Exchange 2013 SP1 DAG
I'm trying to find a way to speed up Mailbox moves (local - from the RTM to the DAG environment) and I've pretty much exhausted all options I am aware of (MRS parameters, TCP Chimney, RSS etc.).
The one thing I haven't tried is the ForceOffline parameter, but unfortunately this switch appears to be very poorly documented.
Does anyone have any experience doing mailbox moves in "offline mode"? Does it speed up the transfer? Are the mailboxes automatically put back in "online mode" after the move?
Thx in advance!
M.

Hi,
ForceOffline forces a mailbox move to be performed in offline mode, meaning the user will have no access to email during the mailbox move. There is no official article explaining that it speeds up the migration using ForceOffline parameter. Your understanding
will be appreciated.
What's more, after finishing the migration, users will have access to email. In other words, mailboxes put back in "online mode".
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Mailbox move requests remain in Queued status

My server is part of a two member DAG. DAG shows to be healthy. I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
Server is Exchange 2010 SP 3

Hi,
Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
check.
Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
Best Regards.

Mailbox Move Problem

Hi,
I need mailbox move between 2 exchange 2013 mailbox server. But we receive an error message and failed job. Status datail StalledDueToWriteUnknown. how to correct this problem ? thank you.
New-MoveRequest -Identity "user1" -TargetDatabase "Mailbox DataBase05" -BadItemLimit 300
[PS] C:\Windows\system32>Get-MoveRequestStatistics -Identity user1
DisplayName               StatusDetail              TotalMailboxSize
TotalArchiveSize         PercentComplete
user1         StalledDueToWriteUnknown 1.704 GB (1,829,622,48...
20

Hi,
Does this issue only occur when migrating the user1?
In order to narrow down whether it is an issue with the user mailbox, please create a test mailbox and try to move it for a test.
If this issue occur to all the users, I suggest we first temporarily disable the “health check” service, raise the baditem limitation to 999.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Mailbox move stuck

Similar Messages

Maybe you are looking for