Error moving mailbox: Failed to copy messages to the destination mailbox store with error:...

I have an Exchange 2000 server and an Exchange 2007 server.  I am trying to migrate/move mailboxes from the 2000 server to the 2007 server using the Move Mailbox GUI from the 2007 server.  About half of them have worked without a hitch, but the other half fail.  The error message I get is "Error Code -1056749164 - Error occured in the step:  Moving messages to the destination mailbox store with error: MAPI or an unspecified service provider."  

I have set it to skip the corrupt items list as high as 100000 but the same result.  There seems to be no common denominator with the accounts I'm trying to move.  They are all in the same domain on the same server.  Any help will be greatly appreciated.

Trent
atrionmedicalAsked:
Who is Participating?
 
ee_autoConnect With a Mentor Commented:
Question PAQ'd, 250 points not refunded, and stored in the solution database.
0
 
isaman07Commented:
Usually the failed mailboxes during a move are related to the mailbox names. Make sure that the user accounts that were created on the new exchange server have the exact same username and mailbox name.
0
 
isaman07Commented:
OOOOPs. just disregard my prior post if your exchange 2007 is joined as a second exchange server within the same organization.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
atrionmedicalAuthor Commented:
Yes.  They are in the same organization in the same domain.  
0
 
isaman07Commented:
Would you try to move the mailbox using ADUC on your exchange 2000 server?
ADUC---->right click a username---->exchange atsks---->move mailbox.
0
 
brittonvCommented:
I am having the exact same problem as you.  I have found a posting by a Microsoft MVP that stated that a reboot of the exchange 2007 server might fix it.

Have you resolved this problem yet?  Have you rebooted it yet?

I am not able to reboot my server right now to test it.

0
 
atrionmedicalAuthor Commented:
No I have not resolved the issue yet and my Exchange server has been rebooted on numerous occasions.  I tried isaman07s suggestion and it did not work.  Hopefully we will get more feedback.
0
 
brittonvCommented:
Well I gave up, I installed Outlook on the server and moved the files to PST as I only had the problem with on user.  Even with the store empty, I couldn't move the mailbox.  I had to delete it on the 2003 server and make a new one on the 2007 server.

Have you thought of using EMERGE?  Take one of the accounts and export and re-import it.
0
 
atrionmedicalAuthor Commented:
Exmerge is my last resort.  I'm hoping to avoid having to use it as it a little more difficult than just clicking "Move Mailbox".  I like the easy way out.
0
 
brittonvCommented:
I hear yah!  However Exmerge may not even work (Didn't for me).

If I were you I'd choose one troubled mailbox and run Exmerge on it.  There is a single click option to export it and reimport it to the same store.  Presumably it'll fix it so that the move will work.

If it doesn't work, as it didn't for me, it is another clue as to your problem.
0
 
exonedgeCommented:
I have experienced a similar if not the same problem doing Exhange 2003 Interorg / cross org mailbox migrations to Exchange 2007.  In my scenario, I'm making the Ex2007 mailboxes ahead of time using powershells Enable-mailbox cmdlet, then I am moving the mailbox using the move-mailbox cmdlet.  The mailbox starts to move, and when it hits the deleted items folder it starts moving not only the source mailboxes deleted items folder into the target mailboxes deleted items folder, but it also starts moving the inbox items there as well and then it fails...

The only way I have gotten around this is by moving the mailbox first to another information store on the source Exchange 2003 server.  Then after waiting 5 minutes for replication, and rerunning my cross org power shel script, the mailbox moves without error.  Completely bizzare.
0
 
dbbgCommented:
Hi all, if your criteria is copy any mailbox to .pst file for some backup purpose or official purpost follow the steps, is you are getting th below error try the steps
"Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749164"

1.If u are using Exchange Server 2007 64 bit and Windows Server 2003 Environment, you cant directly copy a mail box to pst format, first you have to install the Exchange Managemenet Tools on any client machines prefarable XP or 2003 Server machine, the client machine should have Office 2003 / 2007 installed. If u need further details on installations just inform
2. Logon to the client machine (where we had installed the Exchange Management Tools) who having  any of the following permissions - Exchange Organisation Admin / Exchange Server Admin, this to be set on your Exchange Server - Organisatio Configuration - add user account (who is going to backup the mailbox - probably Administrator, the same account to be used to logon to client machine where Exchange Management Shell is installed) give the permission for the user on Main Exchange Server from there itself.
3. If you are using Exchange Server 2007 select the user mail box and give "Manage Full Access Permission" to Administrator means using whos account you are logging to Client machine,
then use the command on Management shell
Export-Mailbox Identity alias PSTFolderPath <path to where PST should be created>
alias - user account, path to where u are trying to backup (ex :  D:\mailbackup\user.pst)
0
 
dbbgCommented:
on the earlier comment the command is
Export-Mailbox -Identity username -PSTFolderPath path
0
 
jacassCommented:
I know this ticket is closed however, I have just had this problem and found it to be a permissions issue.

I granted full access permission within exchange 2007 and the problem went away, I was able to archive this user.

Please note I had previously ran a script to all users for full access rights which should of worked on all users, for some reason it either missed some or the rights have been removed.
0
 
PssTechCommented:
I did what "jacass" said and it worked for me. Just for future. Thx "jacass"
0
All Courses

From novice to tech pro — start learning today.