• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 154
  • Last Modified:

Why this mailbox always failed in moving to another exchange server?

This is setting up a new Exchange Server 2013 to join with one existing Exch2k13 server. The objective is, moving all of the mailboxes from old server to this new server. However, I tried from ECP, and the status shown completed, but none was synced and moved.

I tried with powershell command - new-moverequest, and found that some mailboxes can moved but only one, with total size of 16.0 gb. When I tried on this failed mailbox again, it shows inprogress, but 2 hours later, it shows failed.
Why the move failed? How should I troubleshoot and get the mailbox migrated successfully?

Appreciate help!
0
MichaelBalack
Asked:
MichaelBalack
1 Solution
 
Manoj BojewarCommented:
Follow below steps to resolve this issue

1 ) First you suspend and remove failed migration.
2)Restart exchange mailbox replication services
3)Start the user mailbox migration again.
0
 
Simon Butler (Sembee)ConsultantCommented:
You need to look at the log file to see why it is failing.
A 16gb mailbox though is likely to have issues - corrupt items or items that are over the limit size set on the new server. Both of those can cause the migration to fail. The log should tell you why it has failed.

Simon.
0
 
Gareth GudgerCommented:
Hey Michael,

Have you tried setting/raising the bad item limits to allow the migration process to drop corrupted items?

Also, another option would be to move the mailbox to another database on the old server. Once it is moved, then migrate it to 2013.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
MichaelBalackAuthor Commented:
Hi all,

This is how I did it:

   1. Using ADSI Edit, and browse to the properties of the affected user account that owns the mailbox
   2. Look for msExchMailboxMovestatus and msExchMailboxMoveFlag, and clear them
   3. rerun "new-moverequest mailbox1 -targetdatabase "DB2"

And mailbox successfully moved in 5 hours.
0
 
Gareth GudgerCommented:
Glad you got it going. Please accept your own comment as the answer.
0
 
MichaelBalackAuthor Commented:
By following the steps, i managed to get the mailbox moved without problem. Think most likely the values in the given msexch attributes stop the attempt to move the mailbox in the subsequent try.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now