When I check msconfig, there are no services that are blocked from starting up.
When I look in services.msc, the problem services have a start up type of 'Automatic', but have a blank space where others will show 'Started'.
Attempting to start them manually results in the following pop up error messages.
I have no idea what's causing this, looks like some sort of cascade effect from another problem service. It's affecting scheduled tasks, SQL server agent and windows back up services.
How can I resolve this? I don't know how to work out what the root cause is.
Task Scheduler Service Start Error:
"Windows could not start the Task Scheduler service on local computer. 1068: The dependecy service or group failed to start.
SQL Server Service Start Error:
"The SQL Server Agent service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
UPDATE:
I've just noticed some other services have a description of "Failed to Read Description. Error Code: 2"
They are:
NetMsmqActivator,
NetPipeActivator,
NetTcpActivator,
NetTcpPortSharing
UPDATE 2: As joeqwerty says the Event Log service does seem to be the root of the problem. This service will not start either.
It fails with 'Error 31 – A device attached to the system is not functioning correctly'.
I've tried detaching all devices.
I've also followed the advice here, where the same problem is described, but with no luck:
Update 3
@ Pacey – The following was a good tip, really clear instruction. However, I found that those reg keys do not exist on my system.
"Your Problem might also derive from the UpperFilter or LowerFilter Settings of the CDROM Drive. These are a known cause for Errorcode 31. You can find step-by-step instructions on removing the filters on about.com"
I followed the advice through to checking every component in device manager separately, but everything is reported as working correctly!?
These services did all work at one point. The hardware set up hasn't changed much.
Guess I'm looking at a repair install maybe???!
Best Answer
The most common cause is obviously that a service or servicegroup that is needed for task-scheduler failed to start.
So first thing you would like to check is which dependencies have beeon configured for the Task-Scheduler.
In CMD:
In Powershell:
The Schedule Service (afaik) depends on 2 services. The EventLog and the RPCSS. So if your scheduler has other dependencies try to set them back to default by issuing:
Your Problem might also derive from the UpperFilter or LowerFilter Settings of the CDROM Drive. These are a known cause for Errorcode 31. You can find step-by-step instructions on removing the filters on about.com
If this doesn't work I would suggest running
to check whether there are system files that have been corrupted.