October 22, 2012 at 5:34 pm
So, I'm having an intermittent issue with the following dump being plastered in my SQLLog on my SQL 2000 SP4 BUILD 2282 system. This stored procedure is executed QUITE frequently, meaning hundreds of times a minute, but only pops up in the log every 15mins or so. The stored procedure is a 3000 line stored procedure (not mine!) that has over 50 conditionals in it.
Any ideas on what could be triggering this dump? I've done a checkdb on the whole db and done checktables on the tables involved. I even attempted to flush the cached plan, and even tried hadding hints to maxdop 1, and still this occurs.
The following is the dump:
SqlDumpExceptionHandler: Process 289 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/23/12 06:51:26 spid 289
*
* Exception Address = 00755204 (SQLExit + 00181C60 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address A1F34000
* Input Buffer 148 bytes -
* dbo.usp_my_stored_proc 'displayEN','-','name`30',
* ''
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CC3FFF 008c4000
* ntdll 7D600000 7D6EFFFF 000f0000
* kernel32 7D4C0000 7D5EFFFF 00130000
* ADVAPI32 7D1E0000 7D27BFFF 0009c000
* RPCRT4 7DA20000 7DAFFFFF 000e0000
* Secur32 7D8D0000 7D91FFFF 00050000
* MSVCP71 7C3A0000 7C41AFFF 0007b000
* MSVCR71 7C340000 7C395FFF 00056000
* opends60 41060000 41065FFF 00006000
* SHELL32 7C8D0000 7D0CEFFF 007ff000
* msvcrt 77BA0000 77BF9FFF 0005a000
* GDI32 7D800000 7D88FFFF 00090000
* USER32 7D930000 7D9FFFFF 000d0000
* SHLWAPI 7D180000 7D1D1FFF 00052000
* sqlsort 42AE0000 42B6FFFF 00090000
* ums 41070000 4107CFFF 0000d000
* IMM32 7DEE0000 7DF3FFFF 00060000
* comctl32 7DBD0000 7DCD2FFF 00103000
* sqlevn70 41080000 4108AFFF 0000b000
* CLUSAPI 74DE0000 74DF1FFF 00012000
* ole32 77670000 777A8FFF 00139000
* OLEAUT32 7D0E0000 7D16AFFF 0008b000
* RESUTILS 74EF0000 74F02FFF 00013000
* USERENV 76920000 769E1FFF 000c2000
* NETAPI32 0AFC0000 0B016FFF 00057000
* AUTHZ 0B020000 0B033FFF 00014000
* COMRES 0BD10000 0BDD5FFF 000c6000
* XOLEHLP 0BDE0000 0BDE5FFF 00006000
* MSDTCPRX 0BDF0000 0BE68FFF 00079000
* msvcp60 0BE70000 0BED4FFF 00065000
* MTXCLU 0BEE0000 0BEF8FFF 00019000
* VERSION 0BF00000 0BF07FFF 00008000
* WSOCK32 0BF10000 0BF18FFF 00009000
* WS2_32 0BF20000 0BF36FFF 00017000
* WS2HELP 0BF40000 0BF47FFF 00008000
* msapsspc 0BF90000 0BFA3FFF 00014000
* MSVCRT40 0BFB0000 0BFC0FFF 00011000
* msnsspc 0BFE0000 0C02FFFF 00050000
* mswsock 0C050000 0C0CFFFF 00080000
* DNSAPI 0C0D0000 0C0F9FFF 0002a000
* winrnr 0C140000 0C146FFF 00007000
* WLDAP32 0C150000 0C17DFFF 0002e000
* iphlpapi 0C1A0000 0C1B9FFF 0001a000
* PSAPI 0C1C0000 0C1CAFFF 0000b000
* netman 0C1E0000 0C221FFF 00042000
* netshell 0C230000 0C3EFFFF 001c0000
* rtutils 0C3F0000 0C3FBFFF 0000c000
* credui 0C400000 0C42DFFF 0002e000
* ATL 0C430000 0C441FFF 00012000
* MPRAPI 0C450000 0C468FFF 00019000
* ACTIVEDS 0C470000 0C4A3FFF 00034000
* adsldpc 0C4B0000 0C4D7FFF 00028000
* SAMLIB 0C4E0000 0C4EEFFF 0000f000
* SETUPAPI 0C4F0000 0C5F7FFF 00108000
* RASAPI32 0C600000 0C63EFFF 0003f000
* rasman 0C640000 0C651FFF 00012000
* TAPI32 0C660000 0C68EFFF 0002f000
* WINMM 0C690000 0C6BCFFF 0002d000
* CRYPT32 0C6C0000 0C752FFF 00093000
* MSASN1 0C760000 0C771FFF 00012000
* WZCSvc 0C780000 0C80DFFF 0008e000
* WMI 0C810000 0C814FFF 00005000
* DHCPCSVC 0C820000 0C83EFFF 0001f000
* WTSAPI32 0C840000 0C847FFF 00008000
* WINSTA 0C850000 0C860FFF 00011000
* ESENT 0C870000 0C973FFF 00104000
* WININET 0C980000 0CA65FFF 000e6000
* Normaliz 0CA70000 0CA78FFF 00009000
* urlmon 0CA80000 0CBB2FFF 00133000
* iertutil 0CBC0000 0CDAAFFF 001eb000
* WZCSAPI 0CDB0000 0CDBDFFF 0000e000
* rsaenh 0E030000 0E064FFF 00035000
* hnetcfg 0E070000 0E0C9FFF 0005a000
* wshtcpip 0E110000 0E117FFF 00008000
* rasadhlp 0E120000 0E124FFF 00005000
* msv1_0 0E200000 0E226FFF 00027000
* cryptdll 0E230000 0E23BFFF 0000c000
* SSNETLIB 0EDB0000 0EDC5FFF 00016000
* NTMARTA 0EDD0000 0EDF0FFF 00021000
* security 0F0B0000 0F0B3FFF 00004000
* SSmsLPCn 0F0C0000 0F0C7FFF 00008000
* SSnmPN70 102D0000 102D6FFF 00007000
* ntdsapi 103A0000 103B3FFF 00014000
* Kerberos 0F880000 0F8D8FFF 00059000
* xpsp2res 151A0000 15464FFF 002c5000
* CLBCatQ 15470000 154F2FFF 00083000
* sqloledb 15500000 15580FFF 00081000
* MSDART 14B60000 14B79FFF 0001a000
* MSDATL3 14DC0000 14DD4FFF 00015000
* oledb32 15F10000 15F88FFF 00079000
* OLEDB32R 15F90000 15FA0FFF 00011000
* xpstar 15FB0000 15FFCFFF 0004d000
* SQLRESLD 0F910000 0F91BFFF 0000c000
* SQLSVC 16000000 1601AFFF 0001b000
* ODBC32 16020000 1605DFFF 0003e000
* COMCTL32 16060000 160F6FFF 00097000
* comdlg32 16100000 16148FFF 00049000
* odbcbcp 0F9C0000 0F9C5FFF 00006000
* W95SCM 0FFD0000 0FFDCFFF 0000d000
* SQLUNIRL 16150000 1617CFFF 0002d000
* WINSPOOL 16180000 161A6FFF 00027000
* SHFOLDER 145E0000 145E8FFF 00009000
* odbcint 16670000 16686FFF 00017000
* NDDEAPI 16790000 16797FFF 00008000
* SQLSVC 167A0000 167A5FFF 00006000
* xpstar 167B0000 167B8FFF 00009000
* SQLFTQRY 167C0000 167E5FFF 00026000
* xpsqlbot 0EE60000 0EE65FFF 00006000
* adsldp 18EB0000 18EDDFFF 0002e000
* SXS 190A0000 1915CFFF 000bd000
* xplog70 0F090000 0F09EFFF 0000f000
* xplog70 0F0A0000 0F0A4FFF 00005000
* dbghelp 195E0000 196DFFFF 00100000
*
* Edi: A1F33FD8: 20202020 20202020 20202020 20202020 20202020 20202020
* Esi: 1277E998: 0000A700 A1F33FD8 00000028 A28BC040 00000001 00000010
* Eax: A1F34000:
* Ebx: 00000001:
* Ecx: 00000000:
* Edx: 00000028:
* Eip: 00755204: 8240188A 077520FB 8549D98B 85F175DB 8B177EC9 5251FC4D
* Ebp: 1277E984: 1277E9F8 0041B12F 41A52988 A28BC068 00000000 0000A700
* SegCs: 00000023:
* EFlags: 00010202: 00460020 006C0069 00730065 00430000 004D004F 00550050
* Esp: 1277E968: 1277E998 A1F33FB0 0075515C 0042E85E 00000000 000004E4
* SegSs: 0000002B:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
* 00755204 Module(sqlservr+00355204) (SQLExit+00181C60)
* 0041B12F Module(sqlservr+0001B12F)
* 00422E1F Module(sqlservr+00022E1F)
* 0042339C Module(sqlservr+0002339C)
* 00418D50 Module(sqlservr+00018D50)
* 00418F93 Module(sqlservr+00018F93)
* 00418B39 Module(sqlservr+00018B39)
* 00529449 Module(sqlservr+00129449)
* 0052926D Module(sqlservr+0012926D)
* 00418D50 Module(sqlservr+00018D50)
* 00418F93 Module(sqlservr+00018F93)
* 00418B39 Module(sqlservr+00018B39)
* 00609278 Module(sqlservr+00209278) (SQLExit+00035CD4)
* 006093B4 Module(sqlservr+002093B4) (SQLExit+00035E10)
* 41071B0A Module(ums+00001B0A) (ProcessWorkRequests+000002D9)
* 4107268C Module(ums+0000268C) (ThreadStartRoutine+00000098)
* 7C34940F Module(MSVCR71+0000940F) (endthread+000000AA)
* 7D4DFE37 Module(kernel32+0001FE37) (FlsSetValue+0000013C)
* -------------------------------------------------------------------------------
October 22, 2012 at 6:16 pm
On twitter I asked you if this sproc does anything "special", such as XP calls, full text search, linked server, openquery, xml, etc. Are triggers in play?
Too bad it is intermittent ... can't comment out code sections to isolate the cause.
As @sqlsoldier said, you may need a support ticket to get to the bottom of this one, or at least someone familiar with debug symbols and stack dump analysis of SQL 2000.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
October 22, 2012 at 6:18 pm
Nothing special other than some dynamic sql with exec() and conditional statements, and being 3000 lines long. No linked servers or xp calls.
October 23, 2012 at 9:09 am
Can you check all the input buffers from the error log entries to see if there is some common thread amongst the sproc parameters? Maybe a funky character is causing something to go south (like the ` character in 'name`30')? Just grasping at straws here ...
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
October 23, 2012 at 9:19 am
Good thinking. Looking at the dumps, it appears every case has the ` character. If i run the sproc statements in SSMS it doesn't trigger the exception though. So, I'm not quite sure that it's purely that character doing it...
This is grasping at straws, grrr. I would totally rewrite this sproc, but it's 3000 lines long, and full of crazy business logic I don't understand 🙂
October 23, 2012 at 3:35 pm
BRIAN.ALLEN (10/23/2012)
Good thinking. Looking at the dumps, it appears every case has the ` character. If i run the sproc statements in SSMS it doesn't trigger the exception though. So, I'm not quite sure that it's purely that character doing it...This is grasping at straws, grrr. I would totally rewrite this sproc, but it's 3000 lines long, and full of crazy business logic I don't understand 🙂
You big baby!! 😀
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply