SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).

We are getting this error in event viewer on one of our SQL 2000 servers:

SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).

The SQL Server itself is running fine, but the SQLServerAgent refuses to start.

The logon credentials are set to log on as the local administrator, which has logon as service rights, this is the same account that the sql logs in with, so confirmed it's ok.

Any ideas where to even start on this one??

Urgent, hence 500 points.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

I've got to post the obvious question incase it is something as daft as it. Did the local admin password get changed? can you log into that box using it to check the password stored in the service config matches that current password.

EncamsAuthor Commented:
Hi there.

All confirmed, admin passwords correct.

Stopped the MSSQLServer service, edited the logon account, retyped password, restarted service, all ok!
The agent service is a different service to the MSSQLServer service, did you check the agent one?

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
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

EncamsAuthor Commented:

The SQL server didn't have a login for the local administrator. Created one, problem solved!

Thanks again,
I'm having a similar issue but just recently changed my password on my network account and now the sqlserveragent will not stay started.  It will start then stop just as described above.  
I am having this problem guys right now...I have done the above and the sqlserveragent still will not start up.

SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start)
I got it to work by applying a sql service pack.   On my local pc I was running an older service pack.   The admin account was fine but I couldn't correct the issue until I installed the service pack and it work fine after that.  

I had researched online and found it was a bug for sql2000 in order svc packs.   I would be on 2005 but other company reasons keep me from moving to 2005 or 2008.  
I figured mine out late last night.  In the SQL server Network Utility, the box 'Force Protocol Encryption' was checked.  Checking this box does not allow for the agent service to start.  I unchecked it and the service started.
I solved the same problem this morning.
I changed my "sa" password and I received this issue after rebooting server.

Procedure :

In Enterprise Manager
Go to Management
SQL Server Agent
Right Click on this item
Properties > Connexion tab
Change password for SA login.


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 SQL Server

From novice to tech pro — start learning today.