April 11, 2011 at 5:16 am
Hi All,
We have a SQL Server 2005 in production environment with Standard edition. Its in a clustered environment. We have 3 different instances of databases configured on this server. As a daily routine, I was checking the health of server and I did find that SQL Server agent service for one of the instance had been stopped. The database service for the same instance and database, agent services for other instances were running properly.
I tried to go through the logs and I could find the day before, It had been stopped abruptly and found the following series of logs in the event viewer:
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 8009030c; message = [Microsoft][SQL Native Client]SQL Network Interfaces: The logon attempt failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 8009030c; message = [Microsoft][SQL Native Client]Cannot generate SSPI context
[sqsrvres] CheckServiceAlive: Service is dead
[sqagtres] CheckServiceAlive: QueryServiceStatus failed (status 6).
[sqsrvres] OnlineThread: Error connecting to SQL Server.
Faulting application sqlagent90.exe, version 2005.90.4035.0, stamp 492b162d, faulting module kernel32.dll, version 5.2.3790.4480, stamp 49c51f0a, debug? 0, fault address 0x0000bef7.
I tried to start agent service but it failed and consequently it stopped database service as well.
It gave the following error:
"Unable to start service SQLAGENT$<instance_name> on server <server_name>.
The SQLAGENT$<instance_name> service on <server_name> started and then stopped."
Can anybody please tell me the reason behind the failure?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply