May 9, 2005 at 3:48 pm
I am working on a test install of SQL Server 2000 SP 3a and am encountering a problem with SQLServerAgent. If I right click on SQL Server Agent in Enterprise Manager, "start" is grayed out which should indicate that the SQL Server Agent has started successfully. If I go to Administrative Tools, Services it shows SQL Server Agent as started. Yet, if I try to start a job from either the server itself or my workstation I get the message: Error 22022: SQLServerAgent is not currently running so it cannot be notified of this action.
I have already tried an uninstall and reinstall but there was no change. The SQL Server Agent service starts with a defined user account that has Administrator privileges (which is how I've set up the 15+ other servers I am responsible for). I've never run into this type of issue so I'm at a loss of what to investigate next. Any help or ideas would be much appreciated.
May 9, 2005 at 4:25 pm
Hi,
I had similar problem once long time ago. It was related to the services startup sequence. I am not even sure now what version it was: 2000 or 7.0 The problem manifested itself that Agent would start starting and then it was waiting for something else to finish it startup, something like that. Agent ended up being in a state that it was half-started and both Start and Stop buttons in Services were grayed out. What I did as a temp measure was to disable autostart for the service and restart the machine. I don't remember how did I fix the cause of the problem, anyway it will be different in your case.
I would check Event log what is going on during services startup.
Yelena
Regards,Yelena Varsha
May 9, 2005 at 4:42 pm
Hi,
Found my records! One of the cases did happen after SP3 install! Here are my records from Jan. 2003:
"..... <user name> had trouble starting SQL Server Agent on <server name> since he installed SP3 to SQL Server 1/27/2003 at 11:10 AM. It told him that the service was disabled or non-existent.....I could not start it too at the beginning with the same message. The service was set to automatic in the Services control panel. There was no SQL Agent logs or records in the event log after the time of the SP3 application. I suspected that maybe the service was disabled by someone previously <to SP3 application> and I set it to disabled again and then to automatic again. It started normally after that....."
Yelena
Regards,Yelena Varsha
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply