How do I get Task Scheduler to start since it is in a "starting" status

Over the weekend, I upgraded a 2 cluster node with Microsoft patches. I upgraded the inactive node first, rebooted, made sure the cluster server was started. I moved the groups to the already upgraded server, stopped the cluster service on the second node and upgraded with patches and made sure the cluster service was running. I moved the groups back to the second node making it the active node. I checked the event log and found nothing suspicious for issues. Being the first time I have patched a cluster, I did not know there was a group of scheduled tasks running on the active cluster. These tasks did not start and we found the Task Scheduler service in a "starting" status and you can't stop or start the service. We rebooted the active node and of course the cluster groups moved to the inactive node. We found the tasks residing on the inactive node. We moved the groups back to the active node once the reboot completed. We then rebooted the inactive node and shortly after the reboot completed the scheduled tasks moved back to the active node where they should be. Nothing is happening since the scheduled tasks service is still in a "starting" status. How do we fix this situation so that the the service gets started and our tasks run. We are currently running the tasks manually.
These are the patches I installed; KB961373, 967715, 960803, 959426, 958690, 958687, 956572, 923561, 952004, 960225 and 963027. This cluster has MoveIT Central on it.
Thanks
AE2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
Have you checked the account that the service is configured to run under?
http://support.microsoft.com/kb/223170 
0
AE2Author Commented:
Thanks for responding, but we figured it out. We changed the task sheduler to manual instead of automatic. We rebooted the active node to get the groups to move back to the inactive node. Once the reboot was complete, we moved the groups back. Once everything was online, we started the task scheduler and things started working again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DonNetwork AdministratorCommented:
Okie Dokie ;^D
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.