Repost: MSDE crash... What to do with the dump file????

Repost: MSDE crash... What to do with the dump file????

Post by José Joy » Mon, 27 Oct 2003 12:35:19



I get from time to time a MSDE crash and I got a SQL dump that tells me to
send the information. However, I do not know to whom and at which condition.
Does anyone has an idea about it?

Last time I got the error, the following (only part of the file is
provided )

The following SP was called. However, the SP normally works.

CREATE PROCEDURE [dbo].[GetDateForLastUOWDeletion]

 )
AS


FROM General WITH (NOLOCK)

RETURN 0
GO

=====================================================================
       BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server 8.00.818
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 13:55:42 10/14/03.
4 Intel x86 level 15, 3055 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 3.

Memory
MemoryLoad = 24%
Total Physical = 1023 MB
Available Physical = 770 MB
Total Page File = 2462 MB
Available Page File = 2306 MB
Total Virtual = 2047 MB
Available Virtual = 978 MB

***Symbol load failed - Proceed to dump without any symbols
*Stack Dump being sent to D:\MSDE\Mssql\Data\MSSQL\log\SQLDump0005.txt
*
****************************************************************************
*
**
*
* BEGIN STACK DUMP:
*   10/14/03 13:55:42 spid 0
*
*   Exception Address = 77EAB2F0
*   Exception Code    = 400042ac PRINTSTACK
*
*  MODULE                          BASE      END       SIZE
*
*        Edi: 00000000:
*        Esi: 00000000:
*        Eax: 0D81EE34: 400042AC  00000000  00000000  77EAB2F0  00000000
00000
000
*        Ebx: 00000000:
*        Ecx: 0D81FA54: 61636F4C  6E6F6974  7520093A  6874736D  632E6472
343A7
070
*        Edx: 0D81FABA: 00000036  30F00000  000077F8  FACC0000  8D320D81
00027
7FC
*        Eip: 77EAB2F0: C2C95E5F  4C8B0010  F0A10424  8977EDA1  EDA1F00D
0004C
277
*        Ebp: 0D81EE84: 0D81EEC0  00881D4A  400042AC  00000000  00000000
00000
000
*      SegCs: 0000001B:
*     EFlags: 00000246:
*        Esp: 0D81EE2C: 00000000  00000000  400042AC  00000000  00000000
77EAB
2F0
*      SegSs: 00000023:
*
****************************************************************************
*
**
* --------------------------------------------------------------------------
---
--
* Short Stack Dump
* 77EAB2F0 Module(UNKNOWN+00000000)
* 00881D4A Module(UNKNOWN+00000000)
* 00881B3E Module(UNKNOWN+00000000)
* 00935D29 Module(UNKNOWN+00000000)
* 41074DFA Module(UNKNOWN+00000000)
* 410715FD Module(UNKNOWN+00000000)
* 4107279E Module(UNKNOWN+00000000)
* 410725B3 Module(UNKNOWN+00000000)
* 514D68FF Module(UNKNOWN+00000000)
----------------------------------------------------------------------------
---
* Location   : 77EAB2F0 Module(UNKNOWN+00000000)
* Return Addr: 00881D4A Module(UNKNOWN+00000000)
Frame      : 0D81EE84
Parameters:
  [1] 400042AC:
  [2] 00000000:
  [3] 00000000:
  [4] 00000000:
  160 bytes of stack data from 0D81EDE4 to 0D81EE84
0D81EDE4:  00BE0000 00BE0B38 00000019 00000000  [....8...........]
0D81EDF4:  0C41FC0C 00000200 00BE0000 00BE91F0  [..A.............]
0D81EE04:  00BE0178 000001C2 77FC9202 77FC93BE  [x..........w...w]
0D81EE14:  77FC9518 0C41FE74 00000000 00BE6A90  [...wt.A......j..]
0D81EE24:  0C41FC74 0C41FC98 00000000 00000000  [t.A...A.........]

0D81EE44:  00000000 00000000 00000001 00000008  [................]

0D81EE64:  4300065E 00000008 00000038 00000000  [^..C....8.......]
0D81EE74:  00000002 43058468 4300065D 00000015  [....h..C]..C....]

 
 
 

Repost: MSDE crash... What to do with the dump file????

Post by Andrew J. Kell » Mon, 27 Oct 2003 20:39:53


