August 19, 2012 at 1:20 am
The agent service is configured to use a service account, as is SQL server itself. SQL starts just fine so I doubt it's a permissions issue. The only way I can get the agent to start is use the Local System account, which I can't do for several reasons the most important of which is replication.
When I attempt to start it in the config manager I get "The request failed or the service did not respond in a timely fashion. Consult the event log..."
Event logs tell me not much:
Timeout (60000 milliseconds) waiting for the SQL Server Agent (MSSQLSERVER) service to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.%5B/quote%5D
except it doesn't look like it's taking 60 seconds. I timed it at about 40 seconds before it reports it failed.
There are no entries in SQLAGENT.OUT when it starts. I'm stumped. I think something is dying in the windows system before it even gets to SQL, but I don't know how to prove it, find it, or fix it. Does anyone have any ideas.
August 20, 2012 at 4:24 am
The password on the Agent account may have been changed
August 20, 2012 at 6:00 am
Information is power as they say.
Check the Windows and SQL logs in detail to see if any evidence is offered.
Have you tried assigning Service to the AUTHORITY\NetworkService account and see if starts?
:exclamation: "Be brave. Take risks. Nothing can substitute experience." :exclamation:
August 20, 2012 at 6:08 am
There are no entries in SQLAGENT.OUT when it starts.
Do you mean there is no file created, or that a blank file is created? Check that the location for the file exists (you may have to look in the registry to find the location) and that the SQL Server Agent service accounts has permissions on it. When you change the service account, you do use SQL Server Configuration Manager (and not the Services applet), don't you?
John
August 20, 2012 at 8:00 am
It's using the same username/pass as the SQL server itself which starts. Not a password issue.
August 20, 2012 at 8:03 am
event logs say:
Timeout (60000 milliseconds) waiting for the SQL Server Agent (MSSQLSERVER) service to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
even though it doesn't attempt to start for 60 seconds (42 by my watch) and SQLAGENT.OUT isn't updated at all when I attempt to start it.
It's definitely not getting past windows. But whatever it is windows is keeping it to itself.
August 20, 2012 at 8:05 am
If you create a new domain account for testing, can you use that and get it to start?
This sounds like it might be some strange permissions error, so I'm looking for another account that might reset something.
August 20, 2012 at 8:11 am
File exists. It was working fine until the last reboot. However it's not updated when you attempt to run it using the network account. If I switch it to Local System it starts, but I can't run it that way. Here's a typical log for that situation:
2012-08-19 03:01:07 - ? [100] Microsoft SQLServerAgent version 9.00.5000.00 ((Unknown) unicode retail build) : Process ID 6016
2012-08-19 03:01:07 - ? [101] SQL Server servername version 9.00.5057 (0 connection limit)
2012-08-19 03:01:07 - ? [102] SQL Server ODBC driver version 9.00.5000
2012-08-19 03:01:07 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
2012-08-19 03:01:07 - ? [310] 4 processor(s) and 16381 MB RAM detected
2012-08-19 03:01:07 - ? [339] Local computer is servername running Windows NT 5.2 (3790) Service Pack 2
2012-08-19 03:01:08 - ? [432] There are 11 subsystems in the subsystems cache
2012-08-19 03:01:13 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2012-08-19 03:01:13 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2012-08-19 03:01:13 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2012-08-19 03:01:17 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2012-08-19 03:01:30 - ? [098] SQLServerAgent terminated (normally)
all starts and stops, user assignment, is being performed in SCM.
August 20, 2012 at 8:13 am
Sorry missed the last statement. Now this is weird. "The process terminated unexpectedly." when I attempt to use Network Service.
August 20, 2012 at 8:20 am
OK, so it works under Local System, which means it can't be pointing at the wrong location. I'm still guessing that whatever service account you are using doesn't have the correct permissions on the location. Now this is strange given that you are indeed using SQL Server Configuration Manager to change service accounts. Maybe something else is overriding the permissions. Please check what permissions the service account has on the folder that SQLAGENT.OUT is in, and that there are no overriding DENYs that could be preventing access.
John
August 20, 2012 at 8:43 am
I just tried a new password and a new user. So bad password yields bad password message. So far so good.
Another user, same thing. 🙁
August 20, 2012 at 8:48 am
The service account is a local admin. Full permission to the LOG folder.
August 20, 2012 at 8:59 am
In that case, I'm stuck. I would recommend that you get hold of a utility by Microsoft (I think it's called sysinternals) and run it while you're attempting to start the service. It logs everything that goes on behind the scenes.
John
August 20, 2012 at 9:01 am
Yeah I think we're going to open a ticket with MS. Thanks all for your input. If anyone has any other ideas I'm all ears, but I'll report back with what I hear.
August 20, 2012 at 5:05 pm
so far our MS guy is as stumped as I so that makes me feel a little better, but I thought I'd share a stopgap solution:
She starts in the command prompt. When I start the agent in the command prompt, as the same service user (interactive logon enabled to test) she starts just fine. All my replication jobs are happy, birds are chirping, angels sing, and my customers stop pelting me with rocks. So this is my temporary solution, while the real solution is investigated.
Hmmmm.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply