I have Windows schedule task that executes vb script daily. Scrip is set to load and update data in access db and sql db.
The Windows schedule task remains in a Running state for a period of time (5 plus hours ...). No errors found.
Please help to find an answer to this task performace issue...
There are error handlings in VBS, and the data was updated correctly by the process for a while. It has not been running prop. since mid december.
No errors. Nothing.
Not sure what could that be.? as of now I'm running that process manually, but really like to go back to the schedule task. Is there are a way to send a message of complition to a log file after each piece of logic complete? Or I have to debug each piece and see where prob is.?