May 10, 2006 at 10:31 am
Hi Guru,
I'm sick of trouleshoot one of my sql box that the sqlagent can't started. Here is the message:
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start)
From enterprise manager on the server itself, I am able to register the server by supplying the server name. However, when I tried to register with the (local), I was never able to do so.
I also tried to restart the SQL agent with localsystem, domain and local admin accounts none of them can start the service. These accounts are local admin to the box and have complete sysdmin rights to sql server. From query analyzer, these accounts can connect to server with blank, LocalHost, (local), and period. So, this tells me that the server does not experience of resolving (local) connection.
I tried to log on to the server with both local and domain accounts to start agent but nothing is good for me. I tried to change startup account from enterprise manager to make sure security is in synch but still the same.
However, the last thing that I’ve not done is reboot the OS.
Please help,
Thanks,
Silaphet,
May 10, 2006 at 12:16 pm
Couple of things need to check.
1> make sure SQL SERVER Services & Agents runs under Domain Account.
2> Exit out Service Manager & start again from Start--Proram....
3> BUILTIN\Administrators account is there in SQL Server. check to see if The BUILTIN\Administrators login does not have access to sql server or the BUILTIN\Administrators login has been removed. I don't know if access is removed for BUILTIN\Administrators. this also cause your agent not to run.
4> if you have recently installed SP-4, then re-install again.
5> Check the services & see how SQL Agent account is configure, as it may have changed or some body might have changed.
6> disabling your anti-virus for testing purpose.
7> Check the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server\Driver
It should be pointing to c:\[Windows folder]\system32\SQLSRV32.dll
8> you may have a problem resolving Localhost or (local) or . (that's a period, btw). You might want to check for rogue DSN's (Administrative Tools, DataSource Administrator). Check System and User DSN's.
I hope this will help.
May 10, 2006 at 2:10 pm
May 11, 2006 at 1:56 am
Hi, we have a similar problem under windows 2000 sp4 with SQL Server standard sp4 onto a muti processor server.
The problem was due to a server option under processor tab -> "Use NT Fiber". After unchecking this option and restarting SQL Server, SQL Server agent start correctly.
Hope it will help you.
Fred.
May 12, 2006 at 8:18 am
Fred,
We never ever touched server configurations. The server runs on thread mode not fiber mode. The NT Fiber option is unchecked. I don't think this is the case.
Any ideas?
Thanks,
Silaphet,
January 26, 2010 at 1:01 am
Nothing mentioned above helped. still agent is in stopped state. 🙁
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply