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

Smile

28 COMMENTS

Seba October 14, 2013 At 2:32 pm

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

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

- Satheshwaran Manoharan October 17, 2013 At 2:56 am
  
  Happy with it . Thanks for sharing your solution Seba
  
Hiren Bhavsar October 31, 2013 At 10:40 am

Thanks for this post, its realy worked.

- Satheshwaran Manoharan November 23, 2013 At 1:49 pm
  
  Thanks Hiren
  
- Satheshwaran Manoharan November 23, 2013 At 1:49 pm
  
  Welcome 🙂 Hiren
  
Alejandro Mateo December 2, 2013 At 1:26 pm

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

- Satheshwaran Manoharan December 8, 2013 At 2:44 pm
  
  You are most welcome
  
ch_15 February 24, 2014 At 8:08 pm

Thank you for slution

Han April 7, 2014 At 12:08 pm

Thanks, you just saved my day! 😉

- Satheshwaran Manoharan April 18, 2014 At 4:26 am
  
  You are most welcome 🙂 Han
  
Joshua July 8, 2014 At 6:10 pm

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.

abc November 7, 2014 At 5:56 pm

Thanks bro that really work for it.

ShhhItsASecret December 31, 2014 At 4:26 pm

You da Man-oharan!

Transmo February 6, 2015 At 9:04 pm

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

- Satheshwaran Manoharan March 8, 2015 At 1:06 pm
  
  Thank you for your comments !
  
  - Samarasiri March 31, 2015 At 9:45 am
    
    it doesn’t matter user is disabled in AD. worked for me with same.
    
Samarasiri March 31, 2015 At 9:43 am

Thanks much

- Satheshwaran Manoharan May 12, 2015 At 6:08 am
  
  Your Welcome !!
  
pavani July 10, 2015 At 4:11 am

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?

Mike September 25, 2015 At 1:41 pm

This worked for me…thanks for the solution.

- Satheshwaran Manoharan September 27, 2015 At 5:12 am
  
  Happy for you
  
Cyril Thomas February 5, 2016 At 11:28 am

Thanks the issue is resolved….

thank you April 27, 2016 At 3:32 am

hi Sir

thank you and keep posting good stuff like this

James August 8, 2016 At 10:26 pm

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

NolaRMeise August 15, 2016 At 11:15 pm

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.

pepito August 17, 2018 At 4:50 pm

I love you, thanks, ME ESTABA VOLVIENDO LOCO

gracias!!

- Satheshwaran Manoharan October 11, 2018 At 12:21 pm
  
  your welcome !
  
priyam October 28, 2020 At 10:09 am

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?