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.
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.