Category: (100) Event ID: 1000 Date: Date Time: Time User: N/A Computer: Computer_Name Description

Timers & Events: Whenever we talk about the event sink and we plan to implement the event sink that should trigger within a specified time or interval, then we will go for onTimer Event sink. Basically Timers have scope, in the same way as other events. With timers, however, no event occurs in that location to cause the specified event to occur (such as a save event or a delete event). Note Scope does define a specific location for the registration event item, which can affect the security context

I tried to compose the test and troubleshooting tools for various exchange technologies. This initial list upto Exchange Server 2003. Technology Tools for test and troubleshooting tools Active Directory Services Interfaces (ADSI) All standard test and debugging tools, as well as other Microsoft and third-party test and debugging tools, can be used. Collaboration Data Objects for Windows 2000 (CDOSYS) No special debugging tools are needed to debug applications that use CDOSYS. CDOSYS SMTP/NNTP Event

When you migrated from Microsoft Exchange 2000 & 2003, where they provide several API's that are not included in Microsoft Exchange Server 2007. Please find the following API's that are not included in the Exchange Server 2007 environment & the recommended technologies to migrate to. APIs that are not included in Exchange 2007 API Status in Exchange 2007 Replacement Technology CDOEX De-emphasized but still supported. Exchange Web Services CDOEXM Not included in Exchange 2007. Microsoft Windows

Not getting all the properties you would expect from an WebDAV ALLPROPS or from an Event sink? Well, it could be that the Exchange schema is broken. The Problem: If you find that your application is no longer retrieving a full list of properties, it may be due to a broken Exchange Web Store Schema. Cause: This is a state where the schema is broken, and can happen due to a variety of causes; such as failed extension of the schema from an application installation or incorrect schema modification of

With messaging APIs, you can retrieve a list of properties dynamicly or by specific property name. For example with WebDAV, ALLPROPS will return a set of properties on a item. There are issues with trying to get a full list of properties. First of all, ALLPROPS does not equate to all properties. In fact, you will only get a set of properties back and its not going to be nearly all of them. Whats going on? Well, lets break this down... Actually, lets cover more important things before explaining why.

Using WebDAV to read BCC information on messages (even in the Drafts folder) will not work. The “urn:schemas:mailheader:bcc” will not return the BCC information using WebDAV - this is expected behavior. If you do a GET against the message to get the MIME, then you will also not get the BCC - this also expected behavior. You will find similar limitations with Exoledb and CDOEX. Extended MAPI can get to the BCC, however BCC information gets stripped when the message hits transport (ie the message is

I came across a tricy situation. One of the customer got the (422) Unprocessable Entity using WebDAV Error, when he tries to access Exchange Server 2007 for the query "SELECT “DAV:displayname” FROM “Inbox” WHERE CONTAINS(*, '"Mike"')"...he is referring that "Use an asterisk (*) to include all properties marked for full-text indexing". The request for working fine for Exchange Server 2003, but its not working on Exchange Server 2007. Found full-text indexing is enabled. Requests without CONTAINS predicate

Want to get creator, lastmodifier, and other security info for an item in an event sink? You can extract a considerable amount of security information using the http://schemas.microsoft.com/exchange/security/ namespace. The information returned is in XML, so individual elements need to be extracted from the XML. The following vb function is an example that shows how to get security information. '----------------------------------------------------------------------------------- 'GetItemSecurityInfo

' TODO: ' Create a C# Winform app ' Reference to Microsoft CDO for Exchange 2000 Server Library (COM) - this ' will add a reference to ADO automaticlly. ' NOTE: Do not add a reference to ADO or ADO.NET - this will cause interferance ' with CDOEX/CDOSYS (which you may not see until processing body parts). ' NOTE: ADO.NET is not supported working against CDOEX or CDOSYS. ' Add a button. ' Replace the button click event code with the code below ' This code will loop through the appointment.bodypart.bodyparts