Step-by-Step : Accessing Exchange mailbox using Exchange MAPI/CDO and MFCMAPI

One of my customer updated that he downloaded the MFCMAPIat his Exchange Server 2010/2013, when he ran he noticed the following error – he wanted to access the exchange mailbox programmatically. Then he noticed the following error as well: To start with he needs Exchange MAPICDO, as Microsoft Exchange MAPI and CDO 1.2.1 provide access…


Custom CDO app throws error CDO_E_FAILED_TO_CONNECT

Recently I was working with a customer (at his Windows XP) where his CDO app (CDOSEND.vbs – given below) is failing to send email and throws the error “CDO_E_FAILED_TO_CONNECT” (you can refer the below given Output also). We tried setting CONFIG parameters like user name, SLL, password – but it doesn’t help. Code Snippet: Option…


Migrated custom C++/CDOSYS app throws compiler errors

Recently I was working with one of the developer who earlier designed an CDOSYS based mail component in his C++ application built using earlier Visual Studio (2005) version . After migration to VS 2008 environment, they noticed compile errors with the same code/no changes made. When I debugged further and noticed that the msado15.tlh and…

2

Exchange throttling: MAPI application fails with error “The information store could not be opened. [MAPI 1.0 – [MAPI_E_LOGON_FAILED(80040111)]]”

We recently resolved a case where a customer tries accessing Exchange Server 2010 mailboxes (DAG) via their custom Exchange MAPICDO based application. On average 2-3 days once, they’re frequently facing an error “The information store could not be opened. [MAPI 1.0 – [MAPI_E_LOGON_FAILED(80040111)]]” while attempting to connect to Exchange server 2010. After some days of…


Outlook 2010: Migrating CDO based application to Outlook Object Model(OOM) library

Recently one of my developer customer migrated from Outlook 2003 to 2010. He tried running the custom application (uses CDO & Outlook 2003) in Outlook 2010. It throws the error “ActiveX component can’t create object”.  Using the following test sample, I can reproduce the exact issue at my end: As you know, Microsoft Outlook 2010…

5

Download: CDO 1.21 (Ver # 6.5.8211.0)

As you know using CDO 1.2.1 (Collaboration Data Objects, version 1.2.1), a package providing access to Outlook-compatible objects through a COM-based API. Using CDO, a program can connect to a MAPI store, and then perform operations against that store, including creating and processing calendar items, and resolving and handling mail recipients. Starting with Exchange Server…


"MAPI_E_FAILONEPROVIDER" when you try to connect to a mailbox on an Exchange 2010 from an Exchange 2003 server

Recently one of my customer updated that when he tried connecting to a mailbox that is located on a  Exchange Server 2010 from Exchange Server 2003 by using a custom MAPI/C++ application. But it failed and it thrown the following error message: “MAPI_E_FAILONEPROVIDER”. As part of troubleshooting the issue, we tried using MFC MAPI utility…


Part 1 : Developer Roadmap – Development Technologies for Exchange Server 2010

This two part article is targeted for the developer audience, if you’re the developer who want to create a develop custom application for Exchange Server 2010 or already has custom application designed for previous versions of Exchange Server 2010. Some Exchange programming technologies that are available in versions of Exchange earlier than Microsoft Exchange Server…

1

KB : Outlook Object Model (OOM) limitations

I found this knowledge base article which talks about known limitation you may encounter with the Microsoft Outlook Object model. I found this interesting excerpt, “…unlike other Microsoft Office programs that have “full” object models, such as Microsoft Word and Microsoft Excel, the Outlook object model primarily focuses on items and the folders in which…


Monitoring Event Sink # 32 – Best Practices: Performance related issues with Event sinks

I would like to share certain best practices – in order to improve the performance or overcome performance related issues associated with event sink and Programming guidelines for event sinks before you develop for your reference. Exchange store events do not by themselves generate Windows Event Log entries. The underlying ExOLEDB provider generates performance counters…


Outlook 2010 : Why CDO 1.2.1 not supported with Outlook 2010?

Collaboration Data Objects (CDO) 1.2.1 is a client library that provides a thin wrapper over Extended MAPI functionality. CDO does not install with Outlook 2010, and is available only as a download. For more information, see Collaboration Data Objects, version 1.2.1 in the Microsoft Download Center. CDO is not guaranteed to work correctly in an…

5

Update : Technologies not available with Exchange 2010 & their migration reference(s)

Some development technologies that shipped/available in earlier versions of Exchange Server are not included in Exchange 2010. The following technologies were removed from Exchange 2007: Exchange providers for Windows Management Instrumentation (WMI) Collaboration Data Objects for Exchange Management (CDOEXM) Collaboration Data Objects for Exchange Workflow (CDOWF) Exchange Web Forms At Functions DAPI.DLL The following technologies…


Outlook Object Model : How to programmatically get logged-in user’s CompanyName in Outlook 2003/2007?

Recently one of my customer updated that they have a requirement to implement the following logic: 1) Get Contact info from GAL or Address book for the specified contact2) Get Contact information regarding his CompanyName etc. In the scenario, i provided the following suggestions: If you try Outlook 2003 & its prior versions: Using the…