Fatal error exception after SP installation

Hello, I installed one week ago the last SQL SP on SQL 2k5 64 bit / Windows
2003 64 bit. The actual version 9.0.2047. Starting from that day the service
restart periodically (one time a day) because a fatal exception. The
application works well until unexpected shutdown. I tried to look at SQL log
and the log files... Most of them are like in chinese for me...
I had nothing of this before I installed the SP. Probably it is not directly
linked to SP, but I don't kow where to start from? Could it the memory (I
intend to upgrade to 9GB anyway...)
What I can see for instance is the SQL log and dump file:
2006-10-25 09:01:19.32 spid9s SQL Trace stopped. Trace ID = '2'. Login
Name = 'sa'.
2006-10-25 10:50:22.32 spid402 ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16, attempting to create symptom dump
2006-10-25 10:50:22.35 spid402 Using 'dbghelp.dll' version '4.0.5'
2006-10-25 10:50:23.91 spid402 **Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
2006-10-25 10:50:23.91 spid402 *
2006-10-25 10:50:23.91 spid402 * User initiated stack dump. This is not
a server exception dump.
2006-10-25 10:50:23.91 spid402 *
2006-10-25 10:50:23.94 spid402 ***Stack Dump being sent to C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump1347.txt
2006-10-25 10:50:23.94 spid402 *
*******************************************************************************
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * BEGIN STACK DUMP:
2006-10-25 10:50:23.94 spid402 * 10/25/06 10:50:23 spid 402
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * Input Buffer 510 bytes -
2006-10-25 10:50:23.94 spid402 * select doc.RefDoc,
RefDocDet_Manque = (select top 1 D.RefDoc
.....
2006-10-25 10:50:27.12 spid402 Error: 8624, Severity: 16, State: 116.
2006-10-25 10:50:27.12 spid402 Internal Query Processor Error: The query
processor could not produce a query plan. For more information, contact
Customer Support Services.
2006-10-25 10:50:34.04 spid402 ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16, attempting to create symptom dump
and in the dump file:
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.2047.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current time is 10:50:34 10/25/06.
4 Unknown CPU 9., 2205 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 96%
Total Physical = 4951 MB
Available Physical = 180 MB
Total Page File = 6629 MB
Available Page File = 1933 MB
Total Virtual = 8388607 MB
Available Virtual = 8383305 MB
**Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump1348.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 10/25/06 10:50:34 spid 402
*
* ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16
*
* Input Buffer 510 bytes -
* select doc.RefDoc, RefDocDet_Manque = (select top 1 D.RefDo
Thnaks in advance for any helpHi
Error 8624 is an internal SQL Server error so you may want to contact PSS.
Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
D.RefDoc...?
John
"Catalin NASTAC" wrote:
> Hello, I installed one week ago the last SQL SP on SQL 2k5 64 bit / Windows
> 2003 64 bit. The actual version 9.0.2047. Starting from that day the service
> restart periodically (one time a day) because a fatal exception. The
> application works well until unexpected shutdown. I tried to look at SQL log
> and the log files... Most of them are like in chinese for me...
> I had nothing of this before I installed the SP. Probably it is not directly
> linked to SP, but I don't kow where to start from? Could it the memory (I
> intend to upgrade to 9GB anyway...)
> What I can see for instance is the SQL log and dump file:
> 2006-10-25 09:01:19.32 spid9s SQL Trace stopped. Trace ID = '2'. Login
> Name = 'sa'.
> 2006-10-25 10:50:22.32 spid402 ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16, attempting to create symptom dump
> 2006-10-25 10:50:22.35 spid402 Using 'dbghelp.dll' version '4.0.5'
> 2006-10-25 10:50:23.91 spid402 **Dump thread - spid = 402, PSS => 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
> 2006-10-25 10:50:23.91 spid402 *
> 2006-10-25 10:50:23.91 spid402 * User initiated stack dump. This is not
> a server exception dump.
> 2006-10-25 10:50:23.91 spid402 *
> 2006-10-25 10:50:23.94 spid402 ***Stack Dump being sent to C:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump1347.txt
> 2006-10-25 10:50:23.94 spid402 *
> *******************************************************************************
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * BEGIN STACK DUMP:
> 2006-10-25 10:50:23.94 spid402 * 10/25/06 10:50:23 spid 402
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * Input Buffer 510 bytes -
> 2006-10-25 10:50:23.94 spid402 * select doc.RefDoc,
> RefDocDet_Manque = (select top 1 D.RefDoc
> .....
> 2006-10-25 10:50:27.12 spid402 Error: 8624, Severity: 16, State: 116.
> 2006-10-25 10:50:27.12 spid402 Internal Query Processor Error: The query
> processor could not produce a query plan. For more information, contact
> Customer Support Services.
> 2006-10-25 10:50:34.04 spid402 ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16, attempting to create symptom dump
>
> and in the dump file:
> =====================================================================> BugCheck Dump
> =====================================================================>
> This file is generated by Microsoft SQL Server
> version 9.00.2047.00
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
>
> Computer type is AT/AT COMPATIBLE.
> Current time is 10:50:34 10/25/06.
> 4 Unknown CPU 9., 2205 Mhz processor (s).
> Windows NT 5.2 Build 3790 CSD Service Pack 1.
>
> Memory
> MemoryLoad = 96%
> Total Physical = 4951 MB
> Available Physical = 180 MB
> Total Page File = 6629 MB
> Available Page File = 1933 MB
> Total Virtual = 8388607 MB
> Available Virtual = 8383305 MB
> **Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC => 0x00000000DEC8BF10
> *
> * User initiated stack dump. This is not a server exception dump.
> *
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump1348.txt
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/25/06 10:50:34 spid 402
> *
> * ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16
> *
> * Input Buffer 510 bytes -
> * select doc.RefDoc, RefDocDet_Manque = (select top 1 D.RefDo
>
>
> Thnaks in advance for any help|||That query is a script file that I execute occasionally. It worked without
problems and it makes no problem except that day.
But all the others fatal errors are generated not by file scripts, but by
stored procs. But it is not the same each time... For example in the next log
is stated dbo.ts3_clsAPI_Membres_Upt.
I will install today the patch kb918222 (buid 2153) to see if it will change
something...
I also verify all my SPs and views, functions to use ANSI_NULL ON
Another log file:
Memory
MemoryLoad = 94%
Total Physical = 4951 MB
Available Physical = 273 MB
Total Page File = 6629 MB
Available Page File = 1585 MB
Total Virtual = 8388607 MB
Available Virtual = 8383233 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 10/26/06 16:32:32 spid 61
*
*
* Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 000000016CBF3010
* Input Buffer 255 bytes -
* d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
* c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
* m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
* & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
* & §2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
* AVETSIAN §2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
* 2 Rousana §� 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
* 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
* APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
"John Bell" wrote:
> Hi
> Error 8624 is an internal SQL Server error so you may want to contact PSS.
> Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> D.RefDoc...?
> John
>|||Hi
If installing the hotfix does not cure this I would call PSS.
John
"Catalin NASTAC" wrote:
> That query is a script file that I execute occasionally. It worked without
> problems and it makes no problem except that day.
> But all the others fatal errors are generated not by file scripts, but by
> stored procs. But it is not the same each time... For example in the next log
> is stated dbo.ts3_clsAPI_Membres_Upt.
> I will install today the patch kb918222 (buid 2153) to see if it will change
> something...
> I also verify all my SPs and views, functions to use ANSI_NULL ON
> Another log file:
> Memory
> MemoryLoad = 94%
> Total Physical = 4951 MB
> Available Physical = 273 MB
> Total Page File = 6629 MB
> Available Page File = 1585 MB
> Total Virtual = 8388607 MB
> Available Virtual = 8383233 MB
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
> SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/26/06 16:32:32 spid 61
> *
> *
> * Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 000000016CBF3010
> * Input Buffer 255 bytes -
> * d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
> * c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
> * m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
> * & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
> * & §2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
> * AVETSIAN §2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
> * 2 Rousana §� 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
> * 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
> * APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
>
>
> "John Bell" wrote:
> > Hi
> >
> > Error 8624 is an internal SQL Server error so you may want to contact PSS.
> >
> > Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> > D.RefDoc...?
> >
> > John
> >
>|||Finally, I think that I find the problem. I have a function like GetParam
(@.ParamName as varchar) as int and a procedure that it was called very often,
and it contains:
select Param1 = dbo.GetParam (@.Param1),
Param2 = dbo.GetParam (@.Param2),
Param3 = dbo.GetParam (@.Param3),
...
and so on, around 100 parammeters is the same select, using the same
function (don't tell me that makes nosense to return 100 columns. It is an
old application made by others :o(
The function GetParam called another function which called another funtion
and so on. It seems the the optimizer crashes because of the complexity of
this. It works with some users connected in the same time, but with arround
100 users is the same time...
I rewrite the procedure to store each value in scalar variables (set
@.ParamValue1 = dbo.GetParam (@.Param1) and so on) and select @.ParamValue1,
@.ParamValue2 etc.
Now it works 5 times faster (the SP) and without crashes. Seems that I have
to consider all old SPs, views and functions to try to eliminate this kind of
complexity...
"John Bell" wrote:
> Hi
> If installing the hotfix does not cure this I would call PSS.
> John
> "Catalin NASTAC" wrote:
> > That query is a script file that I execute occasionally. It worked without
> > problems and it makes no problem except that day.
> >
> > But all the others fatal errors are generated not by file scripts, but by
> > stored procs. But it is not the same each time... For example in the next log
> > is stated dbo.ts3_clsAPI_Membres_Upt.
> >
> > I will install today the patch kb918222 (buid 2153) to see if it will change
> > something...
> > I also verify all my SPs and views, functions to use ANSI_NULL ON
> >
> > Another log file:
> > Memory
> > MemoryLoad = 94%
> > Total Physical = 4951 MB
> > Available Physical = 273 MB
> > Total Page File = 6629 MB
> > Available Page File = 1585 MB
> > Total Virtual = 8388607 MB
> > Available Virtual = 8383233 MB
> > ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
> > SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
> > EXCEPTION_ACCESS_VIOLATION. SQL Server is
> > terminating this process.
> >
> > *
> > *******************************************************************************
> > *
> >
> > * BEGIN STACK DUMP:
> >
> > * 10/26/06 16:32:32 spid 61
> >
> > *
> >
> > *
> >
> > * Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
> >
> > * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> >
> > * Access Violation occurred writing address 000000016CBF3010
> >
> > * Input Buffer 255 bytes -
> >
> > * d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
> >
> > * c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
> >
> > * m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
> >
> > * & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
> >
> > * & §2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
> >
> > * AVETSIAN §2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
> >
> > * 2 Rousana §� 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
> >
> > * 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
> >
> > * APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
> >
> >
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Error 8624 is an internal SQL Server error so you may want to contact PSS.
> > >
> > > Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> > > D.RefDoc...?
> > >
> > > John
> > >
> >