none
Suddenly getting MAPI_E_NETWORK_ERROR or MAPI_E_CALL_FAILED when using Outlook MAPI instead of CDO MAPI Download RRS feed

  • Question

  • Hello everyone,

    I have a multithreaded MAPI application working well with the separate CDO Mapi Download. The unicode limitation in of this MAPI implementation (no Unicode MSG files possible) is a pain,  so we often use Outlook MAPI (2007-2013).

    This works fine most of the time, but:

    Some installations get MAPI_E_NETWORK_ERROR or MAPI_E_CALL_FAILED after some minutes of activity (lots of MAPI calls worked well seconds before). Switching Outlook Versions does not help, switching to CDO Mapi works fine but brings in the unicode problem.

    A real network error is not the problem, one time a MAPI_E_RECONNECTED error occured, after that a couple of MAPI_E_NETWORK_ERROR and MAPI_E_CALL_FAILED occured. This MAPI_E_RECONNECTED error pointed me to the following blog entry:

    http://blogs.msdn.com/b/stephen_griffin/archive/2012/02/27/what-is-mapi-e-reconnected.aspx

    I'm not sure if this could be the problem, but perhaps someone here has a good idea of what to do... (Except EWS)

    Best regards

    Thorsten


    Best Regards/Viele Grüße Thorsten

    Monday, August 4, 2014 2:13 PM

All replies

  • Hello Thorsten,

    Do you use the cached exchange mode? Do you have the latest updates installed for Outlook/Office?

    Do you get the same results with a single thread? Or is it specific to the secondary threads only?

    Most probably you are aware that CDO is not supported any longer. See Collaboration Data Objects (CDO) 1.2.1 is not supported with Outlook 2010 and later versions .

    Monday, August 4, 2014 2:51 PM
  • Hello Eugene,

    we block the cached mode (abort our process when cached mode configuration is detected). We tried with several Outlook Versions and several Servicepacks of Office/Outlook without success.

    Our application is not able to run with one thread, because the whole architecture is multithreaded.

    CDO is not used at all, we use the MAPICDO http://www.microsoft.com/en-us/download/details.aspx?id=42040 Package.

    Best regards

    Thorsten


    Best Regards/Viele Grüße Thorsten

    Monday, August 4, 2014 3:36 PM
  • Which MAPI calls return that error?

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Monday, August 4, 2014 4:44 PM
  • Hello Dmitry,

    HrGetOneProp, LPMAPIPROP->SaveChanges and some other calls return MAPI_E_NETWORK_ERROR 

    HrGetOneProp, LPMAPICONTAINER->OpenEntry and some other calls return MAPI_E_CALL_FAILED

    I can't exactly identify the "other calls" in the moment... because some functions are encapsulated in an own library which has poor logging capabilities.

    Best regards

    Thorsten


    Best Regards/Viele Grüße Thorsten

    Tuesday, August 5, 2014 6:45 AM
  • Do you get this problem in all versions of Outlook? Latest versions should be able to reconnect...

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Tuesday, August 5, 2014 9:10 PM
  • Hello Dmitry,
    yes, we get the problem with all Outlook Versions and with Exchange 2007 and 2010, probably with Exchange 2013, too. (Remember we don't start Outlook, we just use MAPI when Outlook is installed).
    Is "reconnect" coupled to any flags when starting a Mapi session?

    Best regards
    Thorsten


    Best Regards/Viele Grüße Thorsten

    Wednesday, August 6, 2014 6:00 AM