SQL Server Agent Stops Unexpectedly and does not restart
I am running SQL Server 2008 (10.0.2531) 32 bit on a 4 CPU Dual Core HP Server with 64GB of RAM. AWE is enabled.
The SQL Server Agent service is running under a purpose designed Network account and is set to
auto-restart on first failure, auto-restart on second failure and restart the whole server on third failure.
Just before the SQL Agent stops, the error log provides the following error messages:
Messages:
1.[298] SQLServer Error: 258, TCP Provider: Timeout error [258]. [SQLSTATE 08001]
2.[165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
3.[298] SQLServer Error: 258, Unable to complete login process due to delay in prelogin response [SQLSTATE 08001]
4.[382] Logon to server '(local)' failed (SubSystemStepHistoryLogge
and then nothing, until the server is restarted manually.
The windows event logs provide no help.
The SQL Server Agent service is running under a purpose designed Network account and is set to
auto-restart on first failure, auto-restart on second failure and restart the whole server on third failure.
Just before the SQL Agent stops, the error log provides the following error messages:
Messages:
1.[298] SQLServer Error: 258, TCP Provider: Timeout error [258]. [SQLSTATE 08001]
2.[165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
3.[298] SQLServer Error: 258, Unable to complete login process due to delay in prelogin response [SQLSTATE 08001]
4.[382] Logon to server '(local)' failed (SubSystemStepHistoryLogge
and then nothing, until the server is restarted manually.
The windows event logs provide no help.
SOLUTION
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What happens when you set the SQL Agent svc to run as a domain account?
ASKER
To clarify my original statement, the SQL Agent Service is running as a Domain Account.
Does this domain account have "log on as a service" rights on that server?
ASKER
Yes the Domain Account has 'Log on as a Service" rights on this server. Further investigation has thrown up the following possible cause for my problem. The MSDB Database, which contains all of the jobs for this server resides on the server's local drive. All of the production databases reside on SAN drives. The local drive began to run out of space. Because the SQL Agent relies on MSDB, there appeared to be no room for the database log to expand. This seems to have the flow on effect that SQL Agent cannot continue its work until more space is available. As soon as some space had been freed on the local drive, the SQL Agent seemed to work properly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Logging is set to SIMPLE. I think the problem is that the drive is just too small. I will be mivng the MSDB database to a larger drive to see if this alleviates the problem more permanently.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will do what you suggest and see if it does enough to alleviate the problem.
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
ASKER