Tuesday , December 18 2018

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

image

 

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

image

 

Smile

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Exchange Server MVP , Publisher of CareExchange.in
Supporting/Deploying/Designing Microsoft Exchange for some years.
Extensive experience on Microsoft Technologies.

Check Also

Anonymous Application relay connectors in Exchange 2016

Lets see how to create an Anonymous Application relay connectors in Exchange 2016. Every Application ...

27 comments

  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. Thanks for this post, its realy worked.

  3. Thanks for sharing. That was the solution on my case.

  4. Thank you for slution

  5. Thanks, you just saved my day! 😉

  6. 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.

  7. Thanks bro that really work for it.

  8. You da Man-oharan!

  9. It worked! I believe the user should not be disabled in AD as well.

  10. Thanks much

  11. 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?

  12. This worked for me…thanks for the solution.

  13. Thanks the issue is resolved….

  14. hi Sir

    thank you and keep posting good stuff like this

  15. 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

  16. 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.

  17. I love you, thanks, ME ESTABA VOLVIENDO LOCO

    gracias!!

Leave a Reply

Your email address will not be published.