Partilhar via

MAPICDO May 2013 Update

  • Artigo

It;’s here! It’s finally here! The May 2013 update of MAPICDO is live here:

https://www.microsoft.com/en-us/download/details.aspx?id=39045

At that same link, you’ll also find the long awaited configuration guidance. It’s not immediately obvious it’s there. Just hit the Download link and it will be offered to you. As a reminder, this configuration guidance will help you in configuring an RPC/HTTP (aka ROH) profile using this MAPI/CDO download package. These instructions do NOT apply equally to Outlook’s implementation of MAPI. Attempting to use these guidelines to build a profile for Outlook’s MAPI, or attempting to “port” a profile between the two implementations WILL lead to failure.

Installation details:

  • This version is 6.5.8320.0. All of the files in the update are dated April 29th, 2013.
  • If you already have a version of the MAPI Download installed, you must uninstall it before installing the new version. The installer does not upgrade, nor does it warn you if you try to install it without uninstalling the previous version.

Fixes:

  • ROH now works when running under Local System context
  • Proxy server settings are no longer case sensitive.
  • PR_PROFILE_RPC_PROXY_SERVER can now be set using Unicode.
  • Improved support for mixed 2010/2013 environments.

Enjoy!

Comments

  • Anonymous
    June 04, 2013
    Stephen, Why does MFCMAPI work on an Exchange 2013 installed on a Windows 2012 which is also (the only) domain controller, simply by using the CONNECT_IGNORE_NO_PF, without needing to make any change documented in the guidance? Thank you.

  • Anonymous
    June 04, 2013
    The comment has been removed

  • Anonymous
    June 04, 2013
    The comment has been removed

  • Anonymous
    June 04, 2013
    You might try getting Outlook to work first, or try testconnectivity.microsoft.com to test your autodiscover configuration. Needless to say, you'll need Autodiscover working properly before you try working on MAPICDO.

  • Anonymous
    June 04, 2013
    The comment has been removed

  • Anonymous
    June 04, 2013
    You should probably look at blogs.msdn.com/.../creating-exchange-2013-profiles-using-mfcmapi.aspx, where I point to two articles that give practical guidance on building these profiles by hand for testing with MFCMAPI. I'd recommend getting that working before attempting to build the profiles programmatically.

  • Anonymous
    June 04, 2013
    Why was it decided not to completely copy Outlook's MAPI?

  • Anonymous
    June 04, 2013
    I don't know how to respond to that. If you want to use Outlook's MAPI, you can install Outlook. MAPICDO is Exchange's MAPI.

  • Anonymous
    June 05, 2013
    I am talking about Exchange MAPI copying Outlook MAPI RPC/HTTP implementation.

  • Anonymous
    June 05, 2013
    Ah - I wasn't involved in the development of Exchange's implementation of RPC/HTTP.

  • Anonymous
    September 09, 2013
    Hello, good morning everyone. Help, help... :-) Problem: BES Express 5.0.4 cannot pass through MapiCDO check step. MapiCDO version 6.5.8320 Exchange 2013 version 712.24 (Exchange 2013 CU2) Some infos from the BES Express install logs:

  1. CExchangeServer::GetExtendedInformation received unexpected version [Version 15.0 (Build 30712.24)]
  2. CExchangeServer::GetExtendedInformation result is [1] - Name:S2013-EXCH,Version:0/0(Version 15.0 (Build 30712.24)),ADFor[ourdomain.local],GC[Name[s2013-ad...
  3. CMAPICon::EditMapiProfile (no UI) sent [BlackBerryServer/S2013-EXCH/besadmin@semper.ch] and return code was [0x80040115] Question : do you know if there is any workaround ? or a newer MapiCDO version ? or anything else that will work ;-) Many thanks and best regards, jb_2000

  • Anonymous
    September 09, 2013
    You should raise this issue with Blackberry.

  • Anonymous
    December 11, 2013
    We keep hearing rumors that Microsoft is going to stop supporting MAPI/CDO.  Any plans for when this goes away?