In a nutshell: use the ‘eventcreate‘

I had an issue with ITM Windows Agent creating events which I was then sending out email alerts via a UNIX script.

The simple problem was backslashes in windows paths where the “Take Action” notification script was literalizing characters which might be part of the EventLog Description

For example:

"c:\Damned these\nagging\slashes\argh"

became

c:\Damned these
agging\slashesrgh

Yes, simply quoting my string would have solved most of my problem, IT DID HOWEVER lead me to a handy windows command for testing, called ‘eventcreateid‘

Example : eventcreate /ID 101 /SO FooBar /D “Test Message for ITM” /T ERROR /L Application

I was experimenting with WAMP on my laptop, not a big deal in itself, but when I rebooted the Apache server failed to start.

Event logs showed something else had already been binded to port 80.

Quick Fix was to determine which PID had it by running the following:
netstat -ano
From there you can use task manager, determine the conflicting process, kill the PID.

(If you had CYGWIN installed)
netstat -ano | grep :80
ps -Wef | grep <pid> # To determine the process
kill -9 <pid>