When trying to start the Windows Event Log service, I get:

"Windows could not start the Windows Event Log service on Local Computer.

Error 4201: The instance name passed was not recognized as valid by a WMI
data provider."

MSKB and Google searches yield nothing useful - just a few people trying to
get this question answered.

Anyone have a clue? If I can't fix this my only option is to reformat and
reinstall as all repair options have failed.

Bill--

I would add in addition to the two Startup Repair options and five F8
options I gave you, to do an SFC from an elevated command prompt:

Right click run box on start menu>run as admin>type sfc/ scannow at cmd
prompt.

CH

"Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
news:8350810B-0216-42FE-996D-7C1E8C73F75F@microsoft.com...[color=blue]
> When trying to start the Windows Event Log service, I get:
>
> "Windows could not start the Windows Event Log service on Local Computer.
>
> Error 4201: The instance name passed was not recognized as valid by a WMI
> data provider."
>
> MSKB and Google searches yield nothing useful - just a few people trying
> to get this question answered.
>
> Anyone have a clue? If I can't fix this my only option is to reformat and
> reinstall as all repair options have failed.[/color]

It tests OK:
"Windows Resource Protection did not find any integrity violations."

However, I still can't run the Windows Event Log service.

"Chad Harris" <fixvista-itneedsit.net> wrote in message
news:O5gMae3OHHA.4244@TK2MSFTNGP04.phx.gbl...[color=blue]
> Bill--
>
> I would add in addition to the two Startup Repair options and five F8
> options I gave you, to do an SFC from an elevated command prompt:
>
> Right click run box on start menu>run as admin>type sfc/ scannow at cmd
> prompt.
>
> CH
>
> "Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
> news:8350810B-0216-42FE-996D-7C1E8C73F75F@microsoft.com...[color=green]
>> When trying to start the Windows Event Log service, I get:
>>
>> "Windows could not start the Windows Event Log service on Local Computer.
>>
>> Error 4201: The instance name passed was not recognized as valid by a WMI
>> data provider."
>>
>> MSKB and Google searches yield nothing useful - just a few people trying
>> to get this question answered.
>>
>> Anyone have a clue? If I can't fix this my only option is to reformat and
>> reinstall as all repair options have failed.[/color]
>[/color]

It tests OK:
"Windows Resource Protection did not find any integrity violations."

However, I still can't run the Windows Event Log service.

"Chad Harris" <fixvista-itneedsit.net> wrote in message
news:O5gMae3OHHA.4244@TK2MSFTNGP04.phx.gbl...[color=blue]
> Bill--
>
> I would add in addition to the two Startup Repair options and five F8
> options I gave you, to do an SFC from an elevated command prompt:
>
> Right click run box on start menu>run as admin>type sfc/ scannow at cmd
> prompt.
>
> CH
>
> "Bill Hobson" <Ihatespamb-hobson@tamu.edu> wrote in message
> news:8350810B-0216-42FE-996D-7C1E8C73F75F@microsoft.com...[color=green]
>> When trying to start the Windows Event Log service, I get:
>>
>> "Windows could not start the Windows Event Log service on Local Computer.
>>
>> Error 4201: The instance name passed was not recognized as valid by a WMI
>> data provider."
>>
>> MSKB and Google searches yield nothing useful - just a few people trying
>> to get this question answered.
>>
>> Anyone have a clue? If I can't fix this my only option is to reformat and
>> reinstall as all repair options have failed.[/color]
>[/color]

With MoveFile...

[url]http://www.microsoft.com/technet/sysinternals/SystemInformation/PendMoves.mspx[/url]

...you can delete folders before the system blocks files.

I sheduled "C:\Windows\Logs" and "C:\Windows\System32\LogFiles" to
delete at startup, rebooted and the EventLog was online again.


Code:
--------------------

"X:\***\movefile.exe" "C:\Windows\System32\LogFiles" ""
"X:\***\movefile.exe" "C:\Windows\Logs" ""
--------------------



KR, Philipp


--
Scaenicus
------------------------------------------------------------------------
Scaenicus's Profile: [url]http://forums.techarena.in/member.php?userid=35362[/url]
View this thread: [url]http://forums.techarena.in/showthread.php?t=662676[/url]

[url]http://forums.techarena.in[/url]

You are right:
It -IS- a permission problem. But the snag was, that I wasn't able to
change something with the permissions, because these files were in use.
(Well... I believe that was the reason)

So add to my solution: The root-folders of the logfiles (Windows and
System32) have to have permission sets, where the "system"-account is
able to read and write files.
Then -after you delete the messed up folders- Windows will copy the
permission for the recreated log-folders from their root-folder (and
the system, as well as the services, are able to use the files).

And why the permissions were messed up at my PC I can only guess - I
use a more or less virgin Vista and not any other OS ((Well... at
-this- PC *gg*)).


KR, Philipp


--
Scaenicus
------------------------------------------------------------------------
Scaenicus's Profile: [url]http://forums.techarena.in/member.php?userid=35362[/url]
View this thread: [url]http://forums.techarena.in/showthread.php?t=662676[/url]

[url]http://forums.techarena.in[/url]