- This topic has 7 replies, 2 voices, and was last updated 8 years, 8 months ago by .
-
Posts
-
I’m not sure why, but my scheduled patching tasks did not run last night. Everything looks good as far as I can tell, so I don’t know what I may have missed.
I have my schedule to run every Wednesday at 01:00.
I looked for some logs, but I don’t see any logs related to last night. I only see the logs for when I manually patched the systems last month.
It sounds to me like you did not enable the scheduler. After you schedule a date/time for a task to run you have to also enable the scheduler, which is not enabled by default. Please have a look at the following page, which explains in more detail how to use the task scheduler.
That’s definitely odd. Can you paste the ‘All Messages’ column content for me to review? If BP modified the next run time, then it should have logged something indicating that the task ran or was missed etc. Also, you said in your original posting that you have the schedule set to run every Wed at 01:00. However, you are now saying that is says the next run time is for the 2nd Wed of April, which implies that you have it set to run monthly, not weekly. Not sure if that has something to do with the issue or not, but I’m highlighting it in case. How do you actually have it set? To run on the 2nd Wed of every month?
Thanks,
Doug
Thanks for sharing. It’s unclear to me what might have happened here. We do not currently have any other reports of similar problems, and I’m not able to reproduce any similar issue. That said, it might be hard to determine exactly what conditions are required to produce the problem. Please let me know if it happens again.
Was this scheduled task loaded from a pre-existing .bps file that you loaded up on Tuesday? Or on Tuesday did you manually set the schedules up from scratch to run Wed at 01:00? If it came from a .bps file and if you have that .bps file still (without having saved over it), then if possible I would want to see that original .bps (sent to me as email attachment, pls). Let me know.
Thanks,
Doug
I just emailed you.
Thanks!
Also, I would strongly encourage you to test out the scheduler in advance of patching by just setting up a bogus test job to a non-existent computer. You can schedule the job for a couple minutes in the future and then just watch it execute. Obviously it will fail because the target computer won’t exist, but you will then at least be able to confirm that the task is being executed in the first place, as opposed to just somehow not even getting executed.
-Doug
- You must be logged in to reply to this topic.