Error in moving mailbox to Exchange 2007 database

Posted on 2008-11-15
Last Modified: 2012-05-05
Hi Expert

I can't find any solution. Please help.

I have just installed Exchange 2007 Standard SP1 with Updates Rollout 4 installed. The Exchange Server 2007 is running on Windows Server 2008 Standard Edition with fully patches.

I've started to move 120 mailboxes from Exchange 2000 to Exchange 2007. Only 5 out of 120 were not successfully moved from Legacy Mailbox status to User Mailbox status.

I then started manually move one by one. It is still persist. I checked the Event Log. It showed Event ID 1008 with following error message:
The move-mailbox task for mailbox 'J Jen' failed.
Error: Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000

I tried Exmerge on Exchange 2000, it has no problem to extract that 5 legacy mailbox to PST files.

Does anyone has encountered it and any advice for me to resolve this issue.
Question by:chekfu
    LVL 14

    Expert Comment

    If you can get it to a PSt then export it to a PST, delete the users mailbox account and create them a new one in 2007 then import  the PST.
    LVL 15

    Expert Comment

    As a quick fix, why don't you just take the PST file that you got from the old Exchange 2000 server, manually create the 5 new mailboxes, and then merge the PSTs into the newly created mailboxes?

    This KB article mentions circumstances similar to yours, although the content of their 1008 Event is different.
    LVL 14

    Expert Comment

    Thats exactly what I just said......
    LVL 8

    Expert Comment

    The last thing that you can check is to see if you need to set "Allow Inheritable Permissions" under the security for the for the 2003 Storage Group/Mailbox Store.

    (This will have to be done in the ESM for 2003)

    Else the only option that you are left with isto Exmerge those 5 mailboxes to a PST file
    LVL 1

    Accepted Solution

    I managed to figure it out the solution. Resolved by using ADSIEDIT utility. Hints: look for LegacyExchangeDN attribute.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
    Set OWA language and time zone in Exchange for individuals, all users or per database.
    In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    761 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now