Post1:
The 1067 error is a general error meaning that a service has failed to start. I would check your event log to see if there is further information there, and also in the SQL log. Also, try starting the SQL Agent service from the command prompt with the -v switch to display the output to the diag screen.

also experienced had a similar error while running SQL2005 SP2. We did receive an error 1067 when manually restarting it via the services snapin.

Turns out Microsoft dot net framework 2.0 was corrupted. This was only determined while trying to repair the SQL install and received a prompt regarding dot net 2.0. So we cancelled the SQL repair and instead repaired the .Net 2.0 installation. Rebooted and SQL agent started automatically. Hope this helps.

Why is this different from all of the other step by step guides? Because I make a living as a DBA and not as a writer and I lived through this experience.
Defining the name:
When I talk to people they say different names on this subject stuff l…

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…