Link to home
Start Free TrialLog in
Avatar of loaganathan
loaganathanFlag for India

asked on

task scheduler service not starting in windows server 2003

hi
i am having two node windows cluster for database failover.scheduled some batch file to start using the windows task scheduler but in one of my cluster node am not able to start the task scheduler service it states an error while starting "  error code 1075 in task scheduler  The dependency service does not exist or has been marked for deletion"

task scheduler is working fine in another cluster node

please help me out with this
ASKER CERTIFIED SOLUTION
Avatar of arnold
arnold
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of loaganathan

ASKER

hi arnold
 
 restarted the node .but i am  getting the same error not able to start the task scheduler service in passive node
and one think i want to inform you i manually failover the cluster to another node in that node task scheduler is working fine

and i found that dependency services for task scheduler are cluster service and RPC services

but in another node where the task scheduler is not starting found only RPC services as dependency

please advice me on this
You can edit the registry HKLM\system\currentcontrolset\services\servicename
http://www.itq.nl/blogs/post/Removing-dependencies-from-a-Windows-service.aspx

Alternatively, use cluster admin on the passive node and connect to the local cluster (.)
Then see whether you can separate the service from being part of the cluster configuration.

This may have been an error during configuration where this resource was tied to the cluster, but then the cluster was deleted and a new one setup. Or it is still defined but inoperative.
still the issue has not resolved.could you please suggest anyother solution
What has been attempted, rebooted, and readied the service?
we have rebooted  and readded the service but the same error persist
Was access using cluadmin (.) ?
Did you using regedit remove the dependency reference to the cluster?