Simon D Richards (3/13/2013)
I know this is old, but I had a similar issue recently. It was a security issue. For whatever reason, the security was not propagated properly during install, I did the following to fix:Switched the account in windows services to a local system account.
Started SQL Agent
Stopped SQL Agent
Changed the service to my account in windows services
Started Agent.
Hope this helps anyone experiencing a similar issue.
I forgot to post that I resolved this issue.
If you switch to a local account, start and stop the SQL Agent and change the Domain Account it works.
I had a situation yesterday where I had to do that and it works.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/