locked
Task Scheduler on Vista daily keep missing Mondays RRS feed

  • Question

  • I have 2 schedular task on Vista Home edition that runs daily but for a few months now has begun to miss Mondays for both task. The Problem is in setting up next schedular dates. Task Schedular shows next run time as 1/25/2011 4:20 pm and last run time as 1/23/2011 4:20 pm for both task and both task completed sucessfully on 1/23/2011. I do download all updates and believe that some download was responsible for the schedular task to start messing up.  So I delete both task and recreated them but have the same problem today and once again only happens on Mondays.
    Monday, January 24, 2011 10:47 PM

All replies

  • Hi,

    I suggest configure the service to automatic or manual seperately to check the result.

    1. Click the Start Button, in Start Search box, type: "services.msc" (without quotes) and press Enter. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
    2. Double click the service "Task Scheduler".
    3. Click on the "General" tab; test on the "Startup Type" as "Automatic" or "Manual" seperately Then please click the "Start" button under "Service Status" to start the service.

    Meanwhile, could you please clarify which updates were downloaded and especially those might sound related.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Friday, January 28, 2011 8:45 AM
    Moderator
  • Look at Task Scheduler Monday morning at 4:00 AM. Both daily task were completed by 4:30 PM for Sunday and added 6 items each to scheduler history.  One task next run date say 01/31/2011 at 4:20 pm and last run date as 01/30/2011 at 4:20 pm which was correct. The other task show next run date say 01/31/2011 at 4:30 pm and last run date as 01/30/2011 at 4:30 pm which was correct. At 5:00 pm on Monday, I started my daily production and both download production files were missing.
     
    Look at Task Scheduler Monday afternoon at 5:00 pm. Both daily task were not run and no items had been added to scheduler history for 01/31/2011.  One task next run date say 02/01/2011 at 4:20 pm and last run date as 01/30/2011 at 4:20 pm which was incorrect. The other task show next run date say 02/01/2011 at 4:30 pm and last run date as 01/30/2011 at 4:30 pm which was incorrect.
     
    Manually ran both task at 5:00 pm and start my production.
     
    What is bumping up task schedule date for each task by one for each Monday run and not running and not creating any items to scheduler history and leaving last run date along? At first looking after the affect, I thought there was a problem in setting up the next scheduler run but now I believe that its the start of the execution of 01/31/2011 where the problem lies.
    Monday, January 31, 2011 11:23 PM
  • Update:
    2/7/2011 Monday 1:15 PM, I look at task history which show:

    2/6/2011 Sunday 4:20 PM my schedule task completed successfully and next schedule date was set for 2/7/2011.

    2/6/2011 Sunday 4:30 PM my second schedule task completed successfully and next schedule date was set for 2/7/2011.

    2/6/2011 Sunday 4:42 PM a System Task was started at 4:42:38 and completed at successfully at 4:42:40 PM.

     

    Computer been running 20 hours and not another system task was started nor while their ever be another one until I re-boot.

     

    Now I do have another task that backup my files and it runs a 10:00 PM everyday and I set it to run it until successfully completed. This task has been running when I been rebooting on Monday at 5:00 PM. Today it show next schedule date at 10:00 PM 2/7/2011 and last schedule run 2/5/2011. I manually started the task and it run successfully and set up 2/7/2011 as next schedule date. I turn off computers for internal cleaning and brought back up at 4:00 PM. Both schedule task ran successfully at 4:20 and 4:30.

     

    I haven’t the slightest idea of what this system task is that runs on Sunday at 4:42 but it sure seems to be stopping any future task, mine or Microsoft or anyone else, from starting until computer is re-booted.

     

    Tuesday, February 8, 2011 2:08 AM
  • Update:

    Last Task to run at 4:42 pm Sunday 2/6/2011 was a Microsoft SystemTask that:

    "Certificate Services Client automatically manages digital identities such as Certificates, Keys and Credentials for the users and the machine, enabling enrollment, roaming and other services."

    "Task is run at system startup-after triggered, repeat every 08:00:00 indefinitely"

    Tuesday, February 8, 2011 7:58 AM
  • My last update:

    When I reported that no task had been run for 20 hours, I was looking at the form that show all task run in the last 24 hours which show the last system task of 4:42 pm on 2/6/2011 was the final one but when I look at individual history on this 8 hour system task, it show something else. It show it ran at 4:42 pm on 2/6/2011, 12:42 am on 2/7/2011 and 8:42 am on 2/7/2011. Probably different files.

    Tuesday, February 8, 2011 8:50 AM
  • Update

    Monday Feb 21 11:00 AM: All Jobs Finish. Daily Schedule Backup task was 13 hours behind schedule. This task is set to run until completed and is schedule at 10:00 PM. Decide to wait an hour to see if it would start. Last of my daily schedule was successfully completed at 4:30 PM Sunday with only 1 system task run between successful schedule and unsuccessful schedule.  There were successful systems task run after 10:00 pm.
     
    12:22  Decide to reboot.
    12:29  Backup Schedule started and completed. This is what it should do but why is it 14 1/2 hours behind schedule.
     
    Conclusion:
     
    The only consistency here that on each Sunday between 4:30 PM and 10:00 PM my local schedule task goes on the blink. It will change the next schedule start date and leave last schedule completion date along because it will never run any of my local task until I restart.  There is only one system task that is run between those time periods and it does run every 8 hours after. The bug must be after the changing my local next schedule start date and actual starting the task because none of the 6 items store in task history are there.
     
    Monday, February 21, 2011 7:35 PM
  • Update:
     
    Sunday 2/27/2011
     
    Decide to try to break time down further down when task scheduler went on the blink. I set up a task backup2 that would run at 5:00 pm, backup3 that would run at 6:00 pm, backup4 that would run at 7:00 pm, backup5 that would run at 8:00 pm, backup6 that would run at 9:00 pm. This would get the time line from 5 1/2 hours down to 1 hour.
     
    4:30 pm My Normal task completed successfully and added 7 history items.
     
    4:40 pm Microsoft System Task had a launch failure but did completed successfully and added 11 history items.
     
    5:00 pm Backup2 task completed successfully, next run date gets increase by 1 day, last run gets increase by 1 day, and 7 items are added to history.
     
    6:00 pm Backup3 task completed successfully, next run date gets increase by 1 day, last run gets increase by 1 day, and 7 items are added to history.
     
     
    This eliminate my previous theory of Microsoft System Task was causing the problem. From here until next boot, non of my local task will be run.
     
    7:00 pm Backup4 task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    8:00 pm Backup5 task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    9:00 pm Backup6 task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    10:00 pm Normal backup task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
     
    My suspicion has turn Microsoft System Restore Task due to updating an entry every hour and timing seems to by off by 20 minutes.
     
    Last 2 items in history for SR task are:
     
    2/26/2011 12:00:00 AM Task Triggered on Scheduler
     
    2/26/2011 11:59:59 PM Task Triggered on Scheduler
     
    Looking at the line for SR task it show:
     
    Next Run 2/28/2011 12:00:00 AM   Last Run 2/27/2011 8:21:04 PM    and then later
     
    Next Run 2/28/2011 12:00:00 AM   Last Run 2/27/2011 9:21:04 PM   and then later
     
    Next Run 2/28/2011 12:00:00 AM   Last Run 2/27/2011 10:21:04 PM 
     
     
    I begin to look at the time settings for SR task at 10:29 and during that time all 4 previous backup task failures begin their run at the same time. They were set to try until completed. I didn’t see anything in the settings for SR task that suggested to try every hour until successful.
     
    Continuation of SR task:
     
    Next Run 2/28/2011 12:00:00 AM   Last Run 2/27/2011 11:21:04 PM  and then later
     
    Next Run 3/1/2011 12:00:00 AM   Last Run 2/28/2011 12:01:05 AM  and then later
     
    Next Run 3/1/2011 12:00:00 AM   Last Run 2/28/2011 1:01:07 AM 
     
     
    One item was added to history:
     
    2/28/2011 12:00:00 PM Task Triggered on Scheduler
     
    I do not know why or where timing got off for SR task but will check out next Sunday.
    Monday, February 28, 2011 6:24 AM
  • Update:
     
    Windows SR, System Restore, task parameters are:
     
    Trigger:
     
    1) Daily at 12:00 am daily.
     
    2) At startup.
     
    Conditions:
     
    1) Start the task only if computer is idle for 10 minutes.
     
    2) Wait for Idle for 365 days.
     
    Settings:
     
    1) Allow task to be run on demand.
     
    2) Run task a.s.a.p. after schedule start is missed.
     
    3) Stop the task if it runs longer than 3 days.
     
    4) If the running task does not end when requested, force it to stop.
     
    Illogical parameters surely wouldn’t cause task scheduler to mal-function. I decided to make sure by changing the wait for idle from 365 days to 1 hour.  I check Windows 7 parameters and they had 23 hours instead of 365 days. Results were I got one more of my task to complete.
     
    4:30 pm My Normal task completed successfully and added 7 history items.
     
    5:00 pm Backup2 task completed successfully, next run date gets increase by 1 day, last run gets increase by 1 day, and 7 items are added to history.
     
    6:00 pm Backup3 task completed successfully, next run date gets increase by 1 day, last run gets increase by 1 day, and 7 items are added to history.
     
    7:00 pm Backup4 task completed successfully, next run date gets increase by 1 day, last run gets increase by 1 day, and 7 items are added to history.
     
    From here until next boot, non of my local task will be run.
     
    8:00 pm Backup5 task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    9:00 pm Backup6 task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    10:00 pm Normal backup task doesn’t run, next run date gets increase by 1 day, last run is left along, and no items are added to history.
     
    Backup task 5,6 and my normal schedule backup where run when I re-booted Monday at 4:00 pm which made them 23,22,21 hours behind schedule. Next Friday I’ll disable SR task before rebooting. I know if I reboot every Sunday at around 6 pm, all my local task would run on time. I have always thought the problem was that I never had any idle time but I wonder if the same problem would also occur if I ran absolutely nothing but my local task for the weekend. If it did, that would prove a very small allocation area for local task which easy became full with no room for more until I reboot. That something I can’t afford to try. Maybe running 100 local task in a hour which is something I can afford would give this answer.
    Monday, March 7, 2011 9:25 PM
  • Update:
     
    While disabling Windows SR task wasn’t the solution.
    Monday, March 14, 2011 2:47 AM
  • Update:
     
    My 2 Daily Task Schedules are running exactly 1 hour late and are showing  5:20 and 5:30 pm for last and next run instead of the trigger 4:20 and 4:30 thru Wednesday. It didn’t adjust to time change. Tomorrow I try to run them on demand at the proper time to see if this will get them back into sync. Yet my other task that schedule to run at 10:00 runs at 10:00 PM. Answer was to uncheck Synchronize Across Time Zones selection.
     
    .
     

    Wednesday, March 16, 2011 9:45 PM
  • Last update under this thread:
     
     
    I have upgraded to Windows 7. I notice that under Windows 7 task scheduler history items has been disable. Looks like another case of the can being kick down the road. Way too much of that going on in America now. I believe Microsoft was aware of this problem from the start but company policy made it impossible to inform me of it. Just a note that they were aware of it and I would had stop wasting my time. Makes you say to yourself never again. "The only things certain in life are death, taxes and software upgrades."
    Sunday, March 20, 2011 3:43 PM