January 24, 2007 at 9:54 am
The last two days I have had SQL unexpectadly restart, with an unhandled exception. Both times the trace indicates the same stored procedure, but with different criteria. The proc does not do anything but selects out of different tables.
In the Application log in the OS I see the following error just as SQL is comming back up.
The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The MSSQLSERVER service terminated unexpectedly..
Below is information about the version, basicaly SQL2005 Standard Edition with no service packs applies.
Microsoft SQL Server
2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Anyone shed any light on this? My only thought is to open a case with MS and give them the stack dumps and see if they can help. But, any help here would be greatly appreciated.
January 25, 2007 at 1:32 am
What's in the SQL errorlog just before it shuts down?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2007 at 5:53 am
Immediatly before it crashed there is a stack dump. The last thing in the error log before the ones associated with the stack dump is my backup 5+ hours earlier.
Here are the first few lines of the stack dump:
Using 'dbghelp.dll' version '4.0.5'
**Dump thread - spid = 85, PSS = 0x0435D5C0, EC = 0x0435D5C8
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\LOG\SQLDump0002.txt
Those 3 all has the same timestamp on them.
January 25, 2007 at 6:03 am
Can you post parts of the stack dump? The input buffer for spid 85, the short stach dump
Few questions...
You said the dump is triggered by a select. Are any of the tables in the select remote? If the select is part of a stored proc, what's the line above it?
Do you have any custom written extended stored procs? Any linked servers to non-sql databases?
With a stack dump, probably your best bet is to contact PSS. If you have a minidump file (.mdmp) they'll need to see that. It's a partial binary dump of memory. From that, they should be able to see what was happening at the time of the crash.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2007 at 9:57 am
All the selects are local. The input buffer just has the stored procedure name and the parameter (XML data in a text variable).
We do have linked servers, but all to SQL 2000 (not 2005), but none are used in this query.
My guess is that this stored procedure did not cause, I know that it got run after the server came back up with the same XML in it
It hasn't happened again since, so for now most likely going to write it off, but open a case with MS if it happens again.
Part of the stack dump, the rest if just more of the same module:
* Short Stack dump
77E55DEA Module(kernel32+00015DEA)
02172CE4 Module(sqlservr+01172CE4)
02176BA0 Module(sqlservr+01176BA0)
0217674D Module(sqlservr+0117674D)
023D9428 Module(sqlservr+013D9428)
78134605 Module(MSVCR80+00004605)
78157991 Module(MSVCR80+00027991)
78158935 Module(MSVCR80+00028935)
78158A5B Module(MSVCR80+00028A5B)
7C82EEB2 Module(ntdll+0002EEB2)
7C82EE84 Module(ntdll+0002EE84)
78158A0C Module(MSVCR80+00028A0C)
78158429 Module(MSVCR80+00028429)
781587BC Module(MSVCR80+000287BC)
781589A1 Module(MSVCR80+000289A1)
78158A5B Module(MSVCR80+00028A5B)
7C82EEB2 Module(ntdll+0002EEB2)
7C82EE84 Module(ntdll+0002EE84)
7C82EDA4 Module(ntdll+0002EDA4)
77E55DEA Module(kernel32+00015DEA)
78158DD3 Module(MSVCR80+00028DD3)
010AC7C6 Module(sqlservr+000AC7C6)
010AC67E Module(sqlservr+000AC67E)
March 22, 2007 at 6:40 am
Finaly ended up calling MS PSS after this happened a few more times last week. Turns out this is a bug fixed in SP1 relating to BLOB's. What is weird is there is no KB article, or a mention of it in the patch notes, because there was no hot fix there never was a KB written
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply