Clicky

I have a new Exchange 2010 SP1 server running, and have moved over the vast majority of my Exchange 2003 mailboxes to it with no problems.  However, there are some mailboxes that fail every time I try to move them.

Below is an example of a log from one move failure, which is the same for all the other mailboxes that fail to move.

 12/1/2011 10:39:23 PM [ex10] 'kbe.local/Users/Administrator' created move request. 12/1/2011 10:39:24 PM [ex10] The Microsoft Exchange Mailbox Replication service 'ex10.kbe.local' (14.1.355.1 caps:07) is examining the request. 12/1/2011 10:39:24 PM [ex10] Connected to target mailbox 'Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e)', database 'Store3', Mailbox server 'ex10.kbe.local' Version 14.1 (Build 218.0). 12/1/2011 10:39:24 PM [ex10] Connected to source mailbox 'Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e)', database 'ex03\CT Second Storage Group\Precon Mailbox Store', Mailbox server 'ex03.kbe.local' Version 6.0 (Build 7654.0). 12/1/2011 10:41:04 PM [ex10] Request processing started. 12/1/2011 10:41:04 PM [ex10] Mailbox signature will not be preserved for mailbox 'Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e)'. Outlook clients will need to restart to access the moved mailbox. 12/1/2011 10:41:04 PM [ex10] Source Mailbox information before the move: Regular Items: 105291, 3.909 GB (4,197,163,412 bytes) Regular Deleted Items: 0, 0 B (0 bytes) FAI Items: 152, 0 B (0 bytes) FAI Deleted Items: 0, 0 B (0 bytes) 12/1/2011 10:41:06 PM [ex10] Initializing folder hierarchy in mailbox 'Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e)': 100 folders total. 12/1/2011 10:41:08 PM [ex10] Fatal error MapiExceptionNoSupport has occurred. Error details: MapiExceptionNoSupport: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80040102, ec=-2147221246) Diagnostic context:     Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=1105]     Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=685][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: 21970   StoreEc: 0x8004010F PropTag: 0x674A0014     Lid: 21970   StoreEc: 0x8004010F PropTag: 0x36138000     Lid: 31473   StoreEc: 0x8004010F     Lid: 28877   Error: 0x0     Lid: 28877   Error: 0x0     Lid: 39287       Lid: 17916   StoreEc: 0x80040102     Lid: 32252   StoreEc: 0x80040102     Lid: 7915    StoreEc: 0x80040102     Lid: 20320       Lid: 4559    StoreEc: 0x80040102     Lid: 21802       Lid: 19994   StoreEc: 0x80040102     Lid: 20202       Lid: 3305    StoreEc: 0x80040102     Lid: 32762   dwParam: 0x3FE00102     Lid: 32762   dwParam: 0x3FE4000B     Lid: 32762   dwParam: 0x67590102     Lid: 32762   dwParam: 0x675A0102     Lid: 32762   dwParam: 0x30080040     Lid: 32762   dwParam: 0x675C0102     Lid: 32762   dwParam: 0x67510003     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      at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.WaitUntilDataIsProcessed()    at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.ImportBuffer(Int32 opcode, Byte[] data)    at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.Flush()    at Microsoft.Exchange.MailboxReplicationService.ProgressTrackerTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.Flush()    at Microsoft.Exchange.MailboxReplicationService.FxProxyTransmitter.Microsoft.Exchange.MailboxReplicationService.IFxProxy.Flush()    at Microsoft.Exchange.MailboxReplicationService.LocalSourceFolder.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo(IFxProxy destFolderProxy, PropTag[] excludeTags)    at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.<>c__DisplayClass1.<Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo>b__0()    at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenuserCallDelegate operation)    at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo(IFxProxy destFolder, PropTag[] excludeTags)    at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CopyFolderProperties(FolderRecWrapper folderRec, ISourceFolder sourceFolder, IDestinationFolder destFolder, FolderRecDataFlags dataToCopy)    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass34.<>c__DisplayClass38.<CreateFolderHierarchy>b__31()    at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenuserCallDelegate operation)    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass34.<CreateFolderHierarchy>b__30(FolderRecWrapper folderRec, EnumFolderContext context)    at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)    at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)    at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2d(MailboxMover mbxCtx)    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)    at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenuserCallDelegate del, FailureDelegate failureDelegate) Error context: -------- Operation: IMapiFxProxy.ProcessRequest OpCode: TransferBuffer DataLength: 1710 -------- Operation: IMapiFxProxy.ProcessRequest OperationSide: Target Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e) OpCode: TransferBuffer DataLength: 1710 12/1/2011 10:41:08 PM [ex10] Removing target mailbox 'Primary (34eacd2b-6f09-44c3-bf86-57bf46fa1f6e)' due to an offline move failure. 12/1/2011 10:41:08 PM [ex10] Relinquishing job.                             
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: 62: 63: 64: 65: 66: 67: 68: 69: 70: 71: 72: 73: 74: 75: 76: 77: 78: 79: 80: 81: 82: 83: 84: 85: 86: 87: 88: 89: 90: 91: 

Select allOpen in new window



I have tried every single thing I could find on Experts Exchange as well as everywhere else on the internet, and just cannot find anything that will allow me to move this.

I've used PFDavAdmin to fix the ACL, fixed the missing anonymous entries with PFDavAdmin, and pretty much everything else I can do with PFDavAdmin.  I also tried removing delegates that were on this mailbox.  It's worth noting that I can move the mailbox to another database on the Exchange 2003 server without failure.

I would be eternally grateful to anyone who can help with this.

asked 12/01/2011 09:55

paulhkbe's gravatar image

paulhkbe ♦♦


8 Answers:
1. Have seen this happen because of mailbox rules.  You can use MFCMAPI http://mfcmapi.codeplex.com/ to remove all mailbox rules and then try to move again.

2. Check the resolution on this thread as well http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/b4fd209d-3c10-4975-b1b3-ee02c054fabf/

3. Last option would be to export to PST and then IMPORT.

How many users have this issue?
link

answered

lucid8's gravatar image

lucid8

check the homeMTA attribute for the Microsoft System Attendant mailbox
you can also try using PfDavAdmin to reset the DACL on the mailbox
link

answered 2011-12-02 at 19:03:17

endital1097's gravatar image

endital1097

lucid8:

1. I tried that with the rules.  Removed them using MFCMAPI, the move still fails with the same message.
2. I also tried that.  I used PFDavAdmin to remove all permissions except default from all of his folders, not just calendar.  No luck.
3. This seems to be happening with about 20 users out of 150.  There is no common link between them, they are not all in the same 2003 database, for example.

endital1097:

The homeMTA attribute for these users is correct, so that's not the problem.  As to your suggestion to use PFDavAdmin to reset DACLs, you'll see in my original post that I've don everything possible with PFDavAdmin to no avail.
link

answered 2011-12-03 at 11:38:29

paulhkbe's gravatar image

paulhkbe

lucid8:  As far as your comment about exporting a PST and importing, I did this for one users and it screwed things up, because anyone who replied to an email from that person from before their mailbox was moved, got an NDR.  Also if anyone used their auto-complete list in Outlook, they'd get an NDR.  I had to tell everyone to delete the entries for that person from their auto-complete list.

Is there a good procedure for exporting and importing, ensuring this sort of thing doesn't happen again, should this be the only way to get these mailboxes moved?
link

answered 2011-12-04 at 17:45:51

paulhkbe's gravatar image

paulhkbe

Regarding the Export/Import via PST issue what you are encountering is the LegacyExchangeDN issue as outlined below and you can solve it 1 of 2 ways.

1. Export, Delete and attempt to move empty mailboxes
A: Kick the users you are going to export off their systems
B: Make a database backup
C: Export all mail to PST
D: Validate all email is accessible within PST
E: Delete all Email in that mailbox from the Server and ensure that Deleted Items is emptied as well
F:  Now try the mailbox move which if successful will set the LegacyExchangeDN as part of the process
G: Import email
H: Done


2. If you don't want to use the above or it doesn't work then you can set the LegacyExchangeDN by Hand

by exporting to PST and then importing to the new server there is an MS problem where imported messages calendar items/appointments made from the old system will  fail on acceptance, updates and other replies and modifications may not work right because the X500 addresses from the original Exchange server cannot resolve to the mailboxes in the new Exchange server.

 
Here are some details about that problem and how to resolve. Basically, you need to obtain the LegacyExchangeDN from the old Exchange install to be added to the new recipients as an X500 format ProxyAddress entry. It's not too bad to do, once you know what to do but it can cause a major amount of frustration for the administrator and end users

 
 Here is a  how to Doggy Piggy Bunny explanantion link http://blogs.technet.com/b/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx

 
 here is another article that may be more helpful as well http://www.simple-talk.com/sysadmin/exchange/exchange-e-mail-addresses-and-the-outlook-address-cache/  a

and then check out this MS forum issue that discusses it in detail as well http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/f99244d7-facf-4ad9-a83e-f6d3baa1ba8b/

 Microsoft also makes a LegacyExchangeDN tool http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19034 The Tool is not really needed it just makes some of the change process a bit easier and the above first  article shows how to use it as well  
link

answered 2011-12-04 at 17:48:44

lucid8's gravatar image

lucid8

Well, here's what I ended up doing.  Before I setup our Exchange 2010 server in our environment, I setup an Exchange 2007 server, just in case I'd end up needing it for something.  I powered it back up (it's been off for 45 days, it's a VM). I moved one of the un-movable mailboxes from 2003 to 2007, and then from 2007 to 2010.  It worked!

Thank you all for your ideas.
link

answered 2011-12-05 at 07:30:06

paulhkbe's gravatar image

paulhkbe

Suggested solution was viable, but I ended up moving the problem mailboxes from 2003 to 2007, then from 2007 to 2010.
link

answered 2011-12-10 at 06:20:03

paulhkbe's gravatar image

paulhkbe

Thanks for the update and the points
link

answered 2011-12-10 at 06:23:00

lucid8's gravatar image

lucid8

Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×25
×70
×2
×1

Asked: 12/01/2011 09:55

Seen: 545 times

Last updated: 12/09/2011 10:23