October 12, 2011 at 3:46 am
Hello All,
My name is Daniel and i'm new to SQL 🙂
We had a cluster failover due to MSSQL service terminating unexpectedly, I have goggled a few of the errors and come across this: http://support.microsoft.com/kb/909089 but I don’t think it relates as we are running MSSQL 2005 not 2000.
Operating system: 2003 R2 SP2, SQL 2005 9.0.4289,Xeon 3.8.0GHz, 8GB RAM.
SQL logs below:
EDIT.
Thanks,
Daniel 🙂
October 12, 2011 at 7:42 am
Did the server failover?
October 12, 2011 at 8:14 am
AlexSQLForums (10/12/2011)
Did the server failover?
It did indeed.
Thanks,
Dan,
October 12, 2011 at 8:46 am
check the cluster.log at the following location
C:\Windows\system32\cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2011 at 8:52 am
Perry Whittle (10/12/2011)
check the cluster.log at the following locationC:\Windows\system32\cluster
Hello,
I have a file called ClCfgSrv.log and a file called clusocm.log in Windows\system32\cluster, no sign of cluster.log.
Thanks,
Daniel.
October 12, 2011 at 8:58 am
daniel.b.handy (10/12/2011)
Perry Whittle (10/12/2011)
check the cluster.log at the following locationC:\Windows\system32\cluster
Hello,
I have a file called ClCfgSrv.log and a file called clusocm.log in C:\WINDOWS\system32\LogFiles\Cluster, no sign of cluster.log.
Thanks,
Daniel.
In addition, the two log files have not been modified since March this year.
Thanks,
Dan.
October 12, 2011 at 9:25 am
sorry, my bad.
check
C:\Windows\cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2011 at 9:45 am
Hi,
The logs don’t go back enough, on a side note, i found the following in the application log:
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:09
User:N/A
Computer:
Description:
A user request from the session with SPID 98 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17066
Date:29/09/2011
Time:16:56:10
User:
Computer:
Description:
SQL Server Assertion: File: <medutil.cpp>, line=2662 Failed Assertion = 'SOS_OK == res'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:12
User:N/A
Computer:
Description:
A user request from the session with SPID 106 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:15
User:N/A
Computer:
Description:
A user request from the session with SPID 100 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:17
User:N/A
Computer:
Description:
A user request from the session with SPID 82 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:29/09/2011
Time:16:56:18
User:
Computer:
Description:
SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related 0stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:19
User:N/A
Computer:
Description:
A user request from the session with SPID 85 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:20
User:N/A
Computer:
Description:
A user request from the session with SPID 107 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:21
User:N/A
Computer:
Description:
A user request from the session with SPID 76 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:1203
Date:29/09/2011
Time:16:56:21
User:
Computer:
Description:
Process ID 68 attempted to unlock a resource it does not own: METADATA: database_id = 32767 SCHEMA(schema_id = 4). Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:3624
Date:29/09/2011
Time:16:56:21
User:
Computer:
Description:
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:23
User:N/A
Computer:
Description:
A user request from the session with SPID 92 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17310
Date:29/09/2011
Time:16:56:25
User:N/A
Computer:
Description:
A user request from the session with SPID 99 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:31
User:N/A
Computer:
Description:
[sqsrvres] CheckServiceAlive: Service is dead
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:31
User:N/A
Computer:
Description:
[sqsrvres] CheckServiceAlive: Service is dead
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:31
User:N/A
Computer:
Description:
[sqsrvres] CheckServiceAlive: Service is dead
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:31
User:N/A
Computer:
Description:
[sqsrvres] OnlineThread: service stopped while waiting for QP.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:32
User:N/A
Computer:
Description:
[sqsrvres] OnlineThread: Error 1 bringing resource online.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:36
User:N/A
Computer:
Description:
[sqsrvres] CheckServiceAlive: Service is dead
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:29/09/2011
Time:16:56:53
User:N/A
Computer:
Description:
[sqsrvres] CheckServiceAlive: Service is dead
October 12, 2011 at 12:38 pm
daniel.b.handy (10/12/2011)
Hi,The logs don’t go back enough, on a side note, i found the following in the application log:
There is only 1 log, its called cluster.log
This details cluster failure events
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2011 at 5:43 pm
Do you have enough space on the C:\ drive
October 13, 2011 at 3:03 am
R_S (10/12/2011)
Do you have enough space on the C:\ drive
Hi,
Yes, plenty.
Thanks,
Dan 🙂
October 13, 2011 at 3:04 am
Perry Whittle (10/12/2011)
daniel.b.handy (10/12/2011)
Hi,The logs don’t go back enough, on a side note, i found the following in the application log:
There is only 1 log, its called cluster.log
This details cluster failure events
Hi,
Yes I found the log, but it does not go back in time far enough, the incident happened on the 29/09/11.
Thanks,
Dan.
October 13, 2011 at 3:09 am
just out of interest, why are you worrying about an event that happened 2 weeks ago. Why did you not tackle this at that time
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 13, 2011 at 3:15 am
Perry Whittle (10/13/2011)
just out of interest, why are you worrying about an event that happened 2 weeks ago. Why did you not tackle this at that time
Incident management deals with getting the service backup and running ASAP, Problem Management (me) deals with finding the root cause and a resolution to ensure we don’t experience the incident again.
🙂
October 13, 2011 at 3:17 am
but you should gather all details immediately as logs will not last for ever as you have found out.
Next time you have an issue take a copy of the cluster.log
Do you have a week old or so backup of the server, you may be able to extract the log from there
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply