Critical update stopped Task Scheduler Service
The Microsoft critcial update released yesterday (810833), messed up the Task Scheduler Service. When I try and start this service, I get, Error 1717: The interface is unknown. The MS page for this patch is This service worked fine until this morning.
The Microsoft critcial update released yesterday (810833), messed up the Task Scheduler Service. When I try and start this service, I get, "Error 1717: The interface is unknown". The MS page for this patch is here
This service worked fine until this morning. I tried uninstalling the hotfix but that didn't fix anything. Anyone else have this problem?
This service worked fine until this morning. I tried uninstalling the hotfix but that didn't fix anything. Anyone else have this problem?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Care to run system file checker
start
run
sfc /scannow
start
run
sfc /scannow
Quote:Care to run system file checker
start
run
sfc /scannow
Ran it... it said I had to be administrator running a console window. Sad thing was, I was logged in as administrator and I was running it from a console window. I am getting real close to getting a third party crontab program.
Edit: Got SFC to work, I was trying to run it from a TS session, W2k didn't like that. This didn't fix the problem, however.
start
run
sfc /scannow
Ran it... it said I had to be administrator running a console window. Sad thing was, I was logged in as administrator and I was running it from a console window. I am getting real close to getting a third party crontab program.
Edit: Got SFC to work, I was trying to run it from a TS session, W2k didn't like that. This didn't fix the problem, however.
Nope, I haven't run any regclean type apps. Maybe an uninstall of a program did the reg corruption. Haven't looked at the .tlb files yet. I think I will install a crontab program tonight, then I can disect this problem at my leisure. It does look like the update didn't do the corruption, or other people would of chimed in. Something else did the corruption.
Thanks for all your help!
Thanks for all your help!
try running a repair install
try running a repair install
try running a repair install
try running a repair install
try running a repair install
try running a repair install
try running a repair install
try running a repair install
try running a repair install
Joel32137's fix did it for the task scheduler unknown interface error 1717 problem. I just turned on the Event Log service, and waa-laa(is that how you spell it?)
