Task Scheduler Alternative

[bobvolz]

Does anyone have or use an alternative to the Windows Task Scheduler. I support 6 Windows 2008 servers and have to run 10 or so nightly tasks. These tasks that run can be exes or .bat . I have found the Win 2008 task scheduler to be very unreliable. The tasks will appear to run but do not. Or the error log will show an invalid directory name. I can usually run them manually from the task scheduler without issue but they appear to get hung up when left on their own to run. Any help would be appreciated.

Bob Volz

[Eugene Lutsenko]

Maybe Alaska write scheduler, such as do you need? I think it is not very difficult. Make a table in which to write the date and time of the application for execution, the path to the file to run it. Allow the user to adjust the table. Make periodic review of this table timer using constructions like:

Code: Select all

oTimer := DC_SetTimerEvent():new(100,{||TableScan(@oDlg)})

and launch performance of the applications for which the time has come. If the time has come to take from the table the full file name run the application and run it using: RunShell("","FunctionName.exe",.F.)

[Cliff Wiernik]

I have found it to be likely related to security issues. You need to have the correct login user for it to work properly. However, don't specifically know what the issues are. Without the proper user, it appears the mappings are not correct. I have generally used the native drive unc path instead of the shared drive letter path and that appears to work better.

[skiman]

Hi Bob,

As Cliff already wrote, this is a security issue. I had the same on a server, and the network administrator fixed it. The task is running as administrator. I don't know what was changed on the server.

The cause is because the task is started when there is nobody logged in on the server.

[bobvolz]

Thanks guys. I usually run as an administrator whether the administrator is logged on or not.
I have tried all the paths including the using local drive letters.

This all worked just fine with Win 2003. I think they crapped up Win 2008 with security stuff . Either that or my virus protection is acting up.
I' will keep trying.
Bob Volz