none
Moving mailbox from Exchange 2007 to Exchange 2010 fails

    Question

  • We are migrating from Exchange 2007 to Exchange 2010, but I'm getting failures when I try to move some mailboxes of my co-workers. I've successfully moved a 27 mailboxes, but I cannot move mine and a few co-workers. They all fail with the same type of error:

    Mailbox move for '<< AD PATH>>' (6dd14402-f9d0-44fb-94a1-13f9cf8c8f11) has failed.

    Error code: -2147221246

    MapiExceptionNoSupport: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80040102, ec=-2147221246)

    Diagnostic context:

    Lid: 18969 EcDoRpcExt2 called [length=945]

    Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=345][latency=15]

    Lid: 23226 --- ROP Parse Start ---

    Lid: 27962 ROP: ropFXDstCopyConfig [83]

    Lid: 27962 ROP: ropTellVersion [134]

    Lid: 27962 ROP: ropFXDstPutBufferEx [157]

    Lid: 17082 ROP Error: 0x80040102

    Lid: 31329

    Lid: 21921 StoreEc: 0x80040102

    Lid: 27962 ROP: ropExtendedError [250]

    Lid: 1494 ---- Remote Context Beg ----

    Lid: 1238 Remote Context Overflow

    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040

    Lid: 4367 StoreEc: 0x80040102

    Lid: 7695 StoreEc: 0x80040102

    Lid: 19936

    Lid: 4559 StoreEc: 0x80040102

    Lid: 21802

    Lid: 19994 StoreEc: 0x80040102

    Lid: 20202

    Lid: 3305 StoreEc: 0x80040102

    Lid: 32762 dwParam: 0xE080003

    Lid: 32762 dwParam: 0xE230003

    Lid: 32762 dwParam: 0xE270102

    Lid: 32762 dwParam: 0xE580102

    Lid: 32762 dwParam: 0xE590102

    Lid: 32762 dwParam: 0xF000102

    Lid: 32762 dwParam: 0xFF40003

    Lid: 32762 dwParam: 0x10F4000B

    Lid: 32762 dwParam: 0x10F5000B

    Lid: 32762 dwParam: 0x10F6000B

    Lid: 32762 dwParam: 0x300184B0

    Lid: 32762 dwParam: 0x300484B0

    Lid: 32762 dwParam: 0x3FE5000B

    Lid: 32762 dwParam: 0x3FE70003

    Lid: 32762 dwParam: 0x361384B0

    Lid: 32762 dwParam: 0x36170003

    Lid: 26346

    Lid: 4073 StoreEc: 0x80040102

    Lid: 28570 StoreEc: 0x80040102

    Lid: 29738

    Lid: 3401 StoreEc: 0x80040102

    Lid: 1750 ---- Remote Context End ----

    Lid: 26849

    Lid: 21817 ROP Failure: 0x80040102

    Lid: 22630

    Context:

    Mailbox: Primary (6dd14402-f9d0-44fb-94a1-13f9cf8c8f11)

    Folder: '/Top of Information Store/Calendar', entryId [len=46, data=00000000078F59658633B44F89220B8F6F2317680100C72C0B82B3AB9042B5A5F086016EDB42010741F3F4930000], parentId [len=46, data=00000000078F59658633B44F89220B8F6F2317680100C72C0B82B3AB9042B5A5F086016EDB42010741F73D830000]

    Operation: Folder.CopyTo

    PropTags: [ContainerContents; FolderAssociatedContents; ContainerHierarchy]


    We've installed Exchange 2007 on Win2k8, Ex2010 is installed on win2k8 R2. Both Data Center editions.


    I think it has something to do with the calender, because that's always the most detailed step, but what ....

    • Edited by Youri Thursday, November 12, 2009 8:26 AM typo
    Thursday, November 12, 2009 8:25 AM

Answers

  • hi Youri.

    Sorry for the delay in responding. Your exception indicates that there might be a problem with the ACLs on the calendar folder of the affected mailboxes. Could you try the following on one of the mailboxes:

    In Outlook, do the following:
    Right-click the Calendar folder, click Properties and select the Permissions tab. 
    Look at the permissions listed and write down all users and their regular and free/busy permissions
    Then delete all user permissions except default and save the permissions

    Attempt to move the mailbox again (you may want to wait a bit just to be safe). 
    If it works then you’re good. Add the users back that were previously removed. Repeat the process for the rest of the mailboxes. If not, unfortunately the only other suggestion is to contact PSS to help troubleshoot the issue.

    David.

    Senior Technical Writer - Exchange This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Youri Saturday, November 14, 2009 12:15 PM
    Saturday, November 14, 2009 5:17 AM
    Moderator

