views:

24

answers:

1

I implemented an update process for a piece of software using the Windows scheduler. It worked great until lately. For some reason the task entered in the Windows Scheduler is not executed anymore.

I suspect that the configuration of the target system changed, but I do not know in which way. The command schtasks /query /V /FO list returns:

HostName:                             someHostName
TaskName:                             update myProgram

Next Run Time:                        never
Status:                                
Logon Mode:                           13:03:00 16.02.2010
Last Run Time:                        9020  
Last Result:                          
Creato:                               system
Task To Run:                          c:\myUpdate.cmd

Start In:                             N/A
Comment:                              N/A
Scheduled Task State:                 Enabled
Idle Time:                            Disabled

Run As User:                          NT Authoring /System
Delete Task If Not Rescheduled:       Enabled
Stop Task If Runs X Hours and X Mins: 72:00:00
Schedule:                             Enable
Schedule Type:                        One time only
Start Time:                           N/A
Start Date:                           N/A
End Date:                             N/A
Days:                                 N/A
Months:                               N/A
Repeat: Every:                        N/A
Repeat: Until: Time:                  N/A
Repeat: Until: Duration:              N/A
Repeat: Stop If Still Running:        N/A

The task was inserted at 16.02.10 13:02:14, and therefore, it should have ran at 13:03:00 16.02.2010, but Last Runtime shows 9020. Does anybody know what that means?

A: 

It turned out that the executable started by the scheduler was missing a DLL and therefore could not executed. So I guess 9020 is some sort of error code, although I could not find it in the reference.

Bertolt