Solved

2013 Exchange database migration empty

Posted on 2016-08-08
7
20 Views
Last Modified: 2016-08-14
I recently migrated 10 mailboxes from 1 DB to the another and they completed successfully but after the move the migration tab in EAC didn't work. It would generate an error when I clicked on it. I went to view the DBs and found that one had dismounted and wouldn't mount. I ended up repairing the DB and now I'm able to mount it and also able to open the Migration tab again BUT when I attempt a mailbox migration it doesn't queue it. I click on the Migration tab in EAC and it's empty. No errors.
0
Comment
Question by:jaynes-it
7 Comments
 

Expert Comment

by:Member_2_7970830
ID: 41747569
you have to clear all the move requests. See if there are any by using the following.

Get-MoveRequestStatistics -MoveRequestQueue <database>  

Then remove them using:

Remove-MoveRequest
0
 
LVL 16

Expert Comment

by:FOX
ID: 41747571
run this command in exchange management shell to check if anything is still lingering

Get-MoveRequest | where {$_.status -ne ”Completed”} | Get-MoveRequestStatistics

ref link:  http://jermsmit.com/tag/get-moverequeststatistics/

more useful commands
ref link:  http://www.exchangemaster.net/index.php?option=com_content&task=view&id=181&Itemid=1&lang=en
0
 

Author Comment

by:jaynes-it
ID: 41747615
DisplayName               StatusDetail              TotalMailboxSize          TotalArchiveSize         PercentComplete
-----------               ------------              ----------------          ----------------         ---------------
Ray K****                CompletedWithWarnings     1.11 GB (1,191,619,840...                          100




[PS] C:\Windows\system32>
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:jaynes-it
ID: 41747619
you have to clear all the move requests. See if there are any by using the following.

Get-MoveRequestStatistics -MoveRequestQueue <database>  

Then remove them using:

Remove-MoveRequest

I tried this but it didn't return anything
0
 
LVL 9

Expert Comment

by:Kevin k
ID: 41748496
First, you must make sure that the mailbox in DB1, not in DB2.

Second, you can run the following command to check additional information about the mailbox move:

Get-MoveRequestStatistics -Identity UserName -IncludeReport |Export-CSV C:\MRStats.csv

As a workaround, run Get-MigrationBatch -Identity "BatchJobName" | fl command and see if it pointed you directly on the cause.

Also have a look at below earlier threads might helps you to get in more detailed:

Thread1

Thread2

Also check this blog to move an Exchange Server 2013 Database to a New Location: http://exchangeserverpro.com/exchange-2013-move-database-to-new-folder-path/

Hope this helps!
0
 

Accepted Solution

by:
jaynes-it earned 0 total points
ID: 41748953
what ended up fixing this problem was recreating the migration mailbox.
1
 

Author Closing Comment

by:jaynes-it
ID: 41755365
i had to contact microsoft support and we spent hours recreating the migration mailbox which resolved the batch migrations.
0

Featured Post

Why are Office 365 signatures so complicated?

Trying to setup transport rules for Office 365 email signatures and can’t quite figure it out? Having to test the signature over and over? Make things simple by using Exclaimer Cloud - Signatures for Office 365.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
Find out what you should include to make the best professional email signature for your organization.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now