Le Café Central de

                 ... Deva blogs!!

  • Le Café Central de DeVa

    Monitoring event sink # 22 - Store Event sink registered with Outbox or Sent item folders won’t fire


    Have you register an Exchange 2000 store event sink globally on the mailbox store, the sink fires for the appropriate events (OnSyncSave, for example) for all folders in a mailbox. However, the sink does not fire for events in the Outbox or the Sent Items Folder?

    For example, when a user sends an e-mail, it appears in the Outbox folder for a brief time.

    Outbox: This is due to Even if an event sink is registered directly on the Outbox, it will not fire.

    The Outbox is a temporary home for a new message while it waits to be picked up by the MAPI spooler. When the message appears in this folder, it does not generate an OnSave or OnSyncSave event. Also, when the message disappears from the folder, it does not generate an OnDelete or OnSyncDelete event.

    Sent Items:
    Messages are moved to the Sent Items folder after being sent by the MAPI client in such a way that events are not generated, and this behavior is by design. The appropriate events are generated if you manually move items into the Sent Items folder.

    Please find the following KB article, which provides resolution.

  • Le Café Central de DeVa

    Monitoring event sink # 21 - Exchange Server 2007 & Store Event sink registration


    One of my customer developed with a store event sink (onsave;ondelete) in x64bit Exchange 2007 server. He want to know in which server role that we need to register the   event sink along with COM+ application?

    Yep, that's true. As you know in Exchange Server 2007 it has various server roles like hub, transport, edge etc.

    The EventSink needs to be installed on the mailbox server role of the Exchange Server.

  • Le Café Central de DeVa

    Some countries / regions not listed in Outlook contact address list ?


    In the Contact form of Microsoft Outlook, the country that you want to use may not be listed in the Country/Region field list.

    Please find the following Support KB which provides the resolution for this issue.

  • Le Café Central de DeVa

    Outlook 2003 & Performance Counter objects


    Please find the following Support KB describes the performance counter objects that are included in Microsoft Office Outlook 2003.

    These performance counter objects can be used like any other counter object in Performance Monitor.

  • Le Café Central de DeVa

    Issue while searching full user name with address book ?


    If you type a full user name in the Display Name field in the Find dialog box of your address book when you try to search a Lightweight Directory Access Protocol (LDAP) server in Outlook 2002/2003, you may receive the following error messages:

    Unable to display results because too many entries in the Internet Directory match your search criteria.


    The search could not be completed. MAPI_E_CALL_FAILED.


    Cannot contact the LDAP server (81) error.

    Please find the following Support kb which gives resolution for Outlook 2002 and Outlook 2003.

  • Le Café Central de DeVa

    Your system is low on virtual memory?


    Couple of customers reported that he face a strange error with Outlook 2007/2003:

    When you start any of the Microsoft Office 2007 or Microsoft Office 2003 programs, you may receive an error message that is similar to the following error message:

    Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

    If you click OK, you may receive the following error message:

    Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.

    This behavior may occur if you try to start any of the programs included in Office on a computer where the paging file value setting is too low.

    To get resolution, please find the following Microsoft Support KB, which provides resolution for the issue.

  • Le Café Central de DeVa

    Can’t connect via Internet to Exchange Server 2003 from Outlook 2003/2007?


    When you try to use Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003 to connect over the Internet to your mailbox on a Microsoft Exchange Server 2003 based-computer, you are prompted for your logon credentials many times, and you do not connect to Exchange Server 2003.

    It may be the issue with regards to Remote procedure call (RPC). Please find the following Microsoft Support KB article which provides what is the issue all about and its resolution.

  • Le Café Central de DeVa

    Nutshell: CDO 1.21 not supported in .Net environment


    Per the Microsoft support policy specified in the following KB, CDO 1.21 is not supported in a .NET Framework environment.

    Instead it recommends, to make use one of the following technologies to build the .NET Framework application, the supported options for accessing Exchange data are:

    • WebDAV

    • CDO for Exchange 2000 Server (CDOEX) and  ExOLEDB through an interop assembly.

    • Windows Management Instrumentation (WMI).

    • Collaboration Data Objects for Exchange Management (CDOEXM)

    Many of the messaging developers asked us the question, why it’s not supported under the .Net environment. With regards to the issue, please find the detailed article by Mstehle.

    Also find the one more related article where many messaging professionals gets confused what does “unsupported” mean? by pcreehan.

  • Le Café Central de DeVa

    Exchange System Manager (Exchange Server 2003) for Vista - Now Available


    Microsoft has released the new version of Exchange System Manager for Exchange Server 2003 running on the Windows Vista operating system.

    You can download it from here.

  • Le Café Central de DeVa

    Visual Basic code with Simple MAPI Functions may Not Work or fail with an error


    If the Microsoft Visual Basic code calls the MAPISendMail function, it may fail with an error message that resembles the following:

    Microsoft Outlook
    Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client.

    This problem often occurs when Microsoft Outlook Express is set as the default mail client.

    Please find the support KB which has detailed information, resolution for that.

  • Le Café Central de DeVa

    .NET Framework 3.5 SP1 Allows managed code to be launched from a network share ?


    Do you know, that using .NET Framework 3.5 SP1 hereafter we can launch our managed code from a network share.

    I read this wonderful blog posted by Vance Morrison, who is an Architect for .Net runtime team. Certainly i believe this will relive lot of deployment related pain specially...

  • Le Café Central de DeVa

    How to get messages contained in Message or IBodypart objects using CDO?


    Please find the VBScript code-snippet to get or extract the messages that are contained in the other objects like Message or IBodyPart.


       1:  ' Please provide the value for sVal  
       2:  Function getMsg(sVal As IBodyPart) As Message
       3:      Dim Msg
       4:      Set Msg = CreateObject("CDO.Message")
       5:      Dim getVal
       6:      Set getVal = Msg.DataSource
       7:      getVal.OpenObject sVal, "IBodyPart"
       8:      Set getMsg = Msg
       9:  End Function
  • Le Café Central de DeVa

    Public folder support for Exchange Server 2007 till 2016 ?


    I went through the following Technet article which talks about one such a interesting question of my favortie "What is happening with public folders ?"

    Please find the excerpts "...Exchange 2007 de-emphasizes public folders. Public folders may not be included in future releases, but support for public folders will be maintained through at least 2016. Current Microsoft Exchange customers should plan to migrate to Outlook 2007 and Exchange 2007. We recommend that you investigate integrating Microsoft Windows SharePoint Services with Exchange Server 2007 if you must have an application that supports sharing documents, calendar items, contacts, and tasks and archiving distribution lists. For other customized applications that are being developed, you should use Microsoft .NET .."

    For more information, you can have a look at this Technet article.

  • Le Café Central de DeVa

    Microsoft Online Services & Exchange Online


    Microsoft Online Services, this is targeted for Microsoft partners. It helps partners to closely work with Microsoft, deliver rich and satisfying customer experiences, whether on-premise or hosted.

    By using Microsoft Online Services, partners are able to more simply develop and deliver custom fit solutions that help businesses to realize their full potential.

    For more information, you can click here to get more details.

    Exchange Online, this is a hosted enterprise messaging solution based on Microsoft Exchange Server 2007. It extends rich capabilities to your users with a single sign-on, including e-mail, shared calendaring, and contacts etc, along with business continuity and disaster recovery with cloud-based antivirus and spam filtering and high data center security standards.

    Click here to view the demo or either you can  for 30 day trial.


  • Le Café Central de DeVa

    Outlook VSTO add-in won't run when you use Outlook view control from Web page?


    Do you know that when you use the Microsoft Outlook View Control from a Web page, Microsoft Visual Studio Tools for the Microsoft Office System (VSTO) Outlook add-ins do not run.

    This issue may occur even by this option: The Outlook View Control is not considered a part of the Outlook user interface. Therefore, the VSTO add-ins do not load correctly.

    For more detailed information, please go through the following KB article.

  • Le Café Central de DeVa

    Programming technology options for you with Exchange Server 2003



    Please find the following MSDN article, which describes, the list of programming technologies, that can be helpful to apply in Exchange Collaborative applications.

    Some of the of technologies available: ADO, ADSI, CDO, EXOLEDB, LDAP, MAPI, Schema, Search, Store Events, WebDAV, Webforms, WMI Providers.


    ActiveX Data Objects (ADO) are used to navigate through Web Storage System. ADO allows the developer to access all Microsoft Database APIs, as well as search for and bind objects. ADO contains built-in objects that the developer can use to add features to the application. This permits developers to add dynamic objects to a static Web page.


    ADSI is a standard Windows-based interface for meta-directory applications. A meta-directory is a high-level network directory service designed to unite account and resource information from multiple network operating environments. The goal of ADSI is to synchronize this information across differing directories. Meta-directories extract security and account data from each directory, and then manage this information as part of an external database.

    ADSI is comprised of a series of client-side DLLs that provide a common set of directory management functions. You can access these functions from almost any environment. As a result, you can add or remove user accounts, configure shared resources, and browse the directory tree all from a single, integrated console. Exchange 2000 uses ADSI to integrate application services with Active Directory's security and account functions. You can also access ADSI using Microsoft Visual Basic, Scripting Edition (VBScript) and Microsoft Windows Script Host to perform directory maintenance tasks.


    Collaboration Data Objects (CDO) was originally called "OLE Messaging" and later "Active Messaging". CDO is a COM wrapper of the MAPI library and can be called from any development language that supports automation. For example, Simple MAPI, CDO is primarily designed for client activities. CDO implements most but not all MAPI functionality, although far more than Simple MAPI.

    Some activities that can be accomplished using CDO:

    • Log onto the messaging system with specific profiles or with anonymous authentication.

    • Compose messages, address and resolve recipients, send, receive, and read messages, add attachments, automate replies.

    • Manage calendars; create meetings and appointments.

    • Manage folders and messages within the information store.

    • Manage Addresses, especially within the Personal Address Book (PAB).


    This is a high performance OLE DB driver. The ExOLEDB provider is a server-side component, and is therefore used only to access public stores and mailbox stores that reside on the same server. You can, however, access data on the server remotely by wrapping functionality into Component Object Model (COM) components, which can be utilized by ASP and other Web applications. The ExOLEDB provider is also ideal for use in COM+ components and Exchange store event and workflow sinks that run on the server. To access remote public stores and mailbox stores, use the WebDAV protocol, MAPI, or CDO 1.2.1.


    The Lightweight Directory Access Protocol (LDAP) protocol is a distributed, hierarchical directory service protocol that you use to gain access to repositories of users and other network objects. Because LDAP is not typically tightly integrated with the host operating system, information can be kept in both LDAP and in a name service such as Network Information Service. When you use LDAP to gain access to the groups, you reduce redundancy and maximize LDAP's scalability.

    LDAP gives you the option of using paged or non-paged results when performing a search. With non-paged results, the maximum number of objects returned is limited by the MaxPageSize constraint on the domain server. With paged results, there is no maximum. You can return all the results. You set the LDAP client page size in the Search Options dialog box. This value cannot exceed the MaxPageSize constraint imposed by the domain server.


    MAPI will generally mean MAPI32.dll, or the APIs contained. It's an API, implemented largely in MAPI32.dll (Messaging Application Programming Interface, 32 bit build). By using this, developers implement a series of Providers. Providers come in three major types, Transport Providers, Message Store Providers, and Address Book Providers. Providers are DLLs that implement a specific pseudo COM API, such as IMessageStore, and the underlying required interfaces, such as IMAPIProp.


    The Exchange store provides a means to define schema information for items. By using the schema capabilities of the Exchange store, you can make schema information about your application discoverable to schema-aware applications such as the Exchange store Structured Query Language (SQL) query processor.


    You can search for items in the Exchange store using a familiar Structured Query Language (SQL) syntax, which is based on the syntax defined by the Microsoft Indexing Service Query Processor.

    Store Events:

    You can respond to events that occur in the Exchange store programmatically. With events, you can write your own custom logic that executes on the server in response to changes in the data in the Exchange store. Exchange store events occur:

    • When Exchange store items are saved, deleted, moved, copied, or modified.
    • When a store is started or shut down.
    • When a specific time interval has elapsed.
    • You can write event sinks that can receive notification of these events.


    The World Wide Web Distributed Authoring and Versioning (WebDAV) protocol provides access to an extensible set of associated properties. WebDAV also defines protocol commands used to search, move, copy, delete, lock and unlock resources, and make new collections of resources (folders).


    Exchange Web forms is a Web-based forms technology that is built on Internet standards. An Exchange Web form is a Web page that is registered in the form registry of the Exchange store.

    WMI Providers:

    Microsoft Windows Management Instrumentation (WMI) supports custom Exchange management and monitoring applications through a set of WMI providers.

  • Le Café Central de DeVa

    Known Issues : To be considered during creating Outlook related applications

    • Development : Outlook Object Model & Outlook 2007

    There are couple of known issues that may occur when you use the Microsoft Office Outlook 2007 object model. Please find the below given article, which talks about this.

    Known issues that may occur when you use the Outlook 2007 object model

    • Development : Form regions & Outlook 2007

    There are couple of known issues that may occur when you use the Form regions and Outlook 2007. Please find the below given article, which talks about this.

    Known issues with developing Office Outlook 2007 form regions

    • Development : Custom forms & Outlook 2007, Outlook 2003, Outlook 2002, Outlook 98 and 97

    There are couple of known issues that may occur when you use the custom forms that were created by using the following earlier versions of Microsoft Outlook. Please find the below given article, which talks about this.

    Known issues in Office Outlook 2007 when you use custom forms that were created by using earlier versions of Outlook

    Note: The scope of this article is limited to custom forms that you create by using the method with which you would typically publish a form in these earlier versions of Outlook. This article does not discuss custom forms that you create by using the new form region feature in Office Outlook 2007.

    • Development : Custom solution & Outlook 2007

    There are some of the known issues with the Outlook 2007 development platform. These issues include changes to command locations and changes to how Outlook displays COM add-ins. Additionally, this article discusses functionality changes in Outlook 2007. Please find the below given article, which are mentioned in this article are not directly related to the object model, to custom forms in Microsoft Office Outlook 2003 or in earlier versions of Outlook, or to the form regions in Outlook 2007.

    Known issues when you develop custom solutions for Office Outlook 2007

Page 1 of 1 (17 items)