Mailbox move request missing

Dear Forum Members,
We have two Exchange 2013 servers, with two databases in a DAG configuration. Now one of them appears to be almost full, so we decided to move one 4Gb mailbox to the other database. This should be kind of routine job, but after I create the migration task,
it completes without any error, but the total number of migrated mailboxes are zero! It looks like as if I never selected that mailbox for migration, furthermore, it looks like an empty migration job :O
Has already anyone seen this behaviour? I can't really find information about this anywhere.
Thank you really for your help,
Best Regards,
Chrsitian

Hi Chrsitian,
How about the result if moving the mailbox via EMS command?
New-MoveRequest -Identity "UserName" -TargetDatabase "DBName" -BadItemLimit 100 -AcceptLargeDataLoss
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Similar Messages

New mailbox move request Exchange 2010 : queued

I have deployed new Exchange 2010 server in Exchange 2003 Organization. It is simple setup one Exchange 2003 and New Exchange 2010.
I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes and result is the same.
Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
I run test MSR replication and is ok.
I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

Hi,
Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
clear the previous move request and then move the mailbox.
If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

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

How to remove failed mailbox move request

Hi all,
Exchange 2010 SP1
i canceled or move failed on several mailboxes. How can I move these mailboxes again since
they still have move request checked?
Thank you.

Hi JaneHHH,
Here are some examples:
To just remove the failed moverequests in EMS, RUN Get-Moverequest -MoveStatus Failed | remove-moverequest
Move all moverequests in EMS, RUN get-moverequest | remove-moverequest
You can of course also remove them in EMC, but a simple right-click the once you want to move in EMC|Recipient Configuration|Move Requests and choose "Clear Move Requests"
:Martina
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.

MailBox Move Request Statistics

Hello,
I am performing some mailbox moves on one of our systems here in testing for a migration. I believe I need to increase the number of CPUs on the virtual machine I am using but wanted to ask to be sure. Currently we have one of the return values of Get-MoveRequestStatistics
for a user showing as:
TotalStalledDueToWriteCpu : 00:22:36
Does this mean the move is waiting on CPU?
Thank you,
Brent

Hello Brent,
Yes, this does potentially indicate the CPU resource issue on your VM.
Also couple of points to note from virtualization best practice/recommendation prospective...
Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in
the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1, although we recommend a ratio of 1:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the
host system. On a system with this configuration, don't allocate more than a total of 16 virtual processors to all guest virtual machines combined.
When calculating the total number of virtual processors required by the host machine, you must also account for both I/O and operating system requirements. In most cases, the equivalent number of virtual processors required in the host operating system for
a system hosting Exchange virtual machines is 2. This value should be used as a baseline for the host operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the host operating
system indicates you're consuming more processor utilization than the equivalent of 2 processors, you should reduce the count of virtual processors assigned to guest virtual machines accordingly and verify that the overall virtual processor-to-physical core
ratio is no greater than 2:1.
Refer:
Exchange 2013 Virtualization
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

Hello,
I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
Exchange 2010 has 2 databases:
1. Database with users mailboxes;    Journaling YES: Journal account.
2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
Exchange 2013 has 1 database:
1. Database with moved users mailboxes;    Journaling YES: Journal account.
I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
I'd like:
* to understand technically what happened,
* to avoid unnecessary growth of Journal Database.
I'd like not to switch off journaling for all users during mailbox move.
best regards Janusz Such

Hello Winnie,
your understanding is not correct:
I move mailboxes from first DATABASE which is journaled;
second database is dedicated solely for Journal user's mailbox and is not touched now.
Thank you for PS commands; I'll use them...
best regards Janusz Such
Hi Janusz,
Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
Journal rule instead of database journal as a workaround.
Regards,
Winnie Liang
TechNet Community Support

Mailbox move request error

Hi
I moved 95 mailboxes from 2003 to 2010 without errors, but the last one are stopped with:
Failed
Error:
Active Directory operation failed on sth-ad01.xxxxx.br. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E48, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
Exchange Management Shell command attempted:
'xxxxx.br/MyBusiness/Users/useralias' | New-MoveRequest -TargetDatabase 'Mailbox Database 1591777605'
If I go to 2003 DC, on the User's Exchange Advanced tab, Mailbox Rights,
Exchange Servers have a DENY on Full Mailbox Access, but it's not possible to remove that (inherit).
Any Ideas?
This topic first appeared in the Spiceworks Community

Hi
I moved 95 mailboxes from 2003 to 2010 without errors, but the last one are stopped with:
Failed
Error:
Active Directory operation failed on sth-ad01.xxxxx.br. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E48, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
Exchange Management Shell command attempted:
'xxxxx.br/MyBusiness/Users/useralias' | New-MoveRequest -TargetDatabase 'Mailbox Database 1591777605'
If I go to 2003 DC, on the User's Exchange Advanced tab, Mailbox Rights,
Exchange Servers have a DENY on Full Mailbox Access, but it's not possible to remove that (inherit).
Any Ideas?
This topic first appeared in the Spiceworks Community

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