I suspect that it is referring to MS PSS.  If you want to get help you can
contact them but there is a charge for the service.  If it turns out to be a
bug in SQL Server they will refund your money though.  An error that is this
critical usually warrants a call to MS PSS as it is usually difficult to
sort out a stack dump in the newsgroup.  Here is the contact information for
PSS.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql    SQL Support
http://www.mssqlserver.com/faq/general-pss.asp   MS PSS

Just a note on yur stored procedure.  You are using a NOLOCK hint which can
cause an error under certain conditions due to the lack of locks and that is
normal for that isolation level.  I have not seen it error so bad that it
does a stack dump though.  Is there a particular reason you are using that
hint for this simple query?  Your query should also have an ORDER BY clause
other wise the TOP is not guaranteed to give you the correct row.

--

Andrew J. Kelly
SQL Server MVP


> I get from time to time a MSDE crash and I got a SQL dump that tells me to
> send the information. However, I do not know to whom and at which
condition.
> Does anyone has an idea about it?

> Last time I got the error, the following (only part of the file is
> provided )

> The following SP was called. However, the SP normally works.

> CREATE PROCEDURE [dbo].[GetDateForLastUOWDeletion]

>  )
> AS


> FROM General WITH (NOLOCK)

> RETURN 0
> GO

> =====================================================================
>        BugCheck Dump
> =====================================================================

> This file is generated by Microsoft SQL Server 8.00.818
> 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 13:55:42 10/14/03.
> 4 Intel x86 level 15, 3055 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 3.

> Memory
> MemoryLoad = 24%
> Total Physical = 1023 MB
> Available Physical = 770 MB
> Total Page File = 2462 MB
> Available Page File = 2306 MB
> Total Virtual = 2047 MB
> Available Virtual = 978 MB

> ***Symbol load failed - Proceed to dump without any symbols
> *Stack Dump being sent to D:\MSDE\Mssql\Data\MSSQL\log\SQLDump0005.txt
> *

****************************************************************************

- Show quoted text -

Quote:> *
> **
> *
> * BEGIN STACK DUMP:
> *   10/14/03 13:55:42 spid 0
> *
> *   Exception Address = 77EAB2F0
> *   Exception Code    = 400042ac PRINTSTACK
> *
> *  MODULE                          BASE      END       SIZE
> *
> *        Edi: 00000000:
> *        Esi: 00000000:
> *        Eax: 0D81EE34: 400042AC  00000000  00000000  77EAB2F0  00000000
> 00000
> 000
> *        Ebx: 00000000:
> *        Ecx: 0D81FA54: 61636F4C  6E6F6974  7520093A  6874736D  632E6472
> 343A7
> 070
> *        Edx: 0D81FABA: 00000036  30F00000  000077F8  FACC0000  8D320D81
> 00027
> 7FC
> *        Eip: 77EAB2F0: C2C95E5F  4C8B0010  F0A10424  8977EDA1  EDA1F00D
> 0004C
> 277
> *        Ebp: 0D81EE84: 0D81EEC0  00881D4A  400042AC  00000000  00000000
> 00000
> 000
> *      SegCs: 0000001B:
> *     EFlags: 00000246:
> *        Esp: 0D81EE2C: 00000000  00000000  400042AC  00000000  00000000
> 77EAB
> 2F0
> *      SegSs: 00000023:
> *

****************************************************************************
Quote:> *
> **

* --------------------------------------------------------------------------

- Show quoted text -

> ---
> --
> * Short Stack Dump
> * 77EAB2F0 Module(UNKNOWN+00000000)
> * 00881D4A Module(UNKNOWN+00000000)
> * 00881B3E Module(UNKNOWN+00000000)
> * 00935D29 Module(UNKNOWN+00000000)
> * 41074DFA Module(UNKNOWN+00000000)
> * 410715FD Module(UNKNOWN+00000000)
> * 4107279E Module(UNKNOWN+00000000)
> * 410725B3 Module(UNKNOWN+00000000)
> * 514D68FF Module(UNKNOWN+00000000)
> --------------------------------------------------------------------------
--
> ---
> * Location   : 77EAB2F0 Module(UNKNOWN+00000000)
> * Return Addr: 00881D4A Module(UNKNOWN+00000000)
> Frame      : 0D81EE84
> Parameters:
>   [1] 400042AC:
>   [2] 00000000:
>   [3] 00000000:
>   [4] 00000000:
>   160 bytes of stack data from 0D81EDE4 to 0D81EE84
> 0D81EDE4:  00BE0000 00BE0B38 00000019 00000000  [....8...........]
> 0D81EDF4:  0C41FC0C 00000200 00BE0000 00BE91F0  [..A.............]
> 0D81EE04:  00BE0178 000001C2 77FC9202 77FC93BE  [x..........w...w]
> 0D81EE14:  77FC9518 0C41FE74 00000000 00BE6A90  [...wt.A......j..]
> 0D81EE24:  0C41FC74 0C41FC98 00000000 00000000  [t.A...A.........]

