Scheduled task problem

  • Thread starter Thread starter Jack
  • Start date Start date
J

Jack

4 weeks ago I setup Task Scheduler to open MS Internet Explorer specified
webpage once a week, on Sunday at 11 pm.
The task was properly executed on 2 consecutive Sundays.
However for the last 2 Sundays task was NOT run.
Reported status: "Could not start"
Last result: 0x0
I need to find out, why?
At that time I was at my computer, doing some typing.
CPU was NOT utilized at all, Internet connection was on (broadband).
In fact I stopped even typing in anticipation of that task to run.
How can I debug that problem?
Your thoughts, please
Jack
 
This is a known bug that affects PCs during the transition from/to
daylight saving time, if the system is installed on a FAT/FAT32
partition. You can solve it in two ways:
- Re-enter the account/password for each task twice each year.
- Convert your system disk to NTFS.
 
Thank you.
Known bug???
Why then MS does not release the fix for it?
I am receiving daily some updates from MS. Why not to fix that bug then by
live update or by Service Pack?
Microsoft should NOT tolerate existence of "known bugs", if it cares about
excelence!
Jack
 
Microsoft should NOT tolerate existence of "known bugs", if it cares about
excelence!
Click to expand...

Unfortunatly this bug has probably fallen prey to prioritiztion.
Personally I would rather have them concentrate on security related
bugs, rather than them fixing something that is 'inconvienient' at worst
twice a year.

Tim Donahue
 
I believe they do have the different departments to deal with the different
issues.
And they are not occupied by the one issue (security) only.
For people running automated tasks this bug can cause quite big harm, if
they DO NOT KNOW about it.
This problem could damage some security of the system as well.
Just another thought.
Jack
 
Tim Donahue said:
Unfortunatly this bug has probably fallen prey to prioritiztion.
Personally I would rather have them concentrate on security related
bugs, rather than them fixing something that is 'inconvienient' at worst
twice a year.

Tim Donahue
Click to expand...

You have a point here. On the other hand, this bug has been
around for several years. I find it a little irritating that it is
neither resolved nor properly documented in the Knowledge Base.
 
Back
Top