Hello, I am moving toward an upgrade to Exchange 2010 but for now I am looking for some assistance with a mailbox move problem I am experiencing with my Exchange 2003 organization. First the systems: Two Windows Server 2003 server SP2 standard edition platforms. One server has been running MS Exchange 2003 SP2 for several years and has Symantec Mail Security v 6.5 installed. The second server is a new (bare metal) installation of Exchange 2003 SP2 with the information store located in the same administrative group as the first server. I am using the Exchange tasks under System Manager to move a single mailbox from one server to the other. The process fails after a couple of seconds with an MAPI error as follows: ... <progress code="0" milliseconds="937">Connecting to destination server.</progress> - <summary isWarning="false" errorCode="0xc1050000"> The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000 - <details> ... So far I have tried several troubleshooting steps to discover the reason for this failure: I used ASDI Edit to Check the values of the HomeMDB attribute for the System Attendant Mailboxes on both the source and destination servers per the MS Support article here: http://support.microsoft.com/kb/264413 The Information Store is mounted on both servers, the user account I am moving is not disabled and does not match the account I am logging in with, I am not running the ADC service, and I am running Symantec AV with exclusions for the MBDATA folder on both servers to prevent real time protection from interfering. The account I am logging into the server to complete the move has full Exchange and Domain administrator privileges. I did review the content at the MS support article here: http://support.microsoft.com/default.aspx?scid=kb;en-us;328229 discussing minimum permissions required for Mailbox store and believe that the settings are OK. It certainly feels like a permissions type problem though. The Information store has been maintained recently with the eseutil /p utility within the past few months. If this seems to be needed I will have to schedule an outage to take the Information store offline. Thanks in advance for any other suggestions as I am stuck at this point. Greg

Have you downloaded and run ExBPA against the Exchange org? Is the mailbox you are trying to move dissabled? Are you able to move any other mailboxes, between servers or between databases on the same server? What caused you to run /P and what else happend after that? Cheers, Rhoderick NOTICE: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hi Rhoderick, The first suggestion led me to the solution. I had not used the EXBPA before and a scan led me to a permissions problem (inheritance not enabled on source server). I remedied and retried the move. Success, beauty! In response to your other questions, the account was not disabled, I wasn't able to move mailboxes in either direction between the two servers (1 db per server), and the eseutil /p was a follow up to an offline defrag to reclaim some white space. We had implemented a new offline archive strategy which was freeing up considerable space that I wanted to get back on the disk. Thanks for your help, marking this as solved. Greg

Excellent - good to hear that it is fixed. ExBPA is a great tool, please continue to use it in Exchange 2003 and also in 2010 when you get that deployed. One minor thing to say, the eseutil /P is for a hard repair of the database as is the worst thing that an Exchange admin can have to do as it means you cannot restore from backup and this is the last go at getting a corrupt DB mounted and salvaging some data from it. I think you meant to type /D which is the offline defrag. Just adding this in case someone looks at it in the future :)Cheers, Rhoderick NOTICE: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.