Microsoft KB Archive/928568

= FIX: SQL Server 2000 stops responding when you cancel a query or when a query time-out occurs, and error messages are logged in the SQL Server error log file =

Article ID: 928568

Article Last Modified on 6/19/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 64-bit Edition

-



Bug #: 50000478 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
In rare situations, Microsoft SQL Server 2000 stops responding when you cancel a query or when a query time-out occurs. Additionally, error messages that resemble the following are logged in the SQL Server error log file:

2006-07-06 11:04:11.82 spid59 clean_tables_xact: active sdes for tabid 457768688

2006-07-06 11:04:12.23 spid59 Using 'dbghelp.dll' version '4.0.5' *Stack Dump being sent to e:\fastnet\MSSQL\log\SQLDump0009.txt

2006-07-06 11:04:12.51 spid59 Error: 0, Severity: 19, State: 0

2006-07-06 11:04:12.51 spid59 SqlDumpExceptionHandler: Process 59 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..




 * BEGIN STACK DUMP: * 07/06/06 11:04:12 spid 59




 * Exception Address = 00402836


 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION


 * Access Violation occurred writing address 00000004


 * Input Buffer 514 bytes -








 * Short Stack Dump


 * 00402836 Module(sqlservr+00002836)


 * 00407EF3 Module(sqlservr+00007EF3)


 * 0041CB9F Module(sqlservr+0001CB9F)


 * 00414C76 Module(sqlservr+00014C76)


 * 00404F9D Module(sqlservr+00004F9D)


 * 006E732B Module(sqlservr+002E732B) (SQLExit+0017F834)


 * 00642592 Module(sqlservr+00242592) (SQLExit+000DAA9B)


 * 0049C46A Module(sqlservr+0009C46A)


 * 41075309 Module(ums+00005309) (ProcessWorkRequests+000002D9 Line 456+00000000)


 * 41074978 Module(ums+00004978) (ThreadStartRoutine+00000098 Line 263+00000007)


 * 7C34940F Module(MSVCR71+0000940F) (endthread+000000AA)


 * 7C57438B Module(KERNEL32+0000438B) (TlsSetValue+000000F0)



2006-07-06 11:04:31.18 spid59 Stack Signature for the dump is 0x79DB129D

2006-07-06 11:04:31.34 spid59 clean_tables_xact: active sdes for tabid 457768688

2006-07-06 11:06:01.39 server Stack Signature for the dump is 0x00000000

2006-07-06 11:06:01.39 server Error: 17883, Severity: 1, State: 0

2006-07-06 11:06:01.39 server Process 53:0 (b68) UMS Context 0x27F80DE8 appears to be non-yielding on Scheduler 1.

This problem occurs if the following conditions are true:
 * The query performs operations on binary large object (BLOB) data types. Examples of binary large object data types include the Text data type, the NText data type, and the Image data type.
 * The query contains the UNION operator or the OUTER JOIN operator.
 * The query spends significant time processing the binary large object data types.



RESOLUTION
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
 * The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

Note This issue does not occur on systems that use the Intel Itanium processor architecture.
 * The system is running a 64-bit version of the Microsoft Windows Server operating system.
 * The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
 SQL Server 2000 Service Pack 4 (SP4)

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack



Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.



WORKAROUND
To work around this problem, use one of the following techniques:
 * Avoid canceling the query.
 * Avoid using time-consuming operations on the binary large object data types. These operations make the query resource intensive and may slow down the server.
 * Rewrite the query to avoid the UNION operator or the OUTER JOIN operator.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, 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

Keywords: kbexpertiseadvanced kbtshoot kbfix kbhotfixserver kbqfe kbpubtypekc KB928568

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.