Syslog and Trap Monitor leave orphan wscript.exe processes running after action

benbree

Team,

I have an action on both syslog and trap monitor to execute a script to convert the trap/syslog message to an Orion alert.  Sometimes after the action is performed (normally in the early AM hours), it leaves a wcript.exe process running until there are too many wscript processes for the server to continue to perform.  Have you seen this?  Is this a problem with my script?  Or is it something in the way the trap/syslog engines process the alerts?

Thanks for any ideas you have!

Regards.

MarieB

Hey benbree-

Did this get resolved? Also, did you try a search in thwack. I searched on wcript.exe and it returned the following items:

http://thwack.com/search/thwacksearch.aspx?q=wcript.exe

HTH,

M