> 0D81EE44:  00000000 00000000 00000001 00000008  [................]

> 0D81EE64:  4300065E 00000008 00000038 00000000  [^..C....8.......]
> 0D81EE74:  00000002 43058468 4300065D 00000015  [....h..C]..C....]


 
 
 

Repost: MSDE crash... What to do with the dump file????

Post by José Joy » Mon, 27 Oct 2003 21:47:04


Thanks for your reply!

I will try to contact MS at the address you gave me.

Related to the SP, It refers to a table containing only a single row. The
data I'm looking for is a date. I do not really care too much if it is a
dirty read. The problem I had without the "NOLOCK" is that I got dead-lock
from time to time.
In fact this table is accessed by 2 processes (the Business Layer of a
Front-End and a clean-up routine that runs at night).
The Business layer of the front-end performs read only access and I do not
care too much if I get from time to time a dirty read.

Jos



> I suspect that it is referring to MS PSS.  If you want to get help you can
> contact them but there is a charge for the service.  If it turns out to be
a
> bug in SQL Server they will refund your money though.  An error that is
this
> critical usually warrants a call to MS PSS as it is usually difficult to
> sort out a stack dump in the newsgroup.  Here is the contact information
for
> PSS.

> http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql    SQL Support
> http://www.mssqlserver.com/faq/general-pss.asp   MS PSS

> Just a note on yur stored procedure.  You are using a NOLOCK hint which
can
> cause an error under certain conditions due to the lack of locks and that
is
> normal for that isolation level.  I have not seen it error so bad that it
> does a stack dump though.  Is there a particular reason you are using that
> hint for this simple query?  Your query should also have an ORDER BY
clause
> other wise the TOP is not guaranteed to give you the correct row.

> --

> Andrew J. Kelly
> SQL Server MVP



> > I get from time to time a MSDE crash and I got a SQL dump that tells me
to
> > send the information. However, I do not know to whom and at which
> condition.
> > Does anyone has an idea about it?

> > Last time I got the error, the following (only part of the file is
> > provided )

> > The following SP was called. However, the SP normally works.

> > CREATE PROCEDURE [dbo].[GetDateForLastUOWDeletion]

> >  )
> > AS


> > FROM General WITH (NOLOCK)

> > RETURN 0
> > GO

> > =====================================================================
> >        BugCheck Dump
> > =====================================================================

> > This file is generated by Microsoft SQL Server 8.00.818
> > 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 13:55:42 10/14/03.
> > 4 Intel x86 level 15, 3055 Mhz processor(s).
> > Windows NT 5.0 Build 2195 CSD Service Pack 3.

> > Memory
> > MemoryLoad = 24%
> > Total Physical = 1023 MB
> > Available Physical = 770 MB
> > Total Page File = 2462 MB
> > Available Page File = 2306 MB
> > Total Virtual = 2047 MB
> > Available Virtual = 978 MB

> > ***Symbol load failed - Proceed to dump without any symbols
> > *Stack Dump being sent to D:\MSDE\Mssql\Data\MSSQL\log\SQLDump0005.txt
> > *

****************************************************************************

- Show quoted text -

Quote:> > *
> > **
> > *
> > * BEGIN STACK DUMP:
> > *   10/14/03 13:55:42 spid 0
> > *
> > *   Exception Address = 77EAB2F0
> > *   Exception Code    = 400042ac PRINTSTACK
> > *
> > *  MODULE                          BASE      END       SIZE
> > *
> > *        Edi: 00000000:
> > *        Esi: 00000000:
> > *        Eax: 0D81EE34: 400042AC  00000000  00000000  77EAB2F0  00000000
> > 00000
> > 000
> > *        Ebx: 00000000:
> > *        Ecx: 0D81FA54: 61636F4C  6E6F6974  7520093A  6874736D  632E6472
> > 343A7
> > 070
> > *        Edx: 0D81FABA: 00000036  30F00000  000077F8  FACC0000  8D320D81
> > 00027
> > 7FC
> > *        Eip: 77EAB2F0: C2C95E5F  4C8B0010  F0A10424  8977EDA1  EDA1F00D
> > 0004C
> > 277
> > *        Ebp: 0D81EE84: 0D81EEC0  00881D4A  400042AC  00000000  00000000
> > 00000
> > 000
> > *      SegCs: 0000001B:
> > *     EFlags: 00000246:
> > *        Esp: 0D81EE2C: 00000000  00000000  400042AC  00000000  00000000
> > 77EAB
> > 2F0
> > *      SegSs: 00000023:
> > *

