Hi all,

Once I saw that a user was complaining about this same problem.

His SQL Server Agent service account was a local admin account. As his domain policy was changed and it was prohibited to use local accounts to start services, his SQL Server Agent raised this error.


To solve it, he used a Domain account for his SQL Server Agent service and it started working again.

I wrote this answer as a reference in future. Because I think formatting and installing from scratch is not a decent solution.