Cannot move mailbox using Move Mailbox Wizard

Error was found for "Name" ( because: Error occurred in the step: Moving messages. Unable to unlock mailbox with error: MAPI or an unspecific service provider.
ID no: 00000000-0000-00000000, error code: -1056749254
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
1. What SP Level and RU do you have installed?

2. Are you trying to move the mailbox to a new server OR into a new DB in the same server?

3. If you are using two different servers ensure they are both pointing to the same DNS server

4. Have you tried to reboot the Exchange 2007 server or servers if you have multiple Exchange 2007 servers?  I have seen a few instances where this resolved the issue

5. Check and make sure that you have proper permissions assigned as per below article...

6.  Do you have latest SP & RU running on the server? Install latest SP and RU and then try again
Get the latest service pack or update rollup for Exchange 2007

7. Try moving the mailbox with Move-Mailbox cmdlet including -Verbose switch which shows the steps in detail and where it gets stuck while moving the mailbox and then post the errors back here so we can review
Move-Mailbox cmdlet

8. The issue can be caused by the corrupted items in the mailbox.   So check the “skip the corrupted messages” and set “Maximum number of messages to skip” to 1000. Then test the issue again.  
NOTE: You also can use switch –BadItemLimit  within the move-mailbox cmdlet referenced above

9. You can also try to do run isinteg against the database to see if it can clean up any problems, however that will require more offline downtime that the above issues so I would do this last unless you are moving the mailbox out of a database with known issues.

indsupportAuthor Commented:
The DB is huge and needs to be defragged, then have it split up
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.