July 1, 2009 at 12:16 am
Hi All,
Today morning in SQL Server Logs i found dump erros .Can any one please suggest why i am getting this error.This is the first time i am seeing this type of error.
Due to this it'll be any problem to the server.
please check the dump error and suggest
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.1399.06
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.
Bios Version is HP - 2
Current time is 09:51:23 07/01/09.
4 Intel x86 level 6, 2000 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 60%
Total Physical = 4093 MB
Available Physical = 1623 MB
Total Page File = 5972 MB
Available Page File = 3791 MB
Total Virtual = 2047 MB
Available Virtual = 271 MB
**Dump thread - spid = 193, PSS = 0x0BE11300, EC = 0x0BE11308
*
* 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\SQLDump0026.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 07/01/09 09:51:23 spid 193
*
* ex_raise2: Exception raised, major=86, minor=24, state=21, severity=16
*
* Input Buffer 510 bytes -
* SELECT P1,[JAN],[FEB],[MAR] FROM ( SELECT PROJECT,LEFT(DAT
* ENAME(MM,ENTERED_DATE),3) AS PV,PROJECT AS P1 FROM TB_COMPLAINTS_TRACKER
* WHERE YEAR(ENTERED_DATE)=2009 --ORDER BY LEFT(DATENAME(MM,ENTERED
* _DATE),3) )PV1 PIVOT ( COUNT(PROJECT) FOR PV IN ([JAN],[FEB],[MAR])
* ) PVV --SELECT LEFT(DATENAME(MM,GETDATE()),3)
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02BA7FFF 01ba8000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEAFFF 0009b000
* RPCRT4 77C50000 77CEEFFF 0009f000
* Secur32 76F50000 76F62FFF 00013000
* USER32 77380000 77410FFF 00091000
* GDI32 77C00000 77C47FFF 00048000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E1FFF 000c2000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C96FFF 00057000
* SHELL32 7C8D0000 7D0CEFFF 007ff000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* IMM32 76290000 762ACFFF 0001d000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7A0FFF 00191000
* SQLOS 344D0000 344D4FFF 00005000
Please do the needfull.
July 1, 2009 at 12:46 am
This is a kind of Assertion/Exception raised by SQLDumper utility (SQl Debugger)..you also have the Query due to which this is happening .
You can run this query in the QA and it should again raise the exception dump in the error log .
I am 100% confident that you will be resolving this issue after applying SP2 ...you are on RTM my friend which is no more supported and is the first build when SQL 2005 was released in 2005 .
If you want proof you need to drill through so many KB articles for each CU or a seperate Hotfix released due to an urgent issue ..
If you do not want to apply SP2 cal MS suport for debugging and findign on which function the exception is getting raised .
They will then tell you in which build this is fixed .But , the first thing they will tell you is to apply SP2 ...
Regards
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply