SQLSERVERAGENT Service Problem [:(]
-
I use MSSQL Server. I let SQL Server Agent to "Autostart when OS starts". The problem is that when I have to restart the server , the agent doesn't start and I get the famous message "At least on of your services ..."
Subsequently, Once I check NT's event log , I see the error "SQLSERVERAGENT service hung on starting." What do you think of it?
Your,
Amir
-
Have you researched the code from the event log? Can you start the agent manually once the SQL Service starts? You should check the account name and password used for the agent. Anything in the SQL error log?
Andy
-
Andy,
At first thank you to answer me. Then , about your question:
1. Yes , I can start it manually , without any chage in the account name and password used for the agent or getting any error.
2. The error ID in the NT Event viewer-sysyten is 7022. And there's other error in Applicatn section of Event Viewer as "SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start)." with error ID as 103.
3. There's nothing in the SQL error log.
Amir
-
Have you changed any security settings within SQL Server?
Do SQLServer and SQL Agent run under the same account?
Steve Jones
-
I couldnt find anything relevant on MSDN or Google. Given that it works when you try it manually, my guess is that your SQL service is slow starting and it has to be running fully for the agent service to start. For a work around, you might want to modify the service for the agent to retry a couple times before failing.
Other than that, can you determine when the problem started - maybe tie it to another change that was made?
If you're not running the most recent service packs, I'd suggest you consider applying those (with usual cautions of course).
Andy
-
Steve,
1. No , I haven't chaged the security settings.
2. Yes , they run under the same account.
Andy,
Which Service Pack do I need for SQL Server 2000 Enterprise Edition?
Anyway, thank you both for your help.
Amir
-
Look under the connection tab in the SQL Server Agent properties. Verify that that the acccount that is selected is a valid SQL Server login. If you ever change the password that this screen uses, it will bomb.
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars -
I am currently running SP1 with no issues. I doubt that applying it will fix this particular problem, but you should plan (and test) to apply it.
Andy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply