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 contact 2) 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 Microsoft Outlook object model, you can access information that is stored in various address books. For example, you can retrieve information about entries in

In previous versions of Exchange, the System Attendant (SA) Mailbox was used by the link monitoring service and for publishing Free / Busy information. However, this functionality is no longer needed in Exchange 2010. As such the mailbox has been removed. One catalyst to this change was the new High Availability (HA) features in Exchange 2010. Having the System Attendant mailbox on servers presents a problem when the server needs to failover to the passive mailboxdatabase copy. Since only one SA

While working with one of my customer we noticed that the yearly recurring appointment doesn’t show in Outlook Web Access or Exchange Web Services(EWS) application. Customer created a monthly or yearly recurring appointment. He set the request to occur on the second, third, or fourth weekday of a month. But, whenever we use Outlook Web Access (OWA) client or customer’s Exchange Web Service (EWS) application to view this request, the request is set to occur on the first weekday of the month; but strangely,

On 7/17/2009, Microsoft released Update Rollup 9 for Exchange Server 2007 Service Pack 1. This update Rollup 9 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers. This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM). For a list of update rollups applicable to Exchange Server 2007 RTM, refer to

Now, you can download Microsoft Office Suite Service Pack 2 which provides the latest updates to the 2007 Office Suite. It consists of, Previously unreleased fixes that were made specifically for this service pack. In addition to general product fixes, this includes improvements in stability, performance, and security. You can find out more information in Knowledge Base Article 953195 , where product-specific changes are described. All of the Public Updates, Security Updates, Cumulative Updates,

One of my customer had created an Outlook Add-in using VSTO & Outlook Object Model (OOM). As per the business logic, he need to implement the WebViewURL in it. The MAPIFolder.WebViewURL works fine and take’s us to set value to it most of the times, but it doesn’t function as expected in some time; the strange thing is it’s not throwing any error or exception when we execute the code. //[Code Snippet : C# , VSTO, Outlook Object Model (OOM)] ... //Provide the non-default store path String pstPath

…I recently submitted the following KB article for publication but wanted to get the content out.  I will update this post when the KB article is published… SYMPTOMS Scenario 1 When you submit an Exchange Web Services request to Microsoft Exchange Server 2007 that contains invalid XML characters, you may get the following ErrorSchemaValidation exception response: “The request failed schema validation: [character], hexadecimal value [value], is an invalid character.” Scenario 2 When you submit

Per the support KB , Microsoft PSS has the support policy for customization of Outlook Web Access for Exchange that cover its versions like 5.5, 2000 & 2003. Per the article, we can get more information regarding the support policy for OWA customization for its various versions like, “…The Exchange 5.5 version of OWA is made up of Active Server Pages (ASPs). The Exchange 2000 and Exchange 2003 versions of OWA are composed of two main components: templates and controls. Templates are served from

My customer has CDOEX based legacy application which pulls the calendar and appointment items. Later they had merged their Exchange Server 2003 SP2 along with Exchange Server 2007 SP1 – mixed mode environment. He had an unique issue, whenever he tries to access couple of appointments created in Exchange Server 2007 environment, his CDOEX application throws the error : 8004011B: Unknown Error which means MAPI_E_CORRUPT_DATA. When we started troubleshooting we found that those appointments were created

One of my customer reported that when he tried renaming the default folder using VBA & Outlook Object Model (OOM) for Outlook 2003, he received the following error: “ You don't have appropriate permission to perform this operation .” As the Outlook 2003 object model was intentionally changed so that you cannot rename default folders, we recommended the customer to make use of Collaboration Data Object library (CDO 1.21) & requested to do the changes per the Knowledge base article .