December 15, 2006 at 8:14 am
Has anyone had a problem with SQLServerAgent failing to start on reboot with the following error
2006-12-14 00:40:23 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2006-12-14 00:40:23 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2006-12-14 00:40:24 - ? [098] SQLServerAgent terminated (normally)
All I have to do is start the service manually and it comes up fine. Its as though the SQLServer service is started but its not actually accepting any connections.
December 15, 2006 at 8:22 am
Did you recently change the password on the account that you are using to start the SQL Server Agent?
When you say "start the service manually" do you mean within Services? and not within Enterprise Manager?
December 15, 2006 at 8:45 am
Hi,
I think that you have recently change the SA password. Tried this solution and I hope that it will slove your problem.
Right click on SQL Agent from SQL Enterprise Manager and select Properties
Click on the "Connection Tab" and select "Use SQL SERVER , Authentication" and
use "SA" for "SystemAdmin Login ID" and specify the password below.
cheers
December 15, 2006 at 10:53 am
Go to Services, find the SQL Server Agent Service. Right click on it and go to Properties. Click on Dependencies tab. The agent service should depend on the MSSQLServer service. If it doesn't, someone deleted the dependancy. That means it is trying to come up before the MSSQLServer service is started and that won't work.
-SQLBill
December 15, 2006 at 11:34 am
YEs, by "Start Manually" I mean that I started it from the Services applet.
There have not been any changes to the 'sa' password or the service account logins that SQLServerAgent or MSSQLServer use.
The dependency MSSQLServer is still present. In fact the SQLServer error log indicates that it has started prior to the SQLServerAgent attempting to start.
December 15, 2006 at 11:39 am
OK thanks for the answers...
Next question, what type of account are you using to start SQL Server Agent? Is it the same account that is used to start the SQL Service? If not, I would try to start the sql agent service with the same account that is used to start the server service as a test...
Leeland
December 15, 2006 at 11:51 am
They both use the same account, not localsystem, to start.
December 15, 2006 at 12:00 pm
What is the domain\account that is used to log into the server ? (Is it the same account that is used to start both services ?)
Under SQL Server Agent -->Properties-->Connection
What do you have the SQL Server Connection listed as?
December 15, 2006 at 12:11 pm
They both use the the same domain\account to authenticate. It is an account created specifically for these 2 services.
It is the default instance of SQL Server.
We use Windows Authentication for the SQL Server Agent Connection.
This is not a consistent problem, only sporadic. I have close to 2500 sql servers deployed. Whenever we reboot a couple hundred to install MS Patches this problem affects roughly a 1/3 of them, and not always the same 1/3.
December 15, 2006 at 12:27 pm
To state the obvious here....
So you stated that you can go into services and manually start the service...but when you go into EM, and attempt to start the service it pukes on you. Correct?
What does the Display Error Log for the SQL Server Agent display when you select Information for the type?
And another obvious question (sorry). Have you stopped the sql server agent service, and re-entered the password for the account and then attempted to restart the service IN BOTH EM and within the Services menu?
December 15, 2006 at 12:33 pm
It doesn't matter where I manually start it from, Services applet or EM, it starts up just fine.
The first bit from the begining of the post is the total contents of the Agent log for the session that failed to start.
2006-12-14 00:40:23 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2006-12-14 00:40:23 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2006-12-14 00:40:24 - ? [098] SQLServerAgent terminated (normally)
I haven't re-entered the password because it never fails to start for me when I try to start it manually, in either location. It is only on reboot that this seems to be a problem.
December 15, 2006 at 12:36 pm
That sounds like you have tried everything I could think of...last thing I could think of is what SP level are the SQL boxes and what Version? Sorry I am not much help to you...sounds like you have your bases covered.
December 15, 2006 at 12:48 pm
SQL2000 on Sp3
I was afraid of that.
Its got to be something funky with our server build, I just hate to open a PSS call on something like this. I'm sure I won't be able to reproduce the problem on demand. Just like taking your car to the mechanic.
December 15, 2006 at 12:57 pm
Is there a reason that you cannot go to SP4? Do you have any Servers that are SP4 SQL 2000 that have this issue?
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply