Working through the recycling of the services on server, changing the accounts for Sharepoint Timer Service, I found myself in the interesting situation of not being able to start the service.It worked , it was started but it’s not working now and it is not starting so I think it’s worth mentioning. Just in case.
The message I am talking about is:
“Could not start the Windows Sharepoint Services Timer on Local Computer
Error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it”
Researching the Internet for this message in relationship with Sharepoint revealed nothing.
The second error message I think might give you a hint that your service is in this state you will receive when you will try to run
stsadm -o updatefarmcredentials :
Error provisioning the local timer service instance during deploying of administration application pool credentials, please provision manually. Cannot start service SPTimerV3 on computer ‘.’.
Trying to run stsadm -o provisionservice -action start -servicetype SPTimerV3 will result in the next message:
The Service name and type specified are not valid. The service may not be installed or may not have been specified with the name space or assembly qualified name,which is case sensitive and required for services not in Sharepoint. additional information….
Well enough with the errors.
The resolution is actually very simple and documented in the http://support.microsoft.com/kb/241584 article , which applies to ANY Windows service.
Here are the steps:
Open the services console, double click the service that presents the error, go to the log on tab and check if the hardware profile defined for the service is enabled.
Most probably it isn’t .Enable it and launch !
So far I haven’t been able to detect WHY or HOW did the how profile ended up as disabled but since the service runs, I will not investigate any more time in this quest.However just to clarify why is this important I will only tell that if ho hardware profile is enabled, the service will not have access to the hardware system resources, such as , well, memory, or processor instructions.