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

Similar Messages

Exchange 2010 SP3 mailbox move Problem

Hi,
I have a big problem with DB, when I want to move some mailbox from this DB to another (same server), move FAILED,
In Event log a found:
FailureType : MapiExceptionJetErrorKeyDuplicate
FailureSide : Source
Message : Error: MapiExceptionJetErrorKeyDuplicate: Unable to query table rows. (hr=0x80004005,ec=-1605)
I Try to run: New-MailboxRepairRequest -Mailbox bberak -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview ... succesfull
I Try eseutil /g ... succesfull too
CAN YOU HELP MEEEE

Yes i try command
New-MailboxRepairRequest -Mailbox XXX -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview –DetectOnly
I found in event log ... succesfull
I have problem with all mailbox in two DB and next two DB are OK
I want to migrate all mailbox in DB to new DB in the same server
I try command :
New-MailboxExportRequest -mailbox XXX-FilePath \\srvexchange\e$\pst\olga.snajdrova.pst ... progress fail about in 10%-20%
and too command:
New-MailboxExportRequest -mailbox pz -FilePath \\hv1-dca\tmp\pzetik.pst -verbose -BadItemLimit 50000000 -AcceptLargeDataLoss ... progress fail about in 10%-20%
I found error message:
Error: MapiExceptionJetErrorKeyDuplicate: Unabl
e to query table rows. (hr=0x80004005, ec=-1605
Diagnostic context:
Lid: 45095 EMSMDB.EcDoRpcExt2 called [len
gth=100]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [e
c=0x0][length=69][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropGetContentsTable [5]
Lid: 27962 ROP: ropSetColumns [18]
Lid: 27962 ROP: ropQueryRows [21]
Lid: 17082 ROP Error: 0xFFFFF9BB
Lid: 17153
Lid: 21921 StoreEc: 0xFFFFF9BB
Lid: 31418 --- ROP Parse Done ---
Lid: 22753
Lid: 21817 ROP Failure: 0xFFFFF9BB
Lid: 28414
Lid: 32510 StoreEc: 0xFFFFF9BB
I havn't account to www.experts-exchange.com

Exchange 2007 to exchange 2013 Mailbox Move problem

Data migrated:
Migration rate:
Error:MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'. --> Active Directory property ‎'homeMDB‎' is not writeable on recipient
‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'.
Md. Ramin Hossain

[PS] C:\Windows\system32>Get-Mailbox arahaman | New-MoveRequest -TargetDatabase "Head-Office"
Active Directory property 'homeMDB' is not writeable on recipient 'domain.org/ICT_Dept/Atikur Rahaman'.
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : [Server=HYPER-SUNMAIL,RequestId=fbb3dcab-54a3-423f-81b5-9c5c397b34b4,TimeStamp=7/2/2014
5:46:07 AM] [FailureCategory=Cmdlet-RemotePermanentException] 63F06918,Microsoft.Exchange.Management.RecipientTask
s.NewMoveRequest
+ PSComputerName : hyper-sunmail.domain.org
Md. Ramin Hossain

Mailbox move from 2007 to 2010 causes performance problems on the 2007 box AFTER the move

I'm having a problem where moving a mailbox from our 2007 Exchange server to our 2010 Exchange server is causing clients that are still on the 2007 server to lock up, sometimes for up to 20 minutes. This all happens maybe 5 minutes *after* the mailbox
move has completed - during the move we see no problems.
I start seeing events 5015, 5016, and then 10025 on the 2007 box and that's when users start complaining of Outlook locking up and emails going to Outbox.
If I do this off-hours like at night or on weekends I don't see the problem, which I'm sure is because there are far fewer clients connected. We do not use cached exchange mode for a variety of reasons but mainly because our document management software
doesn't play nicely with it.
I am leaning toward the disk structure of our 2007 server. They are fast (15k SAS) but arranged in a RAID-5 which isn't ideal, but which keeps up fine in all other cases. What is happening post-move that makes for so much disk activity? I
thought maybe if I moved a good chunk of users off the 2007 box off-hours it might make daytime moves more possible, but I just tried again and it all locked up just the same.
The details:
Exchange 2007 SP3 (15k SAS disks, 2x quad core Xeon E5345, 16GB RAM)
Exchange 2010 (VMware with 4 virtual cores, 16GB RAM, storage on EqualLogic SAN)
Clients are almost exclusively Outlook 2010 on Win7, though a handful of 2007 users remain.
We have about 240 users total, about 100 of which have moved to the 2010 system.
Thanks for any suggestions. I am stumped at this point.

Hi,
Based on my experience, the issue generally happens during the migration the old server didn’t get pulled from Active Directory correctly .
http://www.squidworks.net/2013/02/solved-event-ids-5015-5016-microsoft-exchange-2010-cannot-find-a-route-to-the-source-transport-server-or-home-mta-server/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Thus, please check if the issue still can be reproduced after the migration.
If you have any question, please feel free to let me know.
Best regards,
Angela Shi
TechNet Community Support

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.

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 Not Complete - Unable to make admin interface connection to server.

Hello,
I have added a second exchange 2007 server and have moved over 20 mailboxes to the new server. I seem to have a problem that the mailbox move has not been completed properly. I'm getting errors in the event log that the search indexer cannot connect to the
admin interface. I'm also unable to login as any one of the users who I've moved to the new server.
Here's one of the errors I'm getting:
Exchange Search Indexer has temporarily disabled indexing of the Mailbox Database Third Storage Group\Mailbox Database 03 (GUID = d4f3ee4d-68b0-4d21-8a76-ee96bf298f34) due to an error (Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError:
Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
    Lid: 10648   dwParam: 0x6D9      Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x6D9      Msg: EEInfo: Status: 1753
    Lid: 9624    dwParam: 0x6D9      Msg: EEInfo: Detection location: 501
    Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string: EP-SW-EX04
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
    Lid: 24060   StoreEc: 0x80040115
    Lid: 23746
    Lid: 31938   StoreEc: 0x80040115
    Lid: 19650
    Lid: 27842   StoreEc: 0x80040115
    Lid: 20866
    Lid: 29058   StoreEc: 0x80040115
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx)
   at Microsoft.Mapi.ExRpcAdmin.Create(String server, String user, String domain, String password)
   at Microsoft.Exchange.Search.NotificationWatcher.NotificationWatcherThread()).

Hello,
I have been fighting today with the migration off my old SBS2003 server to a brand new SBS2008 server. I have been preparing this migration for a couple off weeks
now (watching videos, reading migration manual from Microsoft, searching TechNet, etc.)
After some troubles with installing the server in Migration mode if finally came to the part to move my old (legacy) mailboxes to the new SBS2008 server. At this point the drama started @#$@$#&^%%#$@
I followed the manual off Microsoft which descripted how to move these mailboxes.
Exchange displayed a error message :
MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
When I googled this error message I realized that many people encountered the same problem but no one had the right answer to this question. I have searched hours and hours to find a solution. It started to drive me crazy and to make it even more worse i discovered
that even though i completed the first step in the migration proces (update the schema to allow a SBS2008 DC to join the domain) my replication with the other DC controllers came with a schema mismatch error???? WTF is going on !!!!!!!!
Finally a brilliant college off me came with the answer that solved all my problems: To GET RID OFF THIS ERROR MESSAGE INSTALL: Messaging API and Collabration Data Objects 1.2.1 on the Exchange server.
After moving about 60 mailboxes my blood pressure dropped and became stable again.
I Have on finall question WHY Microsoft? Was this to much trouble to put this in het migration manual off 81 pages?
from-a-very-disappointed-microsoft-user
PLS: send me a reply if this solved you're problem moving the mailboxes to the new server. !

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits

Hi All,
I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated:
Limit of Exchange 2007 simultaneous mailbox moves per database
Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2007 simultaneous mailbox moves per CAS server
Limit of Exchange 2010 simultaneous mailbox moves per database
Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2010 simultaneous mailbox moves per CAS server
Any other Exchange 2007 or 2010 hard coded limits
Thanks in advance.
Michael.

My usual answer to this question is that Microsoft set these limits for a reason. Increasing them may not offer you much in the way of benefits if you end up slamming the server. I generally recommend that you leave them alone.
I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency. I was able to increase the number of
concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Mailbox move slow performance - RelinquishedWlnStall on Exchange 2013

I see a number of my mailbox moves going into a stalled state migrating from Exchange 2007 to 2013. I have paired back the number of simultaneous moves to 7 max. This has helped, but not eliminated the problem. Looking at the MoveRequestStatistics
I see that StalledDueToWriteCpu number is high. No other counter is of concern.
I see the status shows as below;
Informational: The request has been temporarily postponed due to unfavorable
server health or budget limitations. MRS will attempt to continue processing
the request again after 4/23/2015 10:39:02 AM.
Does this mean that the CPU is spiking to a high level and causing the mailbox move to stall? I have 8 cores allocated to this server 4 of the cores are averaging around 80% the other 4 about 30-40%.
Thanks

Hi BTRowdy1,
Thank you for your question.
By the information reminder, mailbox movement will be stopped because you have high hardware usage. it occurred when the server have some performance issues, for example hardware performance, you could add hardware(eg: memory) for move mailbox, we could
move few mailboxes at the simultaneous.
Are there any other applications on this server which occurred on CPU?
I suggest we move mailboxes out of production. In addition, we could monitor it for 24 hours if there is any improvement. If not, we could create a new move request for mailbox movement.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Autodiscover fails after mailbox move

Hello,
Environment: existing exchange 2010 org, with new Exchange 2013 introduced. Clients are Outlook 2013. Clients can connect to all mailbox on the 2010 Server, also can connect to new mailboxes on the 2013 Server. But if I move an existing mailbox from
the 2010 Server to the 2013 server Outlook cannot connect anymore, because autodiscover fails. Both servers use the same autodiscover settings, SCP contains the same URL.
TIA
Update: I've just installed an Outlook 2010 for testing purposes and it is working! From this point it may be rather a client side problem than a server side...

Hey there,
I actually installed 2013 using the CU5 install files. So you are right, CU5 does not matter from a first look, but it does matter overall for this issue. Keep reading.
Tangent: This appears to be unrelated but I will mention it anyways. I noticed, after the mailbox was migrated that when I am on the internal network, autodiscover fails the same way it does for you. However, when I bring the client off the corporate network
and have it connect via the public Internet, autodiscover suceeds. When testing with EXRCA autodiscover also succeeds. Please do note that external access to Exchange is handled by Microsoft's Web Application Proxy. This proxy performs "pass-through"
authentication of autodiscover so that may have something to do with it.
Back to the main issue of Outlook staying disconnected after the migration. I wasn't going anywhere with this so I opened a case with Microsoft. I was able to replicate the problem with the support tech and they were also able to replicate this in
their lab. This was the conclusion:
This is a known issue. It happens because when a mailbox is moved to 2013, the mailbox itself still has a cache entry that points the client back to the 2010 server. From what Microsoft said, this cache expires in an "undetermined" time interval
for Exchange 2013 SP1 up to CU4 and every "2 to 2.5 hours" in Exchange 2013 CU5. They could not reference a KB article with this info.
Microsoft mentioned that the cache is also cleared when recycling the IIS Application Pool that runs RPC on the 2013 CAS server which is also caused by an IISreset. However, I have not been able to verify the application pool recycle method in my tests.
From what I can see, IISreset is the only way to clear the cache. I have sent a follow-up to Microsoft asking which App Pools specifically need to be recycled to avoid having to perform a full IISreset. I will test and report back here.
In any case, here is my strategy moving forward which was blessed by the Microsoft team:
Create a migration batch for a number of users (in my case I will make it 5 to 10 users at a time)
Select to "Manually Complete the batch" in the "New Local Mailbox Move" window. This process will migrate 95% of the mailbox and then stop.
Once the migration has gone through 95% and it stops syncing, the batch shows as "synced" on the migration window. Until this point in the process, users are able to use Outlook without any interruption and the move is invisible to them.
When I am ready to finish the migration, I will select to "Complete This Migration Batch" on the ECP Migration screen. At this time, users that have Outlook open will receive a prompt to
restart it. When Outlook re-opens it will show as "Disconnected" until the next step is performed.
Once the batch shows as "completed" I will perform an IISreset on the 2013 CAS server (or recycle the appropriate app pools once Microsoft provides them to me.) At this time, Outlook will show as "Connected to Microsoft Exchange" and
users will receive a second prompt to restart Outlook. After the second restart you'll be good to go!
I will try to time my migration so they complete after hours, when most people are less likely to have Outlook open. Don't forget, that the cache entry that causes all these issues is cleared after about 2 to 2.5 hours if you are on 2013 CU5. In any
case, I think it's better if you have control over when the migration finishes by opting to complete it manually.
Hope this helps.
Fable
EDIT: Microsoft has confirmed that recycling the following Application Pools makes Outlook connect to Exchange 2013:
Exchange 2013 CAS Server:
MSExchangeAutodiscoverAppPool
MSExchangeRpcProxyFrontEndAppPool
Exchange 2013 Mailbox Server:
MSExchangeAutodiscoverAppPool
MSExchangeRpcProxyAppPool
If you decide to not do an iisreset and opt for recycling the App Pools instead, be advised that after the AppPools are recycled, Outlook connects to Exchange and asks to be restarted. If you close Outlook and immediately open it again, you will be prompted
with a username and password pop-up (At least I was in all my tests of this method.) This issue is resolved if, after you close Outlook, wait 5 to 10 minutes before you re-open it. You will not be prompted for a user/pass at this point.

Remote 2010 - 2010 Cross-forest mailbox move timeout

I'm having a problem moving large mailboxes cross-forest. Smaller mailboxes with fewer items move successfully. I've tried the suggestions in this article
http://technet.microsoft.com/en-us/library/dd638094.aspx about increasing DataImportTimeout in the EWS web.config and restarting IIS on both sides, just in case.
I also found a suspicious timeout in MsexchangeMailboxReplication.exe.config that was 00:00:50 (exactly the timeout it's complaining about in the error below), but changing it to 10 minutes didn't seem to help
<customBinding>
<binding name="MrsProxyClientBinding"
receiveTimeout="00:00:50"
sendTimeout="00:00:50">
<reliableSession ordered="true" />
Below is the full text of the error I'm geting in the move request log. After this error occurs, the entire mailbox move process begins again. The strange thing is I've gotten successful moves of mailboxes up to 10Gb before, and this same error happens on a
mailbox that's 4gb.
Can someone help troubleshoot this error? It's driving me crazy.
11/17/2011 10:00:00 PM [Server2] Initial seeding completed, 172342 items copied, total size 10.55 GB (11,327,875,162 bytes).
11/17/2011 10:00:00 PM [Server2] Final sync has started.
11/17/2011 10:02:13 PM [Server2] Transient error TimeoutErrorTransientException has occurred. The system will retry (1/60).
Error details: The call to 'https://server1.domain.local/EWS/mrsproxy.svc server1.domain.local (14.1.325.0 caps:01FFFF)' timed out. Error details: The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The request operation did not complete within the allotted timeout of 00:00:50. The time allotted to this operation may have been a portion of a longer timeout. --> The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The request operation did not complete within the allotted timeout of 00:00:50. The time allotted to this operation may have been a portion of a longer timeout.
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallService(GenericCallDelegate del, String epAddress, VersionInformation serverVersion)
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationProxyClient.CallServiceWithTimeout(TimeSpan timeout, GenericCallDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationProxyClient.Microsoft.Exchange.MailboxReplicationService.IMailboxReplicationProxyService.IFolder_GetRules(Int64 folderHandle, Int32[] extraProps)
at Microsoft.Exchange.MailboxReplicationService.RemoteFolder.Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules(PropTag[] extraProps)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.<>c__DisplayClass1c.<Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules>b__1b()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules(PropTag[] extraProps)
at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.ReadRules(IFolder folder, PropTag[] extraPtags)
at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.EnsureDataLoaded(IFolder folder, FolderRecDataFlags dataToLoad, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass4`1.<LoadFolders>b__0()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.LoadFolders[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.GetFolderMap[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.GetSourceFolderMap(GetFolderMapFlags flags, FolderRecDataFlags dataToLoad, GenericCallDelegate abortDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyAllFolders()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<FinalSync>b__4b(MailboxMover mbxCtx)
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: IFolder.GetRules
OperationSide: Source
Primary (34bdddb1-2e13-45ab-a575-3f6de414c398)
PropTags: [ReportTime; 1627389955; 1627455491]
Folder: 'MAILFOLDER', entryId [len=46, data=0000000083AB09B7111C3B4682D4140582FD21F30100E929EE996D69BF409B946039972CD120000000F4001F0000], parentId [len=46, data=0000000083AB09B7111C3B4682D4140582FD21F30100D60B955AB375EF4DB7D38206B8CDAA36000000E3000C0000]

Hi,
Please try the steps below to chang the following file:
C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.Config file contents:
--Change the following on the source side on the CAS server in the file MSExchangeMailboxReplication.exe.config
• Changed the values from 1048576 to 3048576 :-
<binding name="MrsProxyClientBinding"
receiveTimeout="00:00:50"
sendTimeout="00:00:50">
<reliableSession ordered="true" />
<textMessageEncoding>
<readerQuotas maxArrayLength="3048576"
maxStringContentLength="3048576" />
</textMessageEncoding>
<httpsTransport authenticationScheme="Negotiate"
maxReceivedMessageSize="3048576"
allowCookies="true" />
• Modify the
file MSExchangeMailboxReplication.exe.config on the target CAS server as follows:-
binding name="MrsProxyClientBinding"
receiveTimeout="00:00:50"
sendTimeout="00:00:50">
<reliableSession ordered="true" />
<textMessageEncoding>
<readerQuotas maxArrayLength="3048576"
maxStringContentLength="3048576" />
</textMessageEncoding>
<httpsTransport authenticationScheme="Negotiate"
maxReceivedMessageSize="3048576"
allowCookies="true" />
Note: make a backup before you change the value.
Restart IIS and then try again to see if this works. Hope it is helpful.
Best Regards Fiona Liao E: [email protected]

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

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.

Mailbox Move Problem

Similar Messages

Maybe you are looking for