Just as clarification on this part:
If we consider two things that we are likely to care about:
-
FMS was able to successfully authenticate into the file, find the specified script, and invoke it.
-
When the script executes, does every step execute without an error, do one or more steps encounter an error condition?
Then:
When the FMS Admin Console tells you that the schedule was run with "Success", it is only addressing the first point, above, i.e., it is indicating that FMS was able to find the target file, authenticate into it, find the named script, and then invoke the script. An example of a "not successful" outcome when running the schedule would happen if the script could not be found (perhaps it was deleted), or perhaps the credentials that the schedule had been supplied did not work to authenticate into the file.
The "Success" outcome that shows in the Admin Console when running the schedule does not reflect anything about whether the individual steps in the script were executed with or without encountering an error condition.
To find out whether the individual steps in a script encountered error condition(s), two common methodologies are:
- Review the contents of the Event.log on the server, which will include log entries for errors encountered in server side scripts.
- Implement one's own error capturing/logging within the script itself, via code that reads the
Get( LastError )function after script steps that are deemed worthy of error trapping.
It's not at all unreasonable to start with a belief that the "Successful" outcome registered in the Admin Console might imply zero errors encountered by the script steps in the scheduled script, but, as mentioned above, it actually has a different meaning.
Hopefully the above breakdown helps a bit.