Check your environment variables. Make sure that MKS specific variables are setup as system-level variables not as account-level variables.  When a program is run from 24x7 (or any any process) it inherits environment settings of the parent process.  : We have a Unix script we are using to parse log files. It runs on Windows  : using the MKS Toolkit. Any time I try to schedule it returns the message,  : "Create Process Failed. Return code: 2 - The system cannot find the  : file specified. If I try using one of the Unix Automation commands, it  : says, "Remote Access Error: Not connected to remote host." It  : should be running locally through the MKS Toolkit. What am I missing?   
   |