****************************************************************************
Quote:> > *
> > **

* --------------------------------------------------------------------------

- Show quoted text -

> > ---
> > --
> > * Short Stack Dump
> > * 77EAB2F0 Module(UNKNOWN+00000000)
> > * 00881D4A Module(UNKNOWN+00000000)
> > * 00881B3E Module(UNKNOWN+00000000)
> > * 00935D29 Module(UNKNOWN+00000000)
> > * 41074DFA Module(UNKNOWN+00000000)
> > * 410715FD Module(UNKNOWN+00000000)
> > * 4107279E Module(UNKNOWN+00000000)
> > * 410725B3 Module(UNKNOWN+00000000)
> > * 514D68FF Module(UNKNOWN+00000000)

> --------------------------------------------------------------------------
> --
> > ---
> > * Location   : 77EAB2F0 Module(UNKNOWN+00000000)
> > * Return Addr: 00881D4A Module(UNKNOWN+00000000)
> > Frame      : 0D81EE84
> > Parameters:
> >   [1] 400042AC:
> >   [2] 00000000:
> >   [3] 00000000:
> >   [4] 00000000:
> >   160 bytes of stack data from 0D81EDE4 to 0D81EE84
> > 0D81EDE4:  00BE0000 00BE0B38 00000019 00000000  [....8...........]
> > 0D81EDF4:  0C41FC0C 00000200 00BE0000 00BE91F0  [..A.............]
> > 0D81EE04:  00BE0178 000001C2 77FC9202 77FC93BE  [x..........w...w]
> > 0D81EE14:  77FC9518 0C41FE74 00000000 00BE6A90  [...wt.A......j..]
> > 0D81EE24:  0C41FC74 0C41FC98 00000000 00000000  [t.A...A.........]

> > 0D81EE44:  00000000 00000000 00000001 00000008  [................]

> > 0D81EE64:  4300065E 00000008 00000038 00000000  [^..C....8.......]
> > 0D81EE74:  00000002 43058468 4300065D 00000015  [....h..C]..C....]

 
 
 

1. Trigger doing UNLOAD to file OR calling Store Procedure doing the UNLOAD to file

Hi,

I don't if its possible to do the following on Informix 7.30 NT I get a SQL
ERROR -201, probably wrong version or syntax error.
Is this supported on IDS2000 ?

create trigger TGU_getrws
    UPDATE of statcond ON COM_RWS_LST
    REFERENCING NEW AS val
    FOR EACH ROW WHEN(val.statcond = 'L')
    (UNLOAD TO 'D:\data\blabla' DELIMITER '|' SELECT statid from COM_RWS_LST
WHERE statcond = 'L')

OR

create trigger TGU_getrws
    UPDATE of statcond ON COM_RWS_LST
    REFERENCING NEW AS val
    FOR EACH ROW WHEN(val.statcond = 'L')
    (EXECUTE PROCEDURE P_tst_rws())

CREATE PROCEDURE P_tst_rws()
        ...
        UNLOAD TO 'D:\data\blabla' DELIMITER '|' SELECT statid from
COM_RWS_LST WHERE statcond = 'L'
END PROCEDURE;

Thanks for any comment on this

Dario

2. DB/Net Library Dlls

3. Tool to interpret SQL Server crash dump files?

4. MS Data Analyzer : connection problems...

5. dump tran creates dump file, but syslogs stays full

6. "insert into table_name select ?, ?, ?" is this possible?

7. Whacky DUMP TRANSACTION SQL 6.5 SP4 - HELP - REPOST

8. Best Practices (Repost - ISP took a dump)

9. REPOST: Oracle dump info needed

10. REPOST: Oracle Dump

11. Repost: When try to get a server list within EM, EM crashes

12. REPOST: Re: db2 error in db2diag.log and LDAP crash