November 4, 2009 at 6:33 am
Hi,
Machine Configuration : Sql server 2005 with SP2, OS : windows server 2K
In last couple of days , Sql server agent (services ) got stopped unexpectedly
nobody has done anything, while see through naked eyes , i couldnt find anything specific to that stop.
We have "restart sql server agent when unexpectedly stops" option ON
can any one , help me in it.
Below is the pasted log
----------------------------------------------------------------------------
Date,Source,Severity,Message
10/26/2009 12:20:23,,Warning,[098] SQLServerAgent terminated (forcefully)
10/26/2009 12:20:23,,Error,[359] The local host server is not running
10/26/2009 12:20:22,,Error,[359] The local host server is not running
10/26/2009 12:20:22,,Warning,[188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
10/26/2009 12:20:06,,Error,[359] The local host server is not running
10/26/2009 12:20:06,,Error,[359] The local host server is not running
10/26/2009 12:20:06,,Error,[359] The local host server is not running
10/26/2009 12:20:06,,Warning,[360] SQLServerAgent initiating shutdown following MSSQL$REPORT_DEV shutdown
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateJobActivity_NextScheduledRunDate)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateJobActivity_NextScheduledRunDate)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateJobActivity_NextScheduledRunDate)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (JobManager)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:20:02,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateStartExecutionDate)
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005<c/> this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Communication link failure [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[298] SQLServer Error: 233<c/> Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> Client unable to establish connection due to prelogin failure [SQLSTATE 08001]
10/26/2009 12:20:02,,Error,[165] ODBC Error: 0<c/> Client unable to establish connection due to prelogin failure [SQLSTATE 08001]
10/26/2009 12:20:01,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateStartExecutionDate)
10/26/2009 12:20:01,,Error,[165] ODBC Error: 0<c/> Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000]
10/26/2009 12:20:01,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateStartExecutionDate)
10/26/2009 12:19:03,,Error,[382] Logon to server 'intechdba' failed (ConnAttemptCachableOp)
10/26/2009 12:19:01,,Error,[382] Logon to server 'intechdba' failed (JobManager)
10/26/2009 12:19:01,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateStartExecutionDate)
10/26/2009 12:18:04,,Error,[382] Logon to server 'intechdba' failed (ConnUpdateStartExecutionDate)
10/23/2009 01:20:52,,Warning,[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
10/23/2009 01:20:52,,Warning,[260] Unable to start mail session (reason: No mail profile defined)
10/23/2009 01:20:52,,Information,[129] SQLAgent$REPORT_DEV starting under Windows NT service control
10/23/2009 01:20:52,,Error,[364] The Messenger service has not been started - NetSend notifications will not be sent
10/23/2009 01:20:51,,Information,[432] There are 11 subsystems in the subsystems cache
10/23/2009 01:20:47,,Information,[339] Local computer is intechdba running Windows NT 5.2 (3790) Service Pack 2
10/23/2009 01:20:47,,Information,[310] 4 processor(s) and 6142 MB RAM detected
10/23/2009 01:20:47,,Information,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is intechdba
10/23/2009 01:20:47,,Information,[102] SQL Server ODBC driver version 9.00.4035
10/23/2009 01:20:47,,Information,[101] SQL Server intechdba version 9.00.4262 (0 connection limit)
10/23/2009 01:20:47,,Information,[100] Microsoft SQLServerAgent version 9.00.4262.00 ((Unknown) unicode retail build) : Process ID 4136
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
November 4, 2009 at 10:59 am
Bhuvnesh (11/4/2009)
10/26/2009 12:20:06,,Warning,[360] SQLServerAgent initiating shutdown following MSSQL$REPORT_DEV shutdown
looks like someone pressed stop on your sql server to me 🙂
November 4, 2009 at 3:03 pm
I agree. It looks like someone stopped the service manually. Is there an event in the system log that states when the log was turned off? You may be able to find out who was on the server at the time (possibly thorugh the security log if it is being audited).
Joie Andrew
"Since 1982"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply