I have got 3 scheduled tasks:
1) one with a CMD file that use the rasdial command to dial an internet connection using
2) one with a CMD file that runs a perl script to send out an email using a SMTP server with ISP
3) one with a CMD file that use the raddial command to disconnect from ISP
All 3 sceduled tasks have been set up to run as a local user with a valid password which is not blank set.
All 3 tasks, when I right click and press run could run successfully.
However, sometimes the tasks "fail to start". How could I find out why? The scheduled task just says "fail to start" with a status code which I don't know how to interpret. There's no password issue (I think), although I think sometimes the tasks fail regardless of whether the machine is suspended or not (I did tick the box, wake up machine to run task). Is there a bug or something? Is there something I could do to ensure the PC really wake up from suspension to run the task?
1) one with a CMD file that use the rasdial command to dial an internet connection using
2) one with a CMD file that runs a perl script to send out an email using a SMTP server with ISP
3) one with a CMD file that use the raddial command to disconnect from ISP
All 3 sceduled tasks have been set up to run as a local user with a valid password which is not blank set.
All 3 tasks, when I right click and press run could run successfully.
However, sometimes the tasks "fail to start". How could I find out why? The scheduled task just says "fail to start" with a status code which I don't know how to interpret. There's no password issue (I think), although I think sometimes the tasks fail regardless of whether the machine is suspended or not (I did tick the box, wake up machine to run task). Is there a bug or something? Is there something I could do to ensure the PC really wake up from suspension to run the task?