Thank you very much Glen...
I registered the OnSave event on the calendar folder and it works
perfectly fine... Thank you very much.
The script that I was using, used to register OnSave event on
file://./backofficestorage/PresenceServer1.com/MBX/purvi/testeventReg.eml
so if I register an event on the parent folder MBX/user, wouldn't it be
able to trap events on all the folders namely inbox, calendar.....
I just wanted to make my fundamentals clear about Exchange Server.....
Thank you very much Glen.... You have been a great help.
Best Regards,
Purvi Dholakia
"Glen Scales [MVP]" <gscales@outlookexchange.com> wrote in message
news:e7CYX9W4EHA.524@TK2MSFTNGP09.phx.gbl...
OnSave will fire for a calendar appointment, it fires when any item is
saved
to the store. If you want an event sink to fire when you create or save
calendar items then you need to make sure you register this event sink on
the calendar folder. The only two folders that an event sink wont fire on
is
sent items and the outbox
Cheers
Glen
"Microsoft LiveComm Developer" <mihir_a_vaidya@hotmail.com> wrote in
message
news:%23A2TG4V4EHA.3596@TK2MSFTNGP12.phx.gbl...
Hey Glen,
I have a new problem with the exchange server.
The OnSave event on the Exchange Server is raised only in cases of an
email
receipt. It is not generated when an appointment is saved to the
calendar.
I want to capture the condition where an appointment is saved/modified
to
the calendar.
Can you throw some light on this?
Thanking you in advance.
Best Regards,
Purvi Dholakia
"Glen Scales [MVP]" <gscales@outlookexchange.com> wrote in message
news:OjIyXlO3EHA.3336@TK2MSFTNGP11.phx.gbl...
You might want to have a read of the Exchange Server 2003 Technical
Reference Guide
http://www.microsoft.com/downloads/d...displaylang=en
its the best online reference to the architecture of Exchange. Tony
Redmond's book also does a very good job of explaining this. (It's lot
more
complicated then just a simple database store, The under-lying
structure
of
the Exchange databases are undocumented)
If your looking at it from a programmatic perspective the method you
use
to
access particular items will differ for each API. Eg if you use
Exoledb/ADO,
WebDAV or CDOEX then every item within each mailbox or pubic folder
store
is
accessible via a file or http URI, you can also search the Exchange
Store
(with some limitations) with SQL commands via these API's.
OnMDBStartUp is explained in the Exchange SDK which you can download
from
http://msdn.microsoft.com/exchange but it essentially fires when each
exchange mailbox or public folder store is mounted or dismounted.
These
are
completely independent of the rest of Exchange as you can have
multiple
mailbox/Public folder stores on Exchange with some mounted and some
dismounted. If you looking at firing an event on the server start-up
and
shutdown you maybe better of using WMI and fire it when one of the
Exchange
services (eg the information store) start-ups or shutdowns eg
http://www.microsoft.com/resources/d..._wmi_kzcp.mspx
or have a look at SVCMON from the Server Resource kit.
Cheers
Glen
"Microsoft LiveComm Developer" <mihir_a_vaidya@hotmail.com> wrote in
message
news:urYe64I3EHA.1124@tk2msftngp13.phx.gbl...
Hello All,
I wanted to know what exactly is an exchange store in exchange server
2003?
The way I know it is as a repository(store) where all the information
of
the
exchange server is stored. It is at a location that can be specified
by
some
URL. You can query the store to know information like the schedule of
a
person or accessing somebody's mailbox information.
Please tell me whether I am right or not.
The other thing that I wanted to know was - There are events and
event
sinks
in exchange server. One of the system events is OnMDBStartUp and
OnMDBShutDown - when are they exactly generated? Are they generated
when
the
exchange server starts or shuts down or they are related to the
exchange
store? I wanted to use these events and was wondering whether I can
use
them
for detecting startup and shutdown of exchange server.....
Thanks for any kind of help.
Best Regards,
Purvi