All replies

  • I'm not sure if this is related to your problem or not but Exchange 2010 is not supported on Windows Server 2008 R2 Datacenter. It is only supported on Standard and Enterprise.

    Thanks

    Will 
    Will Shepherd - MCSE/MCITP/MCTS (Windows 2008,Exchange 2007,OCS 2007)
    Thursday, November 12, 2009 1:06 PM
  • I'm not sure if this is related to your problem or not but Exchange 2010 is not supported on Windows Server 2008 R2 Datacenter. It is only supported on Standard and Enterprise.

    Thanks

    Will 
    Will Shepherd - MCSE/MCITP/MCTS (Windows 2008,Exchange 2007,OCS 2007)

    RTFM :), didn't see that one comming, always thought bigger is better, but I will quickly create another VM with Win2k8R2 EE, install Exchange again and give it a quick check.

    If it's the solution, why didn't Microsoft put a check in the installer about this OS thing, easy to look over IMHO.

    Get back soon, any other ideas are welcome, since it's a wild guess
    Thursday, November 12, 2009 2:55 PM
  • Unfortunately the installation of Exchange2010 on a Win2k8R2 EE gave the same result when trying to move my mailbox:

    Error: MapiExceptionNoSupport: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80040102, ec=-2147221246)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=1152]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=601][latency=109]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropFXDstCopyConfig [83]
        Lid: 27962   ROP: ropTellVersion [134]
        Lid: 27962   ROP: ropFXDstPutBufferEx [157]
        Lid: 17082   ROP Error: 0x80040102
        Lid: 31329  
        Lid: 21921   StoreEc: 0x80040102
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 1238    Remote Context Overflow
        Lid: 23066   StoreEc: 0x8004010F
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67170102
        Lid: 28444   dwParam: 0x67170102
        Lid: 36537   dwParam: 0x67170102
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x67170102
        Lid: 23066   StoreEc: 0x8004010F
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x679A000B
        Lid: 28444   dwParam: 0x679A000B
        Lid: 36537   dwParam: 0x679A000B
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x679A000B
        Lid: 23066   StoreEc: 0x8004010F
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67AD000B
        Lid: 28444   dwParam: 0x67AD000B
        Lid: 36537   dwParam: 0x67AD000B
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x67AD000B
        Lid: 23066   StoreEc: 0x8004010F
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67FE0102
        Lid: 28444   dwParam: 0x67FE0102
        Lid: 36537   dwParam: 0x67FE0102
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x67FE0102
        Lid: 23066   StoreEc: 0x8004010F
        Lid: 22086  
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x80040102
        Lid: 22630  
    So we're back to square one.
    Thursday, November 12, 2009 4:18 PM
  • hi Youri.

    We're looking at this internally. I'll get back to you shortly.

    David.
    Senior Technical Writer - Exchange This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, November 12, 2009 10:08 PM
    Moderator
  • How are you moving the mailbox?  Using the Exchange 2007 EMC won't work, you need to use the MoveRequest in Exchange 2010. 

    Any connection problems to the Exchange 2010 mailbox server in general?  FW blocking traffic etc?


    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com
    Thursday, November 12, 2009 10:29 PM
  • The error code 0x80040102 translates to MAPI_E_NO_SUPPORT which means that there should be no connection problems between the two servers.  It is related to some feature being performed with MAPI that cannot be accomplished.  This comonly occurs when using an out of date version.

    As Scott stated, make sure you perform the move on the Exchange 2010 EMC or EMS.

    If you are executed your move on Exchange 2010, then I have to ask if you installed anything in addition to Exchange 2010 on the mailbox server?  If you did install something that has its own implementation of MAPI, then you can run fixmapi.exe to reregister the correct version MAPI32.dll.
    Sean | http://seanv.wordpress.com
    Friday, November 13, 2009 12:47 AM
  • @Scott (and bit of Sean): I'm using the Exchange 2010 tools to create a local move request. No connectionproblems, since I can move almost half of the mailboxes.
    @Sean: It's a clean install. The Win2k8DC-install also has the forefront installed, but nothing more. The (test)-installation I tried on the Enterprice Edition has nothing else installed, just a typical Exchange installation. No Anti-Virus. The Fixmapi.exe gave no response in the (elevated) commandprompt. And a new move request gave same result.

    Strangly all of the mailboxes failing are used by real people. The mailboxes I could move where general mailboxes (all of them) likes ones for the helpdesk. They are of course also AD-users, but not in flesh and blood. I could also move the rooms. I could move some real people succesfully, so it's not true that I cannot move any 'real' people. I cannot come up with a difference between the real people I can move and the ones I cannot move. All of the have calanderitems. Only most of the failing ones have many items, since they work here for some years.
    Friday, November 13, 2009 8:49 AM
  • I cannot come up with a difference between the real people I can move and the ones I cannot move. All of the have calanderitems. Only most of the failing ones have many items, since they work here for some years.

    I have personally come across issues with Exchange in dealing with large calendar items or contacts.  Various issues occur such as problems enumerating number to name lookup for Outlook Voice Access when there are large numbers of contacts.  Whenever, I come across a large calendar, I tend to confront the end-users because there is really no need to keep more than 5 years worth of calendar items (I have never heard of a regulatory body requiring more than that) and definitely not on a tier one system like Exchange.  I try to convince users to purge or archive calendar items that are older than a year.

    Have you tried using exmerge on the mailboxes that are failing in Exchange 2003?  Why not remove Exchange 2010 out of the picture and check to see if the mailboxes themselves are exportable.  If exmerge fails, then you are going to have to figure out which items the export is failing on and clean up their mailbox.
    Sean | http://seanv.wordpress.com
    Friday, November 13, 2009 3:25 PM
  • We don't have a Exchange2003, but a Exchange 2007 SP2 as source server. I can try ExMerge on Monday, since I don't have the systemtools for Exchange2007 installed or available. The number of calenderitems cannot be "the" issue, since a couple of the failing mailboxes are just 6 weeks old and belong to users not that active. Furthermore, about a month ago we changed domains. Then the company taking care of the domainname change created new mailboxes on the new Exchange 2007 mailserver (the one I'm trying to put offline) using export/import through a PST file. That went fine (also exporting my mailbox to a PST file works fine, so no errors in that part). Does that rule out the test to try Exmerge as well?

    But I'll give it a try on monday, just to rule things out. In the meanwhile I'm open for suggestions.

    Friday, November 13, 2009 6:43 PM
  • hi Youri.

    Sorry for the delay in responding. Your exception indicates that there might be a problem with the ACLs on the calendar folder of the affected mailboxes. Could you try the following on one of the mailboxes:

    In Outlook, do the following:
    Right-click the Calendar folder, click Properties and select the Permissions tab. 
    Look at the permissions listed and write down all users and their regular and free/busy permissions
    Then delete all user permissions except default and save the permissions

    Attempt to move the mailbox again (you may want to wait a bit just to be safe). 
    If it works then you’re good. Add the users back that were previously removed. Repeat the process for the rest of the mailboxes. If not, unfortunately the only other suggestion is to contact PSS to help troubleshoot the issue.

    David.

    Senior Technical Writer - Exchange This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Youri Saturday, November 14, 2009 12:15 PM
    Saturday, November 14, 2009 5:17 AM
    Moderator
  • Great, it worked. Now I'm only curious how I can remove and reset the settings of the mailboxes from the server. Or is the only way to ask people to do it by themselves? The tools I've found are set-only. Not view or remove.

    Thanks
    Saturday, November 14, 2009 12:16 PM
  • This didn't work for me.  Any other ideas?

     

    Wednesday, September 22, 2010 8:13 PM
  • Hi,

    Check out http://runebelune.blogspot.com/2010/11/mapiexceptionnosupport.html.

    This has solved it for me.

     

    Rune

    • Proposed as answer by JWD2 Saturday, December 03, 2011 5:51 PM
    Friday, November 12, 2010 3:07 PM
  • I had the exact same problem and error message when moving a mailbox between two Exchange 2010 servers and this solution worked for me.  The user had a bunch of unnecessary permissions set for specific users.  After I deleted all of them, leaving just the default permissions, the mailbox moved without problem.
    Thursday, January 06, 2011 4:37 PM
  • The PFDAVAdmin utility worked great!  Thanks RuneBelune.  You saved me a lot of headaches.
    Saturday, December 03, 2011 5:52 PM
  • a few updates:

    • Exchange is now supported on windows server datacenter edition
    • Update Rollup 1 for Exchange Server 2010 Service Pack 2 fixes some of the stalled moves due to permissions (http://support.microsoft.com/kb/2579051).


    Mike Crowley | MVP
    My Blog -- Planet Technologies

    Tuesday, July 10, 2012 3:00 AM
    Moderator
  • This solution worked for me.  I am running Exchange 2010 SP2 RU4...  Thank you!


    • Edited by RoninCast Tuesday, October 02, 2012 7:26 PM
    Tuesday, October 02, 2012 7:25 PM