Exchange crash during move request, new DB in dirty shutdown

I had a hardware failure (storage controller in VM environment) during a mailbox move request to a new DB. After fixing that and rebooting, the old database came up and is fine which is great. The new database is in a dirty shutdown state right now with a few completed but most are still queued or in progress. If I try to remove the request on the completed mailboxes it has a message along the lines of, couldn't connect to mailbox database, it could be dismounted. Do you want to orphan the move request for user XYZ?
Will this cause any problems? I would like to remove the move requests and proceed recovery and repair of the dismounted DB. Thoughts?
Thanks,
Josh
This topic first appeared in the Spiceworks Community

Hi,
Thank you for sharing the resolution.
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. Thanks Gen Lin-MSFT

New Local Move Request Script for Exchange 2010 mailboxes

Hi I would like to have a script that can enable me automatically move mailboxes of certain domains to a new mailbox database. E.g. new local move request to move only 20 mailboxes in mailboxdatabase01 with the domain name: mymove.com, moving
it to mailboxdatabase05. Also, I want to be able to adjust the number of mailboxes to move. Thanks in advance.

Wrap this, or something similar, into a script that filters out the users with that domain in a particular DB.
http://technet.microsoft.com/en-us/library/dd876878(v=exchg.141).aspx
And some filtering examples are in here:
http://blogs.technet.com/b/rmilne/archive/2014/03/24/powershell-filtering-examples.aspx
I doubt there is a sample script out there that does exactly what you want, so you'll have to do some coding.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

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

Mailbox move failure - EX2010 to 2013 - IExchangeFastTransferEx.SetProps failed ‎(hr=0x8004010f, ec=0)‎

Hi,
I've been having problems moving my mailbox from Exchange 2010 to 2013 as part of an upgrade I'm doing. I've moved a couple of other mailboxes without issues, and the account can move between different DAG groups on Exchange 2010.
The process does the initial move quite quickly, and then stalls when it gets to 95% going into a loop of retries for up to 5 hours before failing.
The essential error information is as follows,
Error: MigrationPermanentException: Error: MapiExceptionNotFound: IExchangeFastTransferEx.SetProps failed ‎(hr=0x8004010f, ec=0)‎
Request Username (40db3a16-4427-4690-bf7e-15db185c8e03) failed.
Error code: -2147221233
MapiExceptionNotFound: IExchangeFastTransferEx.SetProps failed (hr=0x8004010f, ec=0)
Context:
Operation: IMapiFxProxy.ProcessRequest
OpCode: SetProps
DataLength: 261
Operation: IMapiFxProxy.ProcessRequest
Operation: IMapiFxProxy.ProcessRequest
OperationSide: Target
Primary (40db3a16-4427-4690-bf7e-15db185c8e03)
OpCode: SetProps
DataLength: 261
Operation: ISourceMailbox.CopyTo
Operation: ISourceMailbox.CopyTo
OperationSide: Source
Primary (40db3a16-4427-4690-bf7e-15db185c8e03)
PropTags: [count:2, 0x360e000d(ContainerHierarchy); 0x360f000d(ContainerContents)]
I've tried a lot of trouble shooting and haven't found anyone with a similar problem via google etc, things I've done.
Tried different EX2013 MB stores
Created a 2nd exchange org admin account
Tried a domain admin account
Removed my Exchange archive
Cleaned up various folders\views\rules
reset the AD account ACL's
Checked out the mailbox via MFCMapi and purged several items.
Moved the mailbox via PS with the ignoresignature setting
I'd rather not export the mailbox to PST in case this happens to multiple accounts, it will also mess up recurring meetings etc as well.
Any thoughts?
Thanks
Jeff

