How to set up Windows Server 2003 to notify on scheduled task failure

Troubleshooting scheduled scripts:

1. If you haven't already, check the Scheduled Tasks log file, in the GUI under Advanced > View Log. Search the file for "***" to find the most recent entries, and you may see a little extra error info.

2. Define a log file to capture output, and send both standard out and standard error there. Change any echo OFF to echo ON to be sure you're not supressing any error messages.
   For example, if your script is called ftp.data.cmd then your scheduled task might look like this,

   cmd /c ftp.data.cmd >> ftp.data.log 2>&1

3. Is the script hanging? Maybe the task scheduler is killing the script (hence the CTRL+C error code) after some specified period of time. Add some of these at strategic points in your scipt,

   echo %DATE% %TIME%

4. Are you sure the account running the script has permissions / access to everything in the script?

5. If you can't get any joy, run this command and post the output here, maybe we can start with the scheduling,

   schtasks /query /v /fo LIST /s YOURSERVER

You could run it silently using a Windows Script file instead. The Run Method allows you running a script in invisible mode. Create a .vbs file like this one

Dim WinScriptHost
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run Chr(34) & "C:\Scheduled Jobs\mybat.bat" & Chr(34), 0
Set WinScriptHost = Nothing

and schedule it. The second argument in this example sets the window style. 0 means "hide the window."

Complete syntax of the Run method:

 object.Run(strCommand, [intWindowStyle], [bWaitOnReturn])

Arguments:

• object: WshShell object.
• strCommand: String value indicating the command line you want to run. You must include any parameters you want to pass to the executable file.
• intWindowStyle: Optional. Integer value indicating the appearance of the program's window. Note that not all programs make use of this information.
• bWaitOnReturn: Optional. Boolean value indicating whether the script should wait for the program to finish executing before continuing to the next statement in your script. If set to true, script execution halts until the program finishes, and Run returns any error code returned by the program. If set to false (the default), the Run method returns immediately after starting the program, automatically returning 0 (not to be interpreted as an error code).