Problem Moving Mailboxes

strangebloke
strangebloke used Ask the Experts™
on
Hi

I'm trying to migrate our user mailboxes from our current Exchange 2003 server to a new Exchange 2003 server.  Both are Exchange 2003 SP2 with all patches installed via Shavlik Netcheck Protect.  They have a single store on each.  Both are on the same domain and within a couple of switches of each other in the server room

What's happening is this.   I use Exchange tasks to move the mailbox from the source server to the destination server  the gui reports the move was successful.  However in the Application event log on the source server two errors are logged.

Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      General
Event ID:      10001
Date:            20/07/2009
Time:            13:10:27
User:            N/A
Computer:      Source server name
Description:
The folder with folder ID 1-1D4F338 could not be deleted. Additional information: 0x8004010f.

Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      General
Event ID:      1203
Date:            20/07/2009
Time:            13:10:27
User:            N/A
Computer:      Source server name
Description:
Failed to delete the mailbox of /O=CHESHIRE DATASYSTEMS LTD/OU=CHESHDATASYS/CN=RECIPIENTS/CN=Username with error 0x8004010f.

The folder name in the first error varies I've just left the last instance in as an example.
The mailbox appears in the list on the new server store with a size roughly the same as it was on the source server.  However the mailbox also still appears in the source server store but only a few hundred kb in size.

If I leave it until the rules have synchronised on the new server you can then connect to the mailbox but only the calendar is visible so i presume that's pointing to the source server.  If I then attempt to move the mailbox back I get an error from the gui and the following in the event log.

Event Type:      Error
Event Source:      MSExchangeAdmin
Event Category:      Move Mailbox
Event ID:      9169
Date:            20/07/2009
Time:            13:28:26
User:            N/A
Computer:      Target server name
Description:
Failed to copy basic mailbox information.
Error: A duplicate mailbox was found due to problems during a Move Mailbox procedure. The duplicate mailbox has been deleted. Try again later.

About quarter of an hour later it sorts itself out and the mailbox is accessible and seems to work fine on the new server.

I've done a fair bit of searching and found many references to a problem with the Offline Address book but nothing that quite matches what I'm seeing.  Also found a hotfix which claims to fix the duplicate mailbox problem,  http://support.microsoft.com/?kbid=940012, but it mentions other errors that I'm not seeing.  Because of that I don't feel comfortable trying to install it in case it's the wrong hotfix and makes things worse.

I've got about 300 accounts to move so I'd appreciate any ideas that would save me having to go through this rigmarole three hundred times.





Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
this could also be related to AD replication .Since homeMDB attribute must be popoulate in AD.
Could you run repadmin /syncall and then verify the source mailbox exists or gets automatically deleted.Also run clean up agent on the source mailbox server !
thanks,
consultkhan

Author

Commented:
Thanks for the replies.  I haven't got a mailbox in this state to test on at the minute.  I'll set up some test mailboxes and try the repadmin and clean up idea.

Mike, thanks for the links.  The first one I haven't seen before I'll have a closer look at that.  The second doesn't apply here as the mailboxes I've tried to move have been in use and have sent and received e-mails.  The third is the workround that I've been using to finish off the transfer, I'm trying to find a way of getting it to work without having to do that every time.

Also I don't see a red X on the mailbox on the source server but that may be because I haven't waited long enough for everything to catch up.  I'll get the test mailboxes set up and get back to you.  Thanks.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
OK I've made a small amount of progress.  I set up two test accounts yesterday, logged on and opened Outlook sent and received a few e-mails.  I then restored copies of my email box into them.  This morning I migrated both of them over to the new server and they worked perfectly.

No idea what that proved.  I've just migrated the account of a long time user who has been off on maternity leave since October.  That worked without leaving the account behind on the source server.  So it appears that the original problem might be caused by logon sessions still being open.  Maybe another user is viewing the calendar or I haven't waited long enough after a user closes their Outlook to migrate?  As i said this user has been off for months and the mailbox has not been used.  I'm thinking I might need to get the migration done out of hours to make sure no-ones connected to anything.

I did still get the delay in synchronising rules error but left it for an hour and then opened the mailbox and they seem to be OK now.  I had tried to fix the delay by installing this hotfix http://support.microsoft.com/?kbid=916694.  It claims to speed up rule synchronisation.  It said it installed OK but when I came to look for the registry keys referred to in the article they aren't there.  I didn't reboot as the article says it's not needed, but it does imply that the registry keys should be there.  Any thoughts on if it's safe to create them?

Author

Commented:
Just tried another mailbox of a user that's in today.  It had all the same problems I described originally.  I ran repadmin /syncall which was fine and reported no errors.  Tried running cleanup agent on the source server and it marked the account left behind with a cross.  Mailbox started to work but showed some reminders for old meetings from days ago.  I checked the source server again later to find that the account was still there and no longer marked with a cross.

No choice but to try moving the account back and letting it go through the process of deleting the duplicate.  Any other ideas?
Run out of time.  Must move mailboxes this weekend.  Have to do it the hard way I guess.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial