Link to home
Start Free TrialLog in
Avatar of Encams
Encams

asked on

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.
Avatar of drydenhogg
drydenhogg

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.

Avatar of Encams

ASKER

Hi there.

All confirmed, admin passwords correct.

Stopped the MSSQLServer service, edited the logon account, retyped password, restarted service, all ok!
ASKER CERTIFIED SOLUTION
Avatar of drydenhogg
drydenhogg

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Encams

ASKER

Doh!

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.
Hello,
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.

Regards
Guillaume