Thursday, January 19, 2006

MAPI errors when moving mailboxes

I spent the better part of the day today working through a problem with the Move Mailbox wizard. I was in the final phase of an Exchange 5.5 to Exchange 2003. Moving the mailboxes one or two at a time seemed to work okay, but they would timeout when more than two or three mailboxes were being moved at a time. The message in the move mailbox log showed:

errorCode='0xc1050115'
An unexpected, unknown error has occurred.MAPI or an unspecified service provider.
ID no: 80040115-0000-00000000

The following event showed up in the event viewer each time a move mailbox failed:

Event Type: Error
Event Source: MSExchangeAdmin
Event Category: Move Mailbox
Event ID: 1023
Date: 1/19/2006
Time: 9:26:13 AM
User: N/A
Computer: xxxxxxxx
Description:Unable to set a property on the message store on 'xxxxxx'. Result: Network problems are preventing connection to the Microsoft Exchange Server computer.An unexpected, unknown error has occurred.Microsoft Exchange Server Information StoreID no: 80040115-0514-000006be

My first instinct was network problems. We hard-coded the network adapters on both the source and destination servers to 100Mb/s, full duplex and put the servers on a different switch. None of these things had any affect, so I did Google searches and came up with possibilities such as corrupted messages. After running ESEUTIL and ISINTEG a couple of times with no success, we were just about to use ExMerge to archive everything to PST and then move the mailboxes once they were smaller.

However, simply copying the first mailbox's PST file (80MB) took 30 minutes. However, it copied fine from the 5.5 server to a different server. So, yep, you guessed it, something about the network adapter was not working properly. We switched it over to a GB Ethernet switch and everything was just shiny!

I never got to the bottom of why network performance for that one server was so bad when it was in a 100MB switch, but the moral of the story is to not forget the basics.

4 Comments:

At 1:19 AM, Blogger Mister XR said...

Holy moses, you saved me with that one. Some of these people have 2GB mailboxes. They think I'm running GMail or something. grumble!

 
At 6:37 AM, Blogger GeoffM said...

Well, I just spent $245 and three days working on a similar issue with MS - different mapi error, this one was errorCode="0xc1054005" The MAPI call failed. MAPI or an unspecified service provider. ID no: 0004005-0000-00000000

And the fun part was it only happened moving the mailbox from an Exchange 2000 server to an Exchange 2003 server. 2000 to 2000 moved just fine.

Turns out after a bunch of troubleshooting that there was a folder in the mailbox that had been programmatically created and it had corrupt DACLs on it. MS has a nifty tool called PFDavAdmin that can show you bad DACLs on a mailbox, and better yet, fix them. Once I fixed the DACL issue the mailbox moved with no problem.

Hope this helps someone else (and saves you $245!!)

Geoff

 
At 6:43 AM, Blogger GeoffM said...

Sorry, the MAPI error code got cut off so in case anyone else is googling for this here's the real MAPI error:

errorCode="0xc1054005" The MAPI call failed. MAPI or an unspecified service provider. ID no: 80004005-0000-00000000

Geoff

 
At 4:41 AM, Blogger nalle said...

I had this problem when i recently tried to move boxes from one 2003 to another...

and the solution for me was to increase the boxes, since they cant go over 2gb as standard....
(silly me)

Here is an great guide how to allow boxes to go over 2gb:
http://www.petri.co.il/setting_mailbox_limits_over_2gb.htm

//nalle

 

Post a Comment

<< Home