Hi,
This is the output of the logfile, the formatting is not great but it essentially does the first part of the move, then repeats the final sync for about 4-5 hours until it gives up, I've removed most of it as it is just the same. the errors at the start
of the message are what appears in the event log on the MRS target server.
Unfortunately I can't see anything obvious in it.
I'd still like to persevere a little bit more but I'm rapidly running out of things to try. I don't want to recreate the mailbox if possible as there are meetings that were created by other people which would need to be recreated and I'm worried the
same thing happens elsewhere with someone who can't have the meetings recreated so easily.
I've only moved about 4 mailboxes so far, the others worked fine but I've got about ~2500 more to do, I was moving mine to test\move forward.
BTW, thanks for the tips Ilantz, just in case!
Thanks
Jeff
27/12/2013
10:28:42 [EX2013MBX] '' created move request.
27/12/2013 10:28:46 [EX2013MBX] The Microsoft Exchange Mailbox Replication service 'targetserver' (15.0.775.35 caps:3F) is examining the request.
27/12/2013 10:28:46 [EX2013MBX] Connected to target mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'EX2013MBStoreTest', Mailbox server 'targetserver' Version 15.0 (Build 775.0).
27/12/2013 10:28:46 [EX2013MBX] Connected to source mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'DAGStore02', Mailbox server 'sourceserver' Version 14.3 (Build 158.0).
27/12/2013 10:28:46 [EX2013MBX] Request processing started.
27/12/2013 10:28:46 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)
27/12/2013 10:28:46 [EX2013MBX] Mailbox signature will not be preserved for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'. Outlook clients will need to restart to access the moved mailbox.
27/12/2013 10:28:47 [EX2013MBX] Stage: CreatingFolderHierarchy. Percent complete: 10.
27/12/2013 10:28:47 [EX2013MBX] Initializing folder hierarchy from mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 127 folders total.
27/12/2013 10:28:47 [EX2013MBX] Folder creation progress: 0 folders created in mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'.
27/12/2013 10:28:56 [EX2013MBX] Folder hierarchy initialized for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 127 folders created.
27/12/2013 10:28:56 [EX2013MBX] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
27/12/2013 10:28:56 [EX2013MBX] Initial sync checkpoint progress: 0/127 folders processed. Currently processing mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'.
27/12/2013 10:28:59 [EX2013MBX] Initial sync checkpoint completed: 119 folders processed.
27/12/2013 10:28:59 [EX2013MBX] Stage: LoadingMessages. Percent complete: 20.
27/12/2013 10:29:04 [EX2013MBX] Messages have been enumerated successfully. 2926 items loaded. Total size: 74.57 MB (78,195,169 bytes).
27/12/2013 10:29:04 [EX2013MBX] Stage: CopyingMessages. Percent complete: 25.
27/12/2013 10:29:04 [EX2013MBX] Copy progress: 0/2926 messages, 0 B (0 bytes)/74.57 MB (78,195,169 bytes), 41/127 folders completed.
27/12/2013 10:32:46 [EX2013MBX] Copying messages is finished. Copying rules and security descriptors.
27/12/2013 10:32:47 [EX2013MBX] A corrupted item was encountered: Folder property ""
27/12/2013 10:32:56 [EX2013MBX] Initial seeding completed, 2926 items copied, total size 74.57 MB (78,195,169 bytes).
27/12/2013 10:32:56 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:32:56 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 0 deleted folders.
27/12/2013 10:32:56 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 0 changed folders, 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:32:57 [EX2013MBX] Final sync has started.
27/12/2013 10:32:57 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 1 deleted folders.
27/12/2013 10:32:57 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 1 changed folders, 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)
27/12/2013 10:32:57 [EX2013MBX] Stage: FinalIncrementalSync. Percent complete: 95.
27/12/2013 10:32:57 [EX2013MBX] Transient error MapiExceptionNotFound has occurred. The system will retry (1/10).
27/12/2013 10:33:31 [EX2013MBX] The Microsoft Exchange Mailbox Replication service 'targetserver' (15.0.775.35 caps:3F) is examining the request.
27/12/2013 10:33:31 [EX2013MBX] Connected to target mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'EX2013MBStoreTest', Mailbox server 'targetserver' Version 15.0 (Build 775.0).
27/12/2013 10:33:31 [EX2013MBX] Connected to source mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'DAGStore02', Mailbox server 'sourceserver' Version 14.3 (Build 158.0).
27/12/2013 10:33:31 [EX2013MBX] Request processing continued, stage IncrementalSync.
27/12/2013 10:33:32 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 0 deleted folders.
27/12/2013 10:33:32 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 0 changed folders, 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:33:32 [EX2013MBX] Final sync has started.
27/12/2013 10:33:32 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 1 deleted folders.
27/12/2013 10:33:32 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 1 changed folders, 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)

Problem clearing a move request

Hi,
I've got a simple Exchange 2010 setup running along a 2007 insallations.
I have 2 DC's both running 2008 but not R2.
My issue is, I have moved a couple of users using the local move request. One of them I delete the move request as soon as it had been completed (the icon changed back to the one without the little green arrow), but the other gives me an error message of
Microsoft Exchange Error
Action 'Clear Move Request' could not be performed on object 'Enid Dalton'.
A User
Failed
Error:
Couldn't find a move request that corresponds to the specified identity 'home.local/Top Level/2nd Level A/A User.
The user exists and has not been moved within the OU structure.
In a real world situation, this would then stop me from moving the user again. Obviously this doesn't happen every day, but a user could move offices for a short period of time and wish to move the mailbox to a local server.
Any idea's ?
Thanks in advance
Phil
Remember : Experience is something you don't get until just after you need it.

When migrating from 2007 or 2010 to 2013 Exchange, if the account was deleted before the move request was cleared, or it was put into a different OU, you can force clear the move request as follows:
Get-MailboxDatabase|%{Get-MoveRequestStatistics-MoveRequestQueue
$_.Name}
|SortPercentComplete|MailboxIdentity,ExchangeGuid,RequestQueue,StatusDetail
Remove-MoveRequest-MailboxGuid
$MbxGuid-MoveRequestQueue
$MoveReQ-Verbose

Mailbox move request missing

Similar Messages

Maybe you are looking for