Moving mailboxes and corrupted Calendar

by Bharat Suneja

Moving mailboxes from an Exchange 2000 virtual server (EVS) to an Exchange Server 2003 EVS – can’t seem to move 1 particular mailbox.

User has a history of corrupted Calendar folder/items – Oultook hangs immediately when choosing the Calendar folder from the folder list. (Lot of 8217s – KB327864: Meetings visible in Outlook may not be visible in OWA or non-MAPI clients).

Errors :

Event ID: 1008

Unable to move mailbox ‘ABC’.

Error: The MAPI call failed.

MAPI or an unspecified service provider.

ID no: 80004005-0000-00000000

Event ID: 9172

Failed to copy messages to the destination mailbox store.

Error: The MAPI call failed.

MAPI or an unspecified service provider.

ID no: 80004005-0000-00000000

Event ID:8506

Unable to move mailbox ABC.

A problem occurred while getting the properties for a message.

Internal parent folder ID: e-21F33E; Message ID: 2-30B3DFA; Error code: 0x80004005.

Run ISINTEG to check for any problem in the database “Second Storage Group\Mailbox Store2 (SERVRENAME)”.

Reference: KB264119. Suggests ISINTEG. Ran ISINTEG once. Didn’t help. (Ran ESEUTIL /p as well… ). No dice. ISINTEG again 4 more times (with only one mailbox the store was already compacted to less than 500 Mb.). Tried mailbox move again to Store 1 in target server, worked. Moved to Store 2 in target server, worked again!

{ 4 comments… read them below or add one }

netjustin February 5, 2007 at 11:30 am


Thanks for the entry. I’m experiencing this problem with several mailboxes.

You mentioned having compacted the database and running “ISINTEG again 4 more times”. Can you be more specific? What switches did you use to end up being able to move the problem mailbox? I’d like to avoid using MDBVu32 because having referenced the manual it seems like using a shotgun to unlock the front door.

Justin ([email protected])


Bharat Suneja February 5, 2007 at 11:53 am

Don’t quite remember – it was a long while ago (that post is from 2004 :). If the KBA points to ISINTEG /Attach, perhaps that’s that’s what I must have referred to.

Generally I try to include as much details as possible, but back when I started this blog, it was a quick way of maintaining “TechNotes” for myself and few others, and I can see why such details may have been missed. :)


netjustin February 8, 2007 at 12:19 am

Having re-ran ISINTEG on the entire database, after that (AND after nightly maintenance) then I was able to move all of the mailboxes without issue.

As far as the /ATTACH switch, I couldn’t get any such switch to work. I wondered if it should have been “ISINTEG -test attach” or something of that nature, but never went there.

Thanks again, friend.


Anonymous April 1, 2008 at 2:49 pm

check if the size of the mailbox you are moving is smaller then the limit of the destination server


Leave a Comment

Previous post:

Next post: