Exchange Server

Guest · Posted: Tue Nov 01, 2005 1:58 am Post subject: event sink diagnostic logging

I'm trying to develop some some simple mailbox processing scripts
(.vbs) that are fired during the OnSave event.

The event registers with no problem (using regevent.vbs), and things
*seem* ready to go, but the event never fires (according to the log
file debugging in my script).

No errors show up in the event log, and I don't know how to procede in
diagnosing the problem.

How can I determine if exchange is trying to fire the event? I'm
assuming there are some verbose logging options to help me track down
the problem....?

I'm using Exchange 2003 on Windows Server 2003.

Thank

Glen Scales [MVP] · Guest

There is no logging specific to Exoledb Event sinks that you can enable you
can turn up the diagnostic logging on your store which will help you see
what's going on with your store (eg who's logging on what rules are
running). The place to start diagnosing a script event problem is with the
Exoledb Script host object check the user account this is set to run under
has rights for the mailbox the sink is to run on. Make sure that "Enforce
access checks for this application" is not enabled. This is a little old
but still has a few other things you might want to check
http://www.outlookexchange.com/articles/glenscales/shesdat.asp. You might
also want to post the code your using .

Cheers
Glen

<forge1968@yahoo.com> wrote in message
news:1130795916.150614.135450@o13g2000cwo.googlegroups.com...

Guest · Posted: Tue Nov 01, 2005 5:58 pm Post subject: Re: event sink diagnostic logging

I tried one of the things mentioned in the article. I dumped the
contents of the code that's stored in my inbox. Things look correct,
and I don't get any errors when the script is registered, but nothing
is ever written into my debug file.

I'm logged in locally to the server using my personal account (which is
the mailbox owner) and I'm registering my script there.

thread-index: AcXfBqGYVjjIiyISQCmNFeMIilYl5g==
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830

' DESCRIPTION: This event is fired when a new message is added to the
folder
Sub ExStoreEvents_OnSave(pEventInfo, bstrURLItem, lFlags)

Dim fso
Dim wfile

Set fso = CreateObject("Scripting.FileSystemObject")
set wfile = fso.opentextfile("c:\tevent.txt",2,true)
wfile.write ("debug")
wfile.write (bstrURLItem)
wfile.close
set fso = nothing
set wfile = nothing

Exit Sub

</SCRIPT>

Guest · Posted: Wed Nov 02, 2005 1:58 am Post subject: Re: event sink diagnostic logging

Thanks! That problem's fixed, but I'm still not getting things to
work. No data is being written into my debug file.

There's still something I'm missing :-(

The file (and folder) I'm writing into have full permissions for the
test user account that I'm troubleshooting with.

Doesn't the event process only use that particular account and its
security credentials?

Glen Scales [MVP] · Guest

The code you posted has one error i can see you have used

Exit Sub

instead of

End Sub

This will cause a compile error which means you script wont run. If you want
to test for compile errors drop the <Script> tags from you code and try to
run it if you have no errors the script should run okay and exit. (just make
sure you add the scirpt tags back in before you register the sink)

Cheers
Glen

<forge1968@yahoo.com> wrote in message
news:1130865044.595371.308750@g43g2000cwa.googlegroups.com...

Glen Scales [MVP] · Guest

How are you registering the sink with regevent.vbs or Exchange Explorer. If
your using regevent.vbs to register your script, dont use a ".eml" ending
for the destination URL of you sink registration. Exchange has a tendency
to convert this into MIME content, which the script engine doesn't like. The
other thing you could try is if you are using Regevent.vbs try registering
the sink with Exchange Explorer to see if this makes a difference.

One of Exchange's dispatchers (which will be running as System) will start
up the Exoledb.host Com+ object which will then run under the context of the
account you have configured this is usually where most people fall down
because they use administrator accounts which are denied access to all
mailboxes other then their own. If you turn up security auditing on your
server you should see this account trying to be used.

Cheers
Glen

<forge1968@yahoo.com> wrote in message
news:1130890448.283003.6040@g47g2000cwa.googlegroups.com...

	Exchange Server Forum Index -> Development	All times are GMT
Page 1 of 1