Exchange 2013 MFCMAPI error

All replies

• 

  

  0

  Sign in to vote

  Hi,

  I don't think MFCMapi will work on Exchange 2013 as outlook client connect through SMTP, something new they have introduces in 2013, but I am not sure someone will connect me if I am wrong.

  Thanks,

  ---

  Ripu Daman Mina | MCSE 2003 & MCSA Messaging | MCC

  Tuesday, April 12, 2016 2:27 PM
• 

  

  0

  Sign in to vote

  Hi All.
  
  I have problem with connecting MFCMAPI to Exchange 2013 Mailbox server.
  

  My Envirement (Windows Server 2012 R2):
  2 x Exchange 2013 Mailbox Server (CU9 & CU12)
  2 x Exchange 2013 CAS Server (CU9 & CU12)
  On Mailbox Server i have MAPI/CDO vs. 6.5.8353
  MFCMAPI vs. 15.0.0.1043
  

  Services:

  Outlook connecting to Mailbox (RPC/HTTP)
  Outlook Anywhere connecting to Mailbox
  Autodiscover work fine
  Test-MAPIConnectivity Success
  mapi/healthcheck.htm 200 OK
  OrganizationConfig (MapiHttpEnabled: False)
  
  HealthSetName AlertValue
  ------------- ----------
  MailboxTransport Healthy
  OutlookMapiHttp.Protocol Healthy
  OutlookMapiHttp.Protocol Healthy
  AD Healthy
  AD Healthy
  OutlookMapiHttp.Proxy Healthy
  OutlookMapiHttp.Proxy Healthy
  OutlookMapiHttp.Proxy Healthy
  OutlookMapiHttp.Proxy Healthy
  Outlook.Protocol Healthy
  Outlook.Protocol Healthy
  Outlook.Protocol Healthy
  
  MFCMAPI error:
  MAPIInitialize failed with error 0x80004005 == MAPI_E_CALL_FAILED.
  Here are some known causes for this.
  ………
  In file MapiObjects.cpp
  On line 120
  
  The same error Was with all Exchange Server 2013 vs. CU9.
  Any sugestion where I can look for more information to resolve the problem?

  I've definitely used MFCMAPI with Exchange 2013 before.  Make sure your account has full access to the mailbox and you are creating the account based on this;:

  https://blogs.msdn.microsoft.com/dvespa/2013/05/21/how-to-use-mfcmapi-to-create-a-mapi-profile-to-connect-to-exchange-2013/

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  Tuesday, April 12, 2016 3:38 PM
• 

  

  0

  Sign in to vote

  I have 2 account with Full Privilages

  domain\username {Receive-As} {ExtendedRight}
  domain\username {Send-As} {ExtendedRight}

  With PowerShell tests permission pass positive

  I read this blog, but at the begining get error and can go forward
  Profile >> show profiles   MAPI_E_CALL_FAILED
  Profile >> Launch profile wizard MAPI_E_CALL_FAILED
  Session >> Logon MAPI_E_CALL_FAILED
  
  I tested reinstall MAPI/CDO, and 2 diferent version of MAPI/CDO and no luck.
  

  Wednesday, April 13, 2016 6:44 AM
• 

  

  0

  Sign in to vote

  Hi ITMMM,

  You can refer to the following blog and it may give you some hints :

  Outlook 2013 – MfcMapi Error – MAPIInitialize failed with error 0x80004005 == MAPI_E_CALL_FAILED.

  Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially by Microsoft.

  Best regards,

  ---

  Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

  Niko Cheng
  TechNet Community Support

  

  
  

  • Edited by Niko.Cheng Wednesday, April 13, 2016 8:23 AM
  • Proposed as answer by Niko.Cheng Friday, April 22, 2016 10:37 AM
  • Marked as answer by Niko.Cheng Saturday, April 23, 2016 8:14 AM

  Wednesday, April 13, 2016 8:23 AM