event log service does not start - "Error 1053: The service did not respond..."

Noone of the .evt files has a read only flag set. Only the 'Archive'-flag like most files in the ...\config directory

The task sheduler gives the Error 1717: The interface is unknown

The event log the 1053

I wanted to try to tackle the 1717 first but according to http://support.microsoft.com/kb/915156 I need to get event log running first...

So I'm back to start...

Later I thought that if your "nice vbs script" did something to the Event Log files (like make then read only), that might also give you a 1053 since the Task Scheduler Service needs to also write to those files.

Take a look out here where the Event Log file are:

C:\windows\system32\config

All the files that end in .evt are the Event Log files.

Are any of them read only?  Nothing in that folder should be read only.

Y and Z

Thanks for your reaction!

There is nothing wrong with attributes of the  "c:\windows\SchedLgU.Txt", I have deleted it as well. Unfortunatly, I still can not start Task sheduler nor the Event logger.

My "nice vbs script" was just written this week and the task sheduler hasn't been running for months... I tried to get it working again because I want to use an OCS Inventory service which depends on the Event log...

X.

Maybe it was your "...nice vbs script which cleans the event-log" that did you in.

I will tell you what I know about the 1053 with Task Scheduler, and you might want to look at your Event Log files and be sure they are not suffering the same affliction if this is the case with you Task Scheduler:

When trying to start the Task Scheduler Service, it looks like it is very slowly trying to start (and struggling), and then after a while you see a message like this:

Services

Could not start the Task Scheduler service on Local Computer

Error 1053:  The service did not respond to the start up or control request in a timely fashion

One thing that can cause this error with Task Scheduler (and it gets stuck Starting) is if the Task Scheduler log file:

c:\windows\SchedLgU.Txt

is read only.  Perhaps the file also corrupted somehow.

Using Explorer, Navigate to the c:\windows folder and locate the SchedLgU.Txt file, right click it and check the Properties.  If the file is marked Read-only, uncheck that Attribute and click OK to save the changes.

You could also just delete the probably cluttered up SchedLgu.txt file unless you need it for something.

If your Task Scheduler Service is hung "Starting", you are going to have to reboot and then see if you can start the Task Scheduler Service and set the Properties Startup to Automatic.

When the Task Scheduler Service starts, if there is no log file, t will create a new log file but stuff will accumulate in if forever which can make troubleshooting Scheduled Tasks a tedious chore.

Y and Z