From time to time, I get asked to explain where CDO publishes Free Busy information in the Public Folder store, so I figured I’d put this article together. The basic process CDO uses for updating FB information is outlined in the More Information section of KB 278954 . We’re concerned with the part of the process summarized as “queued up to be sent to the site’s Free/Busy public folder.” The first thing CDO does is to open the Public Folder store and read a couple properties off of it, PR_FREE_BUSY_FOR_LOCAL_SITE_ENTRYID

Recently one of my customer updated that they get an different issue with their ASP application. This application running on their Web server that uses MAPI to read the Contacts folder in the Public Folders from Exchange Server 2003 SP2 machine. The user can retrieve his email in outlook and browse the public folders as he is used to, but when this user want to use the ASP page that reads the public folder he fails. Customer receives the following error: bstrPublicRootID = objInfoStore.Fields.Item(&H66310102).Value

My colleague Edwin, writing for the Exchange Support Team Central Europe blog , posted an article on accepting meeting requests with CDO . The key takeaway from the post is this: This means that when calling the respond method on meeting updates / requests, the sequence number must be read from the request and written to the response, otherwise Outlook will not be able to match the response to the original meeting. (The proposed solution is to read the dispidApptSequence from the original message

Suppose you’ve scheduled an meeting and sent out meeting requests to a number of recipients. Some of those recipients don’t like the time you’ve scheduled for the meeting and decide to propose a new time . At this point, you will receive a message with message class "IPM.Schedule.Meeting.Resp.Tent". This message will contain information about the proposed new time, which Outlook will then tag on to the meeting when it processes the response. Now – suppose you also have some CDO based code

This is an issue that has only been reproduced so far with Exchange 2003 , but I wanted to document it here in case anyone else is running in to it. Suppose you have a CDO 1.21 based application which uses GetAssociatedAppointment to accept meeting requests. Suppose further that this application receives and processes a meeting request that contains an embedded message. The resulting appointment item created on the calendar will have an attachment on it, but this attachment will be unusable. What’s

Ever copied a DLL from one system to another and registered it using RegSvr32.exe? or in other words ever created a DLL hell situation? Its easy and dirty at the same time to copy-paste DLL between systems and register them using regsvr32.exe Often you copy-paste, register DLL from temporary folders or may be desktop and then later delete the DLL or move to other folder without unregistering/re-registering it. Stop right there!!! You are creating a problem for yourself. Every time you register a

Working with a customer the other day, I went looking for my blog post discussing the fact that MAPI is not supported with .Net. Turns out, while I’ve mentioned it several times, I’ve never devoted a topic to it. So here goes. Here are the articles which outlines our official support policies for MAPI and .Net, from both the Exchange and Outlook perspectives: Support policy for Microsoft Exchange APIs with the .NET Framework applications Support policy for Outlook APIs that are used in the .NET Framework

We had a customer who used CDO to create appointments and send meeting requests. Since they were operating in Europe, it wasn’t unusual for these items to have the E uro symbol (€) in the body of a meeting. When they would send the appointment, if the recipient was on Exchange 2007, all the Euro symbols would get replace with question marks. What was happening? When you call .Send on an appointment using CDO, CDO builds a new meeting request message. It copied PR_BODY from the source appointment

With continuation to previous blog post , this article describes how to access items in a WebDAV application that are identified by using MAPI. The WebDAV application uses flat URLs to access items or folders. How to use flat URLs to access items by using MAPI ? Read property tag 0x670E001E by using MAPI on the folder or item to access. Save the returned value in a variable. The value will resemble the following: /-FlatUrlSpace-/ca09cf9efaad754e8a85909b04bb255c-12ee443 Construct a URL that is used

CDOEX is a superset of CDOSYS; this means that CDOEX contains all of the functionality of CDOSYS, plus additional functionality for use with Microsoft Exchange Server 2000. When CDOEX is installed on a computer, it takes over the functionality that was previously provided by CDOSYS. Any program that makes calls to CDOSYS will now call CDOEX instead. When CDOEX is installed (by installing Microsoft Exchange Server 2000, Microsoft Office XP, or other programs), the CDO for Windows 2000 reference is