34.5 C
Tuesday, June 18, 2024

New-MailboxExportRequest : Couldn’t connect to the source mailbox – Fix

I just had to Export few mailboxes to PST.

Just struck up with an  Error.. Thought it is corruption…But the fix was beyond my thinking.

Exchange 2010 SP2



VERBOSE: [14:14:09.565 GMT] New-MailboxExportRequest : Couldn’t connect to the source mailbox. –>
MapiExceptionProtocolDisabled: Unable to make connection to the server. (hr=0x80004005, ec=2008)
Diagnostic context:
Lid: 59431   EMSMDB.EcDoConnectEx called [length=146]
Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x7D8][length=56][latency=17]
Lid: 59505   StoreEc: 0x7D8
Lid: 52465   StoreEc: 0x7D8
Lid: 60065
Lid: 33777   StoreEc: 0x7D8
Lid: 59805
Lid: 52209   StoreEc: 0x7D8
Lid: 56583
Lid: 52487   StoreEc: 0x7D8
Lid: 19778
Lid: 27970   StoreEc: 0x7D8
Lid: 17730
Lid: 25922   StoreEc: 0x7D8
VERBOSE: [14:14:09.567 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:OnComplete.
Couldn’t connect to the source mailbox.
+ CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : 6B6493C8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

VERBOSE: [14:14:09.577 GMT] New-MailboxExportRequest : Ending processing &


Fix –

Go the Properties of the mailbox

Make Sure MAPI is Enabled




Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles


  1. This wasn’t the cased in my environment. Luckily, restarting DAG nodes helped.

    I use: Win 2008 R2 w/ Exchange 2010 SP3 RU2 (DAG)

  2. Thank you for sharing your solution to this!!! I was scratching my head on this one and worried about my mail store since I had never seen a MailboxExportRequest fail before. I had this exact issue…I had disabled all protocols on a user’s mailbox, something I’d never bothered with before, and sure enough re-enabling MAPI fixed it.

  3. New-MailboxExportRequest : Couldn’t connect to the source mailbox error only for few mailboxes

    I exported 700+ mailboxes from same exchange server and stuck with few mailboxes giving me same error.

    group of mailboxes which are giving me same error have nothing in common, they don’t belong to same OU.

    checked mailbox features properties as well. MAPI is enabled.

    mailboxes which are giving me error exist in exchange, no spelling mistake

    I am not understanding when same command in same server worked for 100’s of mailboxes why it doesn’t work for few mailboxes?

  4. Also check the MAPIBlockOutlookNonCachedMode setting. If this is set to True, the export will fail with the same “Couldn’t connect to the source mailbox” error.

    In Exchange Shell:
    Set-CASMailbox -MAPIBlockOutlookNonCachedMode $false

  5. I really do believe each of the ideas you may have offered on your own post.
    These are very convincing and can definitely work.
    Still, the posts are too short for starters. Might just you please prolong them a
    little bit from subsequent time? Many thanks for the post.

  6. i checked, and for my users MAPI is enabled on checking Exchange console
    also tried CASMailbox -MAPIBlockOutlookNonCachedMode $false. But my export is still failing
    Any ideas?


Please enter your comment!
Please enter your name here