Tips on Using Microsoft Exchange Server Event Service

Limitations of Script.Response Property

Liberal use of the Script.Response property is the only way to debug agent scripts. However, it can only be invoked from within the scope of the four server-side events, Folder_OnMessageCreated, Folder_OnMessageDeleted, Message_OnChange, and Folder_OnTimer. You cannot set this property from within any other function. For example, if the Folder_OnMessageCreated function makes a call to the user-defined function GetMessage, Script.Response will not work from within the new function. To read more about how the BDG developers worked around this limitation, see About the DebugReport Subroutine in the Implementation section.

Increasing the Notification Frequency of the Event Service

The notification interval determines the amount of time the Microsoft Exchange Event Service waits before checking folders for changes. The default interval is 5 minutes (or 600 seconds). This value can be decreased for demonstration or testing purposes. Note that in a production environment it is not necessarily a good idea to lower this trigger, because it can negatively impact the performance of the server.

To increase the notification frequency to 30 seconds

Increasing Windows NT Event Log Error Detail

Like other Exchange system services, the Microsoft Exchange Event Service offers a varying degree of Windows NT Event Log error detail. The value defaults to zero (0), but can be as high as five (5).

To set the maximum logging level

Changing the Maximum Size of Agent Logs

The Event Service automatically truncates agent log files after they exceed the maximum size, default 32 KB.

To modify the maximum log file length for agents