Event Log and Task Scheduler

I've searched the web for this and hacked my way around but just can't find
the answer.

2 errors:

1) Event Log service wont start. Error 4201 the instance name passed was not
recognized as a valid WMI provider

2) Task Scheduler: "task scheduler not available" whenI try to acesss it.
The service is up and running.

I've tried various things including taking ownership of the logfiles
directory. Ensuring full ownership on the registry keys. To no avail.

Also, i've found some response to check the Local Sec Pol but there's not
snap-in for it. I'm running Vista Home Premium.

This is driving me nuts because all I want to do is install an HP 840c
printer from an XP box running it as a printer server and it wont install.
Though the HP site says you dont need any drivers etc. Can't check the event
logs cause they aren't workign.

Agggh!

Cheers
Lincoln

http://support.microsoft.com/kb/929833

"Lincoln De Kalb" <> wrote in message
news:9D784DD4-3E11-40CB-88B9-...
> I've searched the web for this and hacked my way around but just can't
> find the answer.
>
> 2 errors:
>
> 1) Event Log service wont start. Error 4201 the instance name passed was
> not recognized as a valid WMI provider
>
> 2) Task Scheduler: "task scheduler not available" whenI try to acesss it.
> The service is up and running.
>
> I've tried various things including taking ownership of the logfiles
> directory. Ensuring full ownership on the registry keys. To no avail.
>
> Also, i've found some response to check the Local Sec Pol but there's not
> snap-in for it. I'm running Vista Home Premium.
>
> This is driving me nuts because all I want to do is install an HP 840c
> printer from an XP box running it as a printer server and it wont install.
> Though the HP site says you dont need any drivers etc. Can't check the
> event logs cause they aren't workign.
>
> Agggh!
>
> Cheers
> Lincoln

Thanks for that but no good. Ran the SFC and rebooted. No files where found
top be unable to be fixed.

Any ideas?

Cheers
Lincoln

"Mac" <> wrote in message
news:6497F49A-BC37-43C7-B777-...
> http://support.microsoft.com/kb/929833
>
> "Lincoln De Kalb" <> wrote in message
> news:9D784DD4-3E11-40CB-88B9-...
>> I've searched the web for this and hacked my way around but just can't
>> find the answer.
>>
>> 2 errors:
>>
>> 1) Event Log service wont start. Error 4201 the instance name passed was
>> not recognized as a valid WMI provider
>>
>> 2) Task Scheduler: "task scheduler not available" whenI try to acesss it.
>> The service is up and running.
>>
>> I've tried various things including taking ownership of the logfiles
>> directory. Ensuring full ownership on the registry keys. To no avail.
>>
>> Also, i've found some response to check the Local Sec Pol but there's not
>> snap-in for it. I'm running Vista Home Premium.
>>
>> This is driving me nuts because all I want to do is install an HP 840c
>> printer from an XP box running it as a printer server and it wont
>> install. Though the HP site says you dont need any drivers etc. Can't
>> check the event logs cause they aren't workign.
>>
>> Agggh!
>>
>> Cheers
>> Lincoln
>

I had the same problem for months. Even on a brand new fresh install that I
setup in another partition for testing--right from the start, no Event
Viewer/Log Service and therefore no Task Scheduler (they are tied
together--can't have the latter without the former).
I ignored it for a long time and just did not use Task Scheduler or try to
access any logs.
Finally, in 'last resort mode'--after imaging my drives just in case, I
tried a Repair Install (Upgrade install started from the Vista
desktop--takes a while) making sure to remain internet connected (so that
many updates are slipstreamed during the setup process)...and it worked.
Fixed the problem(s) totally. And all has been working ever since.
No idea how or why.
The only downside was that a number of settings/services/drivers reverted to
their defaults, and it took a bit of time to get things back to how I liked
it.

--
Maxwell Bluemeanie
----
"Lincoln De Kalb" <> wrote in message
news:9D784DD4-3E11-40CB-88B9-...
> I've searched the web for this and hacked my way around but just can't
> find the answer.
>
> 2 errors:
>
> 1) Event Log service wont start. Error 4201 the instance name passed was
> not recognized as a valid WMI provider
>
> 2) Task Scheduler: "task scheduler not available" whenI try to acesss it.
> The service is up and running.
>

Thanks for that Max. I had seen someone write that they reinstall over the
top using the upgrade option.

Amazes me that there are so many people out there the with the issue and no
fix from MS. I think they are being carefull (read slow) to patch
non-critical stuff lest the media beat them up over it.

"Max" <> wrote in message
news:...
>I had the same problem for months. Even on a brand new fresh install that I
>setup in another partition for testing--right from the start, no Event
>Viewer/Log Service and therefore no Task Scheduler (they are tied
>together--can't have the latter without the former).
> I ignored it for a long time and just did not use Task Scheduler or try to
> access any logs.
> Finally, in 'last resort mode'--after imaging my drives just in case, I
> tried a Repair Install (Upgrade install started from the Vista
> desktop--takes a while) making sure to remain internet connected (so that
> many updates are slipstreamed during the setup process)...and it worked.
> Fixed the problem(s) totally. And all has been working ever since.
> No idea how or why.
> The only downside was that a number of settings/services/drivers reverted
> to their defaults, and it took a bit of time to get things back to how I
> liked it.
>
> --
> Maxwell Bluemeanie
> ----
> "Lincoln De Kalb" <> wrote in message
> news:9D784DD4-3E11-40CB-88B9-...
>> I've searched the web for this and hacked my way around but just can't
>> find the answer.
>>
>> 2 errors:
>>
>> 1) Event Log service wont start. Error 4201 the instance name passed was
>> not recognized as a valid WMI provider
>>
>> 2) Task Scheduler: "task scheduler not available" whenI try to acesss it.
>> The service is up and running.
>>
>