Mailbox move Exchange 2003 to Exchange 2010
-
Sunday, March 18, 2012 1:48 AM
Hello,
We have Exchange 2003 running on Windows 2003 Servers. We are in the process of transitioning to Exchange 2010 and we are trying to move mailboxes to Exchange 2010 from Exchange 2010 management console. These are local moves as the servers are in same forest.
When I try to move a mailbox it just sits there, the log says it is connected to source mailbox store and target mailbox store. But nothing happens. Please advice.
TIA
Tom
All Replies
-
Sunday, March 18, 2012 2:05 AM
WHat is the status or the mailbox you;re moving?
As a test create a test mailbox on 2003 and move that.
Sukh
-
Sunday, March 18, 2012 2:07 AM
Ststus says moving.
I created a brand new mailbox in 2003, in a new OU and tried and the result is same.
Thanks
Tom
-
Sunday, March 18, 2012 2:14 AM
-
Tuesday, March 20, 2012 9:05 AM
-
Tuesday, March 20, 2012 1:13 PM
It just says failed.
[PS] C:\Windows\system32>Get-MoveRequestStatistics -Identity eadmin
DisplayName Status TotalMailboxSize TotalArchiveSize PercentComplete
----------- ------ ---------------- ---------------- ---------------
Example Administrator ... Failed 720.4 KB (737,654 bytes) 0Thanks
Tom
-
Tuesday, March 20, 2012 2:13 PM
Try some suggestions here, likely a permissions issue. Either inheritance is missing on some DBs or some Exchange servers are not in the correct Exchange groups....
Hey guys, i was working on an Exchange 2003 to 2010 migration and came up with the same error... I went to Exchange System Management on the Exchange 2003 Server and right clicked on the First Storage Group\Mailbox Store; Security Tab; then added a Computer Object(EXG01) and gave it Full Control... I was then able to use Exchange Server 2010 to utilize the "New Local Move Request" to the Exchange 2010 Database... Please reply and let me know if this helped you!
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
-
Tuesday, March 20, 2012 4:54 PM
View and post the log for the move in the EMC. Goto Recipient Configuration\Move Request, opening up the move request the mailbox, and then click the Log tab.
See this TechNet article for more help: Troubleshooting Mailbox Moves
Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP http://info.izzy.org | http://jasonsherry.org | Twitter: @JasonSherry
-
Wednesday, March 21, 2012 4:45 PM
Hello,
Please find the output from log tab:
3/21/2012 12:24:04 PM [Exchange2010MBServer4] 'mb.com/MB Users/Administrator' created move request.
3/21/2012 12:24:07 PM [Exchange2010CASServer1] The Microsoft Exchange Mailbox Replication service 'Exchange2010CASServer1.mb.com' (14.2.283.3 caps:07) is examining the request.
3/21/2012 12:24:07 PM [Exchange2010CASServer1] Connected to target mailbox 'Primary (49be4554-6ad6-41e9-86ed-45ff05e069bb)', database 'RSource', Mailbox server 'Exchange2010MBServer4.mb.com' Version 14.2 (Build 247.0).
3/21/2012 12:24:07 PM [Exchange2010CASServer1] Connected to source mailbox 'Primary (49be4554-6ad6-41e9-86ed-45ff05e069bb)', database 'Exchange2003MailBoxServer\Third Storage Group\Third1 Mailbox Store', Mailbox server 'Exchange2003MailBoxServer.mb.com' Version 6.0 (Build 7654.0)Tom
-
Wednesday, March 21, 2012 7:54 PM
Please find the error from mailbox move:
Database on 2003 is mounted and is accessible
Error:
MapiExceptionJetErrorVersionStoreOutOfMemory: Unable to open message store. (hr=0x80004005, ec=-1069)
Diagnostic context:
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=127]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropLogon [254]
Lid: 17082 ROP Error: 0xFFFFFBD3
Lid: 26937
Lid: 21921 StoreEc: 0xFFFFFBD3
Lid: 31418 --- ROP Parse Done ---
Lid: 22753
Lid: 21817 ROP Failure: 0xFFFFFBD3
Lid: 26297
Lid: 16585 StoreEc: 0xFFFFFBD3
Lid: 32441
Lid: 1706 StoreEc: 0xFFFFFBD3
Lid: 24761
Lid: 20665 StoreEc: 0xFFFFFBD3
Lid: 25785
Lid: 29881 StoreEc: 0xFFFFFBD3Tom
-
Thursday, March 22, 2012 2:51 AM
Hi,
We may have version store issue at Exchange 2003 side. The Version Store keeps an in-memory list of modifications made to the database.
When maximum Version Store size has been reached, write operations to the database will start failing with -1069 (JET_errVersionStoreOutOfMemory) because there's no more Version Store space in which to record the operation.
Please try to check the event log to see if you have event 602, please post the detail event information here.
Also you can follow the article below to troubleshoot the issue.
Troubleshooting Version Store issues - JET_errVersionStoreOutOfMemory
http://blogs.technet.com/b/exchange/archive/2006/04/19/425722.aspx
Xiu Zhang
TechNet Community Support
-
Thursday, March 22, 2012 6:24 PMIf it is an actual version store memory exhaustion try rebooting the 2003 server.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
-
Friday, March 23, 2012 5:29 PM
Hi TSAM,
kindly feedback especially on version store (JET_errVersionStoreOutOfMemory) troubleshooting (by Xiu Zhang) and rebooting by James Chong
Many thanx
If this post has been useful please click the green arrow to the left or click "Propose as answer"
-
Monday, March 26, 2012 5:50 AM
-
Tuesday, March 27, 2012 1:23 PM
Still troubleshooting with MS and no answers so far.
Thanks
Tom
-
Monday, April 02, 2012 5:59 AM
-
Wednesday, April 04, 2012 6:51 PM
Nothing yet, still with MS.
I personally think it as a resource issue and stopping some service like MS search etc. helped out.
Tom
- Marked As Answer by TSAM Wednesday, April 04, 2012 6:51 PM

