New
#11
See my updated post above..
Note here the problem is reported as fixed after an in-place upgrade repair:
http://answers.microsoft.com/en-us/w...c-3b0d97dee86b
See my updated post above..
Note here the problem is reported as fixed after an in-place upgrade repair:
http://answers.microsoft.com/en-us/w...c-3b0d97dee86b
Thank you Dalchina for your suport and good advice. Tweaking.com's Repair tool worked, the scheduler is back in business. Have to re-do some settings (e.g. Firefox instead of Edge) but that's peanuts.
Keep up the good work.
Regards,
Steinspecht
I just had the same issue and read all the posts below to no avail. To cut a long story short here is the fix that worked for me ( no idea why this worked but it did)
1) I created a new version of the task in the Apple folder in the Task Scheduler Library (rather than my own folder)
2) I could run this manually within the Task Scheduler app without the error
3) I exported the task from the Apple folder then imported it back into "My" folder in the Task Scheduler Library
4) Now I could manually run the task in my folder without any problems.
It makes no sense to me but it sure beats having to do a reinstall and all that entails. Worth 2 minutes of your time to try that's for sure. :)
I will have to wait until tomorrow at 8 am to see if it runs at its scheduled time but I fully expect it to. If not I'll update this post.
Update : Scheduler task ran normally so I guess the fix worked
Last edited by LeftlySC; 18 Nov 2016 at 08:30.
update: Scheduler task ran fine at 8 am as expected so whatever this "fix" did it it worked
That didn't work either This is so frustrating...
I was able to get something working though! I've been doing 'Create Task...', but then I tried 'Create Basic Task...' and for whatever reason that worked. I only wanted my task to run when I was connected to a specific network (which the basic task doesn't do), but I think I'm done poking it.
I kept getting the "Task Scheduler service is not available" message but found that it was only on specific tasks, so I started comparing task settings. It turned out that the problem for me was caused by a having a network condition for a network that no longer existed. I disabled that condition and then all the tasks started working again.
Changing/removing some task conditions might be worth a shot for other users having this issue. It looks like some conditions can cause the "not available" message to show up if they fail.