Killed SPs and sqlserveragent stop working
-
We had a lot user connections with 'sleeping' mode in sysprocesses. I killed them with the status='sleeping', I realized that i might also killed some connections are not supposed to be killed.
After that, I checked event viewer, I saw 'Unable to read local eventlog (reason: The data area passed to a system call is too small). '
When I restarted the sqlserveragent service, I got'Could not start SQLserverAgent Service on local computer. The service did not return an error. This could be an internal Windows error or an internal service error. If this error persists, contact your system administrator. ' and also the following message appears in Application log '
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role). '
-
Did you try restarting the SQL service, not just the agent?
-
Did any passwords since the last time the agent service was started? You may want to check and see how SQL Server is trying to log in and what permissions it has.
"Keep Your Stick On the Ice" ..Red Green -
Tyang, you should not kill all processes that have status 'sleeping'! Some is using by SQL Server itself and used only when some events triggered.
If you insist to kill the processes, try to add one more condition - uid = 0
Regards,
kokyan 
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply