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?

"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?"

Sounds like a .tlb file screwup, or registry GUID is gone/messed up!

I know that Microsoft uses things called Type Libraries (.tlb extensioned files) on disk that house things called INTERFACES for programs... COM stuff iirc. That is the keyword here, the word "interface", but that might be a registry GUID as well.

(Uually, .tlb files are full of abstracted function calls for other libraries.)

What are you running in Task Scheduler? One by one, eliminate it down to the problem one, if it is ONLY 1 of them... that's what i'd try first! Could be the application itself, one of your scheduled items is bad.

I'd guess that whatever typelib or registry GUID for a DLL/OCX/ActiveX in the Task Scheduler as a scheduled item that it is calling on to load things up has changed & they may not have accounted for it in that applications' code.

Who knows, Task Scheduler may need a patch for this new patch as well, but I don't use the TaskScheduler at all here, I turn it off, so I have not run into that here!

* Anyone else hit this wall?

APK

P.S.=> If you can zero it down to only ONE of the programs in there being bad then uninstall the app & reinstall it! apk

Deleted all the tasks... same error.

How do I uninstall, then reinstall the task scheduler service? Any dependancies that I need to worry about?

"Deleted all the tasks... same error. "

Ok then... the problem's sounding/looking like it is in the Task Scheduler service itself at this point from the data you are providing as well as the test you performed!

Your registry... have you by any chance run any types of Registry Cleaning program on it?

Many of them (not mine though, afaik, I had to make corrections for that a couple years back in fact) will list as candidates for deletion things called TypeLibs (the .tlb GUID registrations I mention above) & CLSID (Class Identifiers) that interface housed abstracted functions may possibly require... COM/ActiveX/OLEServers use this like mad!

Some registry cleansing programs CAN & will cause this type of damage because of their lack of safeguards/filtrations of those items in the registry IF you chose to indiscriminately remove them without further detailed investigation of them...

Now this is more than just a thought!

See, I've seen this "go-down" before & have even advised another coder (who took GREAT offense to this suggestion, I don't blame him, sometimes it stings taking critique) to correct this in his application in fact.

To date, he has not... not that I am aware of at least.

EDIT PART - IF you are LUCKY in that scenario... the program in question maintains some sort of registry OR file based tracking of its activities & provides you a means to re-merge the entries you removed... good ones, do!

"How do I uninstall, then reinstall the task scheduler service? Any dependancies that I need to worry about?"

THAT is a good question, I do not believe you can easily. I don't know if changing sysoc.inf files' internal contents will show Task Scheduler even as a removeable item in Control Panel, Add-Remove Programs, Windows Components (as that will show MANY that are not shown as removeable, but are if you edit that file properly).

Lookup sysoc.inf here on the forum, I am sure I have seen the technique illustrated/enumerated for that, to get things normally hidden from view to show in it for use in removal in said control panel item mentioned above!



* Good luck, if this does not work, we will keep at it... it'd be an interesting thing to investigate!

APK

P.S.=> Again though: I wonder, has anyone else hit this problem besides yourself? If not, it may be a 'simple-case' of disk file (in the case of a .tlb) or registry corruption for the function/dll/activeX/ocx com libs it calls & their interfaces as it seems to be telling us here... apk

Care to run system file checker

start
run
sfc /scannow

"Care to run system file checker

start
run
sfc /scannow

"

Good point, because it may be a case of a corrupted file OR missing one...

(OR, the 'classic' mismatch of OLEServer DLL version build needed is overwritten by another model that has diff. function call errorlevels returns in it, or function call parameter values types changes from what is expected by taskscheduler calling it.)

*

Running it as DS3Circuit points out, is not going to hurt anything & maybe even fix it!

APK

"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.

Durt,

Personally I think really that you have a few registry GUIDS missing for various TypeLibs (type library function calls) that TaskScheduler needs to go calling functions it uses... registry corruption, rather than a missing .tlb file.

This is why I asked if you ran any registry cleaning programs, some will present those to you as valid to remove, when in fact, they are NOT!

* Here is part of the problem of complexity that comes up when you build apps with alot of "moving parts": More room for breakdown.

(Blow out one wrong GUID in a CLSID or TypeLib entry in the registry, or burn a file on disk by mistake, and BANG!)

This system of "non-monolithic" totally statically linked executeables files systems does have its merits in easier & potentially smaller updates & patches since you don't have to replace the WHOLE system when updating it, & also in dynamically loadeable/unloadeable .DLL/.OCX etc. in memory mgt. but the trade off is that stuff being more parts to keep solid & tracked... plus, it lets the system overall be smaller, sharing various libraries common to many applications.

(DLL Hell has been lessened with WFP/SFP in place with side by side loadings of needed libs, but that too, is not totally perfect either but a great start)

I try to build single-exe style apps, because of less moving parts to track but sometimes I use .DLL's & .OCX's because they are proven & work... and would be TOO much work to try to build some of their functions manually & be 110% sure they are as solid as some prebuilt functions are.

I imagine it's the same for most coders in that respect.

APK

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!

Well, you're welcome first of all, I hope that some of that does help in solving your hassle...



* Whatever you do, don't give up on it & reinstall if you don't have to... it'd be neat to see if you do in fact arrive at a solution!

(Even if it is a "paperclips, rubberbands, & super-glue + chicken-wire" type of hacked up fix for this!)

QUESTION: Have you examined the contents of sysoc.inf & see if you can make the TaskScheduler tools available for update/reinstall/uninstall? That file hides ALOT of what Windows Installer can display in the actual Windows Components add-remove tool in Control Panel... look into it, it may have taskscheduler be one you can remove & then reinstall fixing it up!

APK

P.S.=> And, I agree... if it was the patch that messed you up, alot more folks would have put in their 2 cents worth as well I imagine having fallen victim to it also... apk

Here's a solution that worked for me when I encountered the same error code when starting the Task Scheduler service..

Make sure your Event Log service is started and set to automatic.

Hope this helps

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?)