ex_raise2 - SQL Restart

Question

Post reply

ex_raise2 - SQL Restart

RichB

SSCrazy Eights

Points: 9651
More actions
October 24, 2005 at 4:17 am

#111968

SQL Logs:

"ex_raise2 - No handler found for exception major 36 minor 24 severity
20 - Server terminating"
Followed by
"Problem creating stack dump file due to internal exception2005-10-23
16:52:23.71 spid2304 SQL Server Assertion: File:
<p:\sql\ums\inc\umslist.h>, line=317
Failed Assertion = 'el->m_next == 0'"
At this point Sql Server restarts...not good!
SQL2k sp3, win2kServer.
Any ideas? At all?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jo Pattyn SSC-Dedicated Points: 32350 More actions · Answer 1

not sure but this mentions ex_raise2

http://support.microsoft.com/kb/825225

solved in SP4

RichB SSCrazy Eights Points: 9651 More actions · Answer 2

aye, thanks, pretty sure this is something different tho.

Phil Parkin SSC Guru Points: 246977 More actions · Answer 3

Is this link relevant? Sounds like similar problems ...

http://www.dbforums.com/showthread.php?threadid=986743&perpage=15&pagenumber=1

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

ramesh-248220 SSC Enthusiast Points: 185 More actions · Answer 4

Hi,

Have you recently put SP4 and the hotfix (and AWE enabled)

I recently upgraded my production server and log shipping server with SP4 and hot fix 899761(but AWE is not enabled) I was getting the same errors after 2 days since I applied the SP4+hotfix.

Yesterday one of the log shipping job started failing and creating SQL Stack dumps. Opened a call with MS but in the mean time I dropped the logshippin and recreated it yesterday night and so far all good.

I am keeping an eye on the SQL logs as these Stack dump erros are written to the logs as well and it will show what the error may be in my case the SQL Stack dump has something like this.

* BEGIN STACK DUMP:

* 10/24/05 10:15:06 spid 57

*

* ex_raise2: Exception raised, major=34, minor=56, severity=21

*

* Input Buffer 382 bytes -

* RESTORE LOG [ABC] FROM DISK = N'D:\MSSQL\BACKUP\SQL_LogShippi

* ng\ABC_tlog_200510241000.TRN' WITH FILE=1, STANDBY=N'D:\MSSQL\BACKUP\LogShipping\ABC_200510241000.tuf'

I manually ran the restore of this log but still it failed and I ran DBCC checkDB on the master DB no errors.

RESTORE LOG [ABC] FROM DISK = N'D:\MSSQL\BACKUP\SQL4_LogShipping\ABC_tlog_200510241000.TRN' WITH FILE=1, STANDBY=N'D:\MSSQL\BACKUP\SQL_LogShipping\ABC_200510241000.tuf'

MS has asked me to see how I go once I recreate the log shipping as they reckon it may be that some indexes were built at the time of log backups(I have checked in my case this is not correct) and the log got corruputed.

But after creating the log shipping all is ok till now but MS has suggested that there are know post SP4 bugs

Cheers

Ramesh

RichB SSCrazy Eights Points: 9651 More actions · Answer 5

Cheers, but thats not it - good luck with yours tho!