Pro-Exchange,Lync & Office 365
Belgian Microsoft Unified Communications Professionals
Microsoft Exchange Server, Microsoft Lync Server & Office 365
Exchange 2010 SP1: MoveRequest fails with “MapiExceptionNoSupport”

One of my colleagues, Geert Gijsels, recently came across the following interesting issue.

During the moves of different mailboxes from Exchange 2003 to Exchange 2010 (SP1) there was a mailbox that repeatedly failed at 10% throwing a “MapiExceptionNoSupport”-error.
Together with the error, the following event would show up in the Application log of the Exchange 2010 Server:

clip_image001

The Move Request log contained the following information. I omitted some lines from the information for readability:

1/11/2012 2:38:17 PM [EX2010] 'domain.local/admin' created move request.
1/11/2012 2:38:19 PM [EX2010] The Microsoft Exchange Mailbox Replication service 'EX2010.domain.local' (14.1.355.1 caps:07) is examining the request.
1/11/2012 2:38:19 PM [EX2010] Connected to target mailbox 'Primary (a0b7df99-3726-409b-b767-102f078eecca)', database 'Mailbox Database - 01', Mailbox EX2010 'EX2010.domain.local' Version 14.1 (Build 218.0).
1/11/2012 2:38:19 PM [EX2010] Connected to source mailbox 'Primary (a0b7df99-3726-409b-b767-102f078eecca)', database 'EX2003\2nd_Storage_Group\MailBox2', Mailbox EX2010 'EX2003.domain.local' Version 6.0 (Build 7651.0).
1/11/2012 2:38:29 PM [EX2010] Request processing started.
1/11/2012 2:38:29 PM [EX2010] Mailbox signature will not be preserved for mailbox 'Primary (a0b7df99-3726-409b-b767-102f078eecca)'. Outlook clients will need to restart to access the moved mailbox.
1/11/2012 2:38:29 PM [EX2010] Source Mailbox information before the move:
Regular Items: 3166, 272.5 MB (285,690,080 bytes)
Regular Deleted Items: 30, 40.2 MB (42,149,589 bytes)
FAI Items: 150, 0 B (0 bytes)
FAI Deleted Items: 0, 4.871 KB (4,988 bytes)
1/11/2012 2:38:29 PM [EX2010] Initializing folder hierarchy in mailbox 'Primary (a0b7df99-3726-409b-b767-102f078eecca)': 125 folders total.
1/11/2012 2:38:30 PM [EX2010] Fatal error MapiExceptionNoSupport has occurred.
Error details: MapiExceptionNoSupport: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80040102, ec=-2147221246)
Diagnostic context:
     Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=1216]
     Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=677][latency=0]
     Lid: 23226 --- ROP Parse Start ---
   

     …

     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(GenericCallDelegate 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(GenericCallDelegate 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(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMapiFxProxy.ProcessRequest
OpCode: TransferBuffer
DataLength: 3127
--------
Operation: IMapiFxProxy.ProcessRequest
OperationSide: Target
Primary (a0b7df99-3726-409b-b767-102f078eecca)
OpCode: TransferBuffer
DataLength: 3127
1/11/2012 2:38:30 PM [EX2010] Removing target mailbox 'Primary (a0b7df99-3726-409b-b767-102f078eecca)' due to an offline move failure.
1/11/2012 2:38:30 PM [EX2010] Relinquishing job

At first, there seemed to be a problem with the DACL of the mailbox (different folders had got certains rights for “NT Authority\Anonymous Logon” that were removed). Unfortunately, resetting the rights using PFDAVadmin yielded no solution.
A call was opened at Microsoft which revealed that this was a known issues and a hotfix was already available (KB2579051) but never made it into any Update Rollup:


I’m currently trying to get more information on more information about what exactly could case this error and what the hotfix exactly does. As soon as I get more information, I’ll blog about it here.


Credits: A big thanks to
Geert for providing me the information and details for this blog post! Geert will shortly also be publishing his article about this issue on Xylos’ blog.


Posted 01-13-2012 5:55 by Michael Van Horenbeeck