I have a .bat file that gets executed by Windows Scheduled Tasks (on Win 2003 Server).
The .bat file calls a .vbs script.
The .vbs script moves a text file (which has its data already comma delimited - no quotes) from a drive on the server to a network drive and changes the extension to .csv.
The script then copies the .csv file to a subdirectory in that network drive.
Finally, the script emails the .csv file as an attachment.
Error checking occurs if the original text file is not located on the server and emails our group a notificaton.
The account used by Scheduled Tasks to execute the .bat file is an Admin account on the server.
The script always works Whenever I log into the server (using the same Admin account that is used by the
Scheduled Tasks) and double click the .vbs script or manually right-click on the Scheduled Task and select "Run".
Everything worked fine for three days in a row. I'm not aware of anything else that has changed. I have seen this happen before where a script works fine for a while, then for some reason, doesn't run for a while, and then starts to run fine again.
It seems like the Scheduled Task is not executing the .bat file even though teh Scheduled Task indicates that it has executed for that day (after the file are there).