Solved

Exchange Server 2003 Problems

Posted on 2011-02-13
4
302 Views
Last Modified: 2012-05-11
  I have been playing with Windows 2003 to SBS 2011 migration. All goes pretty well except when I try to migrate the Exchange Server 2003 mailboxes. About half of them fail with the error message that there are too many corrupt messages.

   I suppose one more addition step before the migration might be a good idea. Maybe checking the Exchange Server 2003 database for corrupt messages and repairing them. Which eseutil option would do that? Repair?
0
Comment
Question by:jimbecher
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 74

Accepted Solution

by:
Glen Knight earned 500 total points
ID: 34882752
You will have to increase the skip corrupt item count in the move mailbox wizard.
You may also find my article here useful, it's for SBS2008 but the steps as I have found in my recent SBS2011 migration guide are almost identical: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_2465-Migrate-Windows-2003-with-Exchange-to-Small-Business-Server-2008.html
0
 
LVL 11

Author Comment

by:jimbecher
ID: 34882793
  Been there done that :) I increased the skip count to 500. Failed half the mailboxes right off the bat. Do you think 500 is too low? I am going to have to revert to the original question. How do you detect and fix corrupt messages on the 2003 side before migration?
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34882823
well, that's kind of difficult because if they are corrupt Outlook won't display them.
Repairing the database MIGHT fix it but there is no guarantee and that's a lot of downtime eating in to your migration.

I would increase the corrupt count on one mailbox to say 1000 and see if it gets past it.
0
 
LVL 11

Author Comment

by:jimbecher
ID: 34882870
  You are correct. This is just a "test" migration and so far 90% of it has been spent on migrating these problem mailboxes. I'll keep playing :)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Suggested Solutions

Utilizing an array to gracefully append to a list of EmailAddresses
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

738 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