(adding this message to the correct thread)
The usual suspects are the registry settings or the file permissions.
You could use Process Monitor and see if you find an status Access Denieds
in it why trying to start the service.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
You could also check the permissions on the files themselves.
Start a command prompt as administrator and repeat for each evtx file.
cd %SystemRoot%\System32\Winevt\Logs
cacls system.evtx
If it doesn't look like this, then it's been modified from the default.
C:\Windows\System32\winevt\Logs\System.evtx
NT SERVICE\Eventlog

ID)F
NT AUTHORITY\SYSTEM

ID)F
BUILTIN\Administrators

ID)F
However, there could be other files locations that are in correct as well
like.
C:\Windows\ServiceProfiles\LocalService\AppData\Local
If the permissions are incorrect, you could change it back manually or use
the command in this KB article.
How to reset security settings back to the defaults
http://support.microsoft.com/kb/313222
Good Luck,
John
--
Speaking for myself only.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Speaking for myself only.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Julian said:
One other bit of info...
Checking the properties of the service, it is set to Log On as Local
Service...but unlike other services of the same type the Log On tab is
entirely greyed out... (i.e. can't change how it logs on) - that doesn't
seem right somehow...