FIX: An attention signal that is sent from a SQL Server client application because of a query time-out may cause the SQL Server service to quit unexpectedly (829015)
The information in this article applies to:
- Microsoft SQL Server 7.0 Service Pack 4
Bug #: 200067 (SQL Server 7.0)
SQL Server 7.0:200067 SYMPTOMSIf you run a query by using a SQL Server client application and the client application sends an attention signal to the server that is running SQL Server because of a query time-out, the SQL Server service may quit unexpectedly. You may notice an error message that is similar to the following in the SQL Server error log: 2003-09-10 13:43:02.38 spid9 Found
active sdes for spid 9 tabid 197575742 in
clean_process
You may also notice one of the following behaviors, depending on whether parallelism is enabled or is disabled on the instance of SQL Server. Behavior 1 If parallelism is enabled on the instance of SQL Server an assertion may occur, and then the SQL Server service may quit unexpectedly. You may see the following stack dump:
Short Stack Dump
0x77f9741f Module(ntdll+1741f) (NtGetContextThread+b)
0x0078c44a Module(sqlservr+38c44a) (utassert_fail+1a0)
0x005bc329 Module(sqlservr+1bc329) (ExecutionContext::Cleanup+9e)
0x004cee07 Module(sqlservr+cee07) (ExecutionContext::Purge+46)
0x004ceb68 Module(sqlservr+ceb68) (stopsubprocess+e6)
0x004cd734 Module(sqlservr+cd734) (subproc_main+175)
0x41092cff Module(ums+2cff) (ProcessWorkRequests+102)
0x41093523 Module(ums+3523) (ThreadStartRoutine+139)
0x7800a27b Module(MSVCRT+a27b) (beginthread+ce)
0x77e8758a Module(KERNEL32+758a) (SetFilePointer+18a)
2003-09-10 13:28:04.99 kernel SQL Server Assertion: File: <proc.c>, line=1931
Failed Assertion = 'm_activeSdesList.Head () == NULL'.
2003-09-10 13:28:04.99 spid9 Using 'sqlimage.dll' version '4.0.5'
Dump thread - spid = 9, PSS = 0x413e70bc, EC = 0x4402c084
Stack Dump being sent to C:\MSSQL7\log\SQL00057.dmp Behavior 2If parallelism is disabled on the instance of SQL Server, the SQL Server service may continue to run. However, you may notice error messages that are similar to the following in the SQL Server error log file: 2003-09-10 13:43:02.38 spid9
Found active sdes for spid 9 tabid 197575742 in clean_process 2003-09-10
13:43:09.37 spid10 Found active sdes for spid 10 tabid 197575742 in
clean_process 2003-09-10 13:43:09.37 spid9 Found active sdes for spid 9
tabid 197575742 in clean_process 2003-09-10 13:43:09.40 spid8 Found active
sdes for spid 8 tabid 197575742 in clean_process 2003-09-10 13:43:23.40
kernel SQL Server shutdown due to Ctrl-C or Ctrl-Break signal.
Behavior 3If the SQL Server client application runs a stored procedure that contains the problem query by a using Remote Procedure Call (RPC) and query parallelism is disabled, the SQL Server service may quit unexpectedly. You may see error messages that are similar to the following in the
SQL Server error log file: 2003-09-10 13:36:17.66 spid9 Found active sdes for spid 9
tabid 197575742 in clean_process 2003-09-10 13:36:17.66 spid9 Process 9
unlocking unowned resource: TAB: 8:197575742 [] 2003-09-10 13:36:17.66
spid9 Using 'sqlimage.dll' version '4.0.5' 2003-09-10 13:36:18.82 spid10
Found active sdes for spid 10 tabid 197575742 in clean_process 2003-09-10
13:36:18.82 spid10 Process 10 unlocking unowned resource: TAB: 8:197575742 []
2003-09-10 13:36:20.73 spid8 Found active sdes for spid 8 tabid 197575742
in clean_process 2003-09-10 13:36:20.73 spid8 Process 8 unlocking unowned
resource: TAB: 8:197575742 [] Dump thread - spid = 9, PSS = 0x4139d0bc, EC
= 0x4139d26c Stack Dump being sent to
C:\MSSQL7\log\SQL00060.dmp
You may also see a stack
dump that is similar to the following:
Short Stack Dump
0x77f9741f Module(ntdll+1741f) (NtGetContextThread+b)
0x005bcdd4 Module(sqlservr+1bcdd4) (ex_raise2+35c)
0x004f8616 Module(sqlservr+f8616) (ex_raise+5f)
0x006e1cf5 Module(sqlservr+2e1cf5) (reportUnlockFailure+8f)
0x005abaa3 Module(sqlservr+1abaa3) (lck_unlock+120)
0x0040c45a Module(sqlservr+c45a) (RowsetLockCache::ReleaseRowsetLock+72)
0x0040341a Module(sqlservr+341a) (closetable+134)
0x005b9bbd Module(sqlservr+1b9bbd) (clean_process+f5)
0x0042b5b6 Module(sqlservr+2b5b6) (execrpc+7b3)
0x4106256e Module(opends60+256e) (execute_rpc+421)
0x4106127c Module(opends60+127c) (execute_event+21a)
0x4106142f Module(opends60+142f) (process_commands+107)
0x41092cff Module(ums+2cff) (ProcessWorkRequests+102)
0x41093523 Module(ums+3523) (ThreadStartRoutine+139)
0x7800a27b Module(MSVCRT+a27b) (beginthread+ce)
0x77e8758a Module(KERNEL32+758a) (SetFilePointer+18a)
Dump thread - spid = 8, PSS = 0x413970bc, EC = 0x4139726c
Stack Dump being sent to C:\MSSQL7\log\SQL00061.dmp RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has
the file attributes (or later) that are listed in the following table. The
dates and times for these files are listed in coordinated universal time (UTC).
When you view the file information, it is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
------------------------------------------------------------------
04-Oct-2002 23:59 7.00.1081 28,944 Dbmssocn.dll
06-Sep-2002 23:55 7.00.1077 53,520 Distrib.exe
06-Sep-2002 23:55 7.00.1077 98,576 Logread.exe
05-May-2003 18:34 54,904 Opends60.dbg
05-May-2003 18:34 7.00.1093 155,920 Opends60.dll
06-Sep-2002 23:56 7.00.1077 250,128 Rdistcom.dll
06-Sep-2002 23:55 7.00.1077 82,192 Replmerg.exe
06-Sep-2002 23:56 7.00.1077 78,096 Replres.dll
17-Sep-2002 22:52 7,941 Securityhotfix.sql
06-Sep-2002 23:56 7.00.1077 160,016 Snapshot.exe
30-May-2003 04:21 59,214 Sp4_serv_uni.sql
15-Jan-2003 01:33 7.00.1085 344,064 Sqlagent.exe
06-Sep-2002 23:55 7.00.1077 45,056 Sqlcmdss.dll
16-May-2003 00:18 7.00.1094 2,629,632 Sqldmo.dll
16-May-2003 13:29 7.00.1094 81,920 Sqlmap70.dll
03-Oct-2003 01:30 7.00.1143 5,062,928 Sqlservr.exe
04-Oct-2002 23:59 7.00.1081 45,328 Ssmsso70.dll
16-May-2003 00:18 7.00.1094 24,848 Ssnmpn70.dll
26-Sep-2002 20:30 28,408 Ums.dbg
26-Sep-2002 20:27 7.00.1079 57,616 Ums.dll
16-May-2003 13:31 7.00.1094 151,552 Xpweb70.dll Note Because of file dependencies, the most recent hotfix that
contains these files may also contain additional files. WORKAROUNDTo work around this problem, you must increase the query
timeout period. To do so, you can use the query wait option in SQL Server. For additional information about the query wait option, visit the following Microsoft Web site: STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.REFERENCES
For additional information about software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe
Microsoft software updates
For additional information about the max degree of parallelism option in SQL Server, visit the following Microsoft Web site:
Modification Type: | Minor | Last Reviewed: | 10/25/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbQuery kbSqlClient KbClientServer kbClient kberrmsg kbSQLServ700preSP5fix kbfix kbbug KB829015 kbAudDeveloper |
---|
|