I have used the Execute External Program action previously on Win XP and earlier OSs but now have Orion on Win 2003 R2 sp 2 server and although the action appears to work (according to test log) and the command runs fine from CMD box the requested program does not run.
Tried giving Local System account the Allow service to interact with Desktop option and also used an alternative account with full local admin rights.
Still no go
What an I missing?
Has anyone got this running on Win 2003 R2 Sp 2 (or either Win 2008 server or Win 7 - have tried with similar lack of success on these with the eval version)
Solved! Go to Solution.
first thing i think of is this, but it could be wrong - in the Program To Execute action did you use the full path name to your program, like: C:\Program Files\DoThis.exe myparameters_here
or even enclose it in quotes "C:\Program Files\DoThis.exe myparameters_here"
these Execute External Program actions are real tricky and finicky for sure.
somewhere along NPM v8 or v9 i remember having to do this too, but i don't any longer. i don't know if maybe an update along the way changed this since now everything is local-system. but maybe it will work for darryl's case.
More ideas... I've wrestled with the like for many hours... days... per note above... it can be real picky.
1. If its a home grown script... add a local log file. I have a function I stick at the bottom of all my vbscripts.. this has helped tracing problems.
2. If you are passing vars... try double/tripple quotes. I think I even have one with quadruple quotes.
3. When you test make sure you use the same user that the alert engine is running... this user by default is a local server user. I had to change the user to a user that has authority to run the remote commands.
4.The alert test does not work. It says it does but it does'nt. To test you need to have the monitor trip. I do this by changing my thresholds.
5. The little box you need to type is is really easy to mis-type and not see the typo. I always type in another editor then cut and paste.
Thanks for the answers guys.
It turns out that the action was being executed only not in the way I was expecting it to but at least I can focus on the real problem now
I am not sure how that person resolved it, but I have seen issues with running batch files before because of the NTFS permissions set on cmd.exe.
I have just change the permissions on it (that might not be something MS would be happy to hear, but you can do it anyhow). I just check the inheritable permissions and it works after that.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.