Just yesterday, I found this to be my problem. Exchange Event Service/Server
scripting works fine.
1) We deinstalled and reinstalled the Exchange Event Service. It had become
"tangled" through all our experimentation.
2) Our script was invoking some custom-built COM objects that were NOT using
the apartment threading model as required by Exchange Server Scripting
environment. Once we corrected our build process to properly build these COM
objects, the server scripts ran OK.
Here is a checklist of things I compiled during problem analysis. I got them
from the Microsoft Press textbook, Programming Exchange and Outlook by
1) increase logging level of Exchange Event Service and then check NT Event
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeES\Parameter Jamie Jones
keyname is LoggingLevel (DWORD) which can be 0-5. 5 is most verbose.
2) insure that domain/userid account has Log on As Service privilege. (pg
3) Server scipts are logged on with identity of most recent author that
copied script to the server. Insure that we were logged on as
MYDOMAIN\MYUSERID when running Outlook to install pixExchScript.txt
4) Are our custom COM objects apartment-threaded as required?
5) Deinstall and reinstall the Exchange Event Service.