Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Execute Program ... Doesn't Appear to be Executing

I have created an alert which runs an executable which interfaces to our Remedy ticketing system. I have created two trigger actions, one to execute a program, the other to write to the event log. The Event log action contains the exact same string as in the Execute Program action ... and is just to ensure that the variable substitution was working, etc.

Execute Program:

mbclient.exe nodb=true Priority=4 Short_Description=${NodeName} DOWN Details=${DateTime}: ${NodeName} down for over 15 minutes. SITE: ${City}. IP ADDRESS: ${IP_Address}. OOB #: ${OOB} Category=Other Type=Other Item=Other Group=Networks

NetPerfMon Event Log:

The action is working for the event log when i do a test of the alert and I see the following in the event log:

mbclient.exe nodb=true Priority=4 Short_Description=aplbio-monzasg-1310043.pipngw.mci.com DOWN Details=Thursday, April 01, 2010 2:57 PM: aplbio-monzasg-1310043.pipngw.mci.com down for over 15 minutes. SITE: Monza. IP ADDRESS: 10.251.149.205. OOB #: Category=Other Type=Other Item=Other Group=Networks

However, I do not see the expected results from the program execution (i.e. a ticket is not created in our Remedy system).

I can copy the text from the event log and paste into a CLI window, though, and I *do* get the expected results, including positive creation of a ticket.

H:\>mbclient.exe nodb=true Priority=4 Short_Description=aplbio-monzasg-1310043.p ipngw.mci.com DOWN Details=Thursday, April 01, 2010 2:57 PM: aplbio-monzasg-1310 043.pipngw.mci.com down for over 15 minutes. SITE: Monza. IP ADDRESS: 10.251.149 .205. OOB #: Category=Other Type=Other Item=Other Group=Networks

2010/04/01 14:58:39 Attempting to send: 21 2010/04/01 14:58:39 INFO: Starting WS Call 2010/04/01 14:58:45 INFO: Finished WS Call: [name=return] [type=class java.l ang.String] [value=0000429796] [encodingStyleURI=null] 2010/04/01 14:58:45 Transaction Sent: 21

Any ideas? Any way to verify that the command is in fact executing, verify output, etc?

Find more posts tagged with

Accepted answers

mrxinu

Taking the next wild stab - try changing the user that runs your alert engine to the same that's able to run that command successfully.

All comments

gbutler

Play with quotes with your arguments I found stuff that worked on cmd-line did not translate to the alert exe line.

If you can get your exe to use a local log file so that you can trace where it breaks.

I found it very easy to edit mistakes in that puny little window where I type the exe string. I cut and paste to be safe.

mrxinu

Taking the next wild stab - try changing the user that runs your alert engine to the same that's able to run that command successfully.

brian_crypto

Thanks! The main problem did indeed turn out to be with the agent service account. I changed that to use a local admin account and it is working fine now.

I did ultimately end up using a batch file though, passing the arguments to it and then letting the batch file pass the parameters on to the actual .exe. This allowed me to setup a troubleshooting log to verify that the command was really firing. And then ran into the need for the quotes for the DateTime field because the spaces cause each block to be read as a different parameter.

So, it all works fine now ...

In the event that this is useful for anyone elase, my alert trigger now uses the follow command line:

CreateRemedy.cmd ${NodeName} "${DateTime}" ${City} ${IP_Address} ${OOB}

and the "CreateRemedy.cmd" looks like this:

@echo off<br />D:<br />set NodeName=%1<br />set DateTime=%2<br />set City=%3<br />set IPAddress=%4<br />set OOB=%5 <br /><br />echo =============================================================== >>  d:\message_broker\CreateRemedy.log<br />echo %date% %time% >>  d:\message_broker\CreateRemedy.log<br />echo   NodeName=%NodeName% >>  d:\message_broker\CreateRemedy.log<br />echo   DateTime=%DateTime% >>  d:\message_broker\CreateRemedy.log<br />echo   City=%City% >>  d:\message_broker\CreateRemedy.log<br />echo   IPAddress=%IPAddress% >>  d:\message_broker\CreateRemedy.log<br />echo   OOB=%OOB% >>  d:\message_broker\CreateRemedy.log

 mbclient.exe nodb=true Priority=4 Short_Description=%NodeName% DOWN Details=%DateTime%: %NodeName% down for over 15 minutes. SITE: %City%. IP ADDRESS: %IPAddress%. OOB #: %OOB% Category=Network Type=WAN Item=Outage Group=Networks >> d:\message_broker\CreateRemedy.log echo %date% %time% >> d:\message_broker\CreateRemedy.log

mrxinu

Nice integration - thanks for sharing. I'm glad that sorted you out.