Solved

Exchange Server 2003 Problems

Posted on 2011-02-13
4
305 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

Want Experts Exchange at your fingertips?

With Experts Exchange’s latest app release, you can now experience our most recent features, updates, and the same community interface while on-the-go. Download our latest app release at the Android or Apple stores today!

Question has a verified solution.

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

Find out what you should include to make the best professional email signature for your organization.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

617 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