Nagios Support Forum

Ok, finally got back to testing this(end of fiscal year, lots of vacation time being used).

As I stated, the updated NRDS fix the installer not passing the variables and the vbs is now the latest version. However, my problem persists in that our task scheduler, Control-M, is still unable to run it. I'm thinking it has to be a permissions thing, but just not sure. Any advice would be welcomed.

It's possible that this is a permissions issue. Have you looked for possible solutions in the Control-M's Administrator Guide? Do you have issues with scheduling any other tasks via Control-M?

No other issues. Control-M is what we use for all scheduled tasks in our environment for immediate notifications if a job fails. It is very heavily used and as far as I know there is no issue. I need to check tomorrow, but I don't think the user actually logs in to run the bat/exe/vbs/whatever. Maybe that is the issue, not sure. I'll be doing very minimal more testing before I give up and just used scheduled task since it will only be a rarely used case.

If anyone can think of something for me to check, again, please feel free to chime in

Unfortunately we don't have Control-M in house. Otherwise, I would love to test it. Let us know how it went.

I'll be doing very minimal more testing before I give up...

It is not your style, BanditBBS.

LOL, I know, but it is only the one machine so far. That being said, it has been resolved.

There were two parts to fixing it, the user Control-M uses needs to be member of local admins and in the Control-M agent, there is a check box that needs checked that allows child processes to be kicked off. I can't remember the exact wording of the check box, but with what I said, should stick out pretty good.

Make sure those two items are set and Control-M can run it instead of used scheduled tasks. Now if it ends with any other code then 0 we'll know immediately.

The one other item to know, I am not having control-M call the vbs directly, I use a batch file that CD's to the folder and runs the vbs with cscript.

Tada!

I'm glad the issue has been resolved! Thanks for sharing the solution! I am locking the topic.