Microsoft KB Archive/909089

= FIX: An access violation may occur when you try to run a Transact-SQL query in SQL Server 2000 =

Article ID: 909089

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



BUG #: 471331 (SQL Server 8.0)



''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
When you try to run a Transact-SQL query from an application in Microsoft SQL Server 2000, an access violation may occur. This problem occurs when the following conditions are true:
 * The Transact-SQL query contains a UNION operator.
 * The Transact-SQL query uses a parallel execution plan.

When this problem occurs, the following error message is logged in the SQL Server error log:

server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1) ... 2005-08-31 12:21:15.46 spid54 DBCC TRACEON 2861, server process ID (SPID) 54.

spid57 Open of fault log C:\Program Files\Microsoft SQL Server\MSSQL\log\exception.log failed.

spid57 Open of fault log C:\Program Files\Microsoft SQL Server\MSSQL\log\exception.log failed.

spid57 Open of fault log C:\Program Files\Microsoft SQL Server\MSSQL\log\exception.log failed.

spid57 Using 'dbghelp.dll' version '4.0.5'


 * Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\log\SQLDump0920.txt

spid57 SqlDumpExceptionHandler: Process 5984 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.


 * ******************************************************************************* * * BEGIN STACK DUMP:



spid 57




 * Exception Address = 0040560F


 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION


 * Access Violation occurred reading address 000000B8


 * d b o . P I H D 14 00 64 00 62 00 6f 00 2e 00 50 00 49 00 48 00 44 00


 * e l e t e _ L e v 65 00 6c 00 65 00 74 00 65 00 5f 00 4c 00 65 00 76 00


 * e l 2 §2 2 65 00 6c 00 32 00 00 00 00 00 a7 32 00 09 04 00 01 32


 * F49 § 2 a 03 00 46 34 39 00 00 a7 08 00 09 04 00 01 32 07 00 61


 * cdgood 63 64 67 6f 6f 64






 * Short Stack Dump * 0040560F Module(sqlservr+0000560F) * 00603FF5 Module(sqlservr+00203FF5) (SQLExit+0009C4FE)


 * 0053577C Module(sqlservr+0013577C)


 * 00420A14 Module(sqlservr+00020A14)


 * 00874277 Module(sqlservr+00474277) (GetIMallocForMsxml+0007F6F7)


 * 00875200 Module(sqlservr+00475200) (GetIMallocForMsxml+00080680)


 * 00875611 Module(sqlservr+00475611) (GetIMallocForMsxml+00080A91)


 * 005BB2F6 Module(sqlservr+001BB2F6) (SQLExit+000537FF)


 * 005BAAB9 Module(sqlservr+001BAAB9) (SQLExit+00052FC2)


 * 00866D25 Module(sqlservr+00466D25) (GetIMallocForMsxml+000721A5)


 * 00868002 Module(sqlservr+00468002) (GetIMallocForMsxml+00073482)


 * 00868B1E Module(sqlservr+00468B1E) (GetIMallocForMsxml+00073F9E)


 * 0087E1CD Module(sqlservr+0047E1CD) (GetIMallocForMsxml+0008964D)


 * 0087E422 Module(sqlservr+0047E422) (GetIMallocForMsxml+000898A2)


 * 0055C692 Module(sqlservr+0015C692)


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


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


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


 * 77E66063 Module(kernel32+00026063) (GetModuleFileNameA+000000EB)




 * Dump thread - spid = 57, PSS = 0x530731f8, EC = 0x53073528

Additionally, the following events are logged in the Application log:

Event 1 Error 17055  MSSQLSERVER DUALP Server  \  17310 : SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

Event 2 Information 17052  MSSQLSERVER DUALP Server N/A Error: 17883, Severity: 1, State: 0 Process 56:51 (c84) UMS Context 0x0029DF20 appears to be non-yielding on Scheduler 1



CAUSE
This problem occurs because operators are converted incorrectly in the compiled plan for an execution plan.



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, but it is only intended to correct the problem that is described in this article. Only apply it 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 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:

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
 Microsoft SQL Server 2000 Service Pack 4 (SP4)

For information about how to obtain SQL Server 2000 SP4, 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. However, the hotfix installation stops and then restarts the MSSQLSERVER service.

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 tool in Control Panel.

SQL Server 2000 Itanium architecture version
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



WORKAROUND
To work around this problem, use one or both of the following methods:  Rewrite the Transact-SQL query, and modify the indexes that create a different execution plan.  Use the following query hint to turn off the parallel query. OPTION (MAXDOP 1) </ul>

<div class="status_section">

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

<div class="moreinformation_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 the terminology that Microsoft uses when Microsoft corrects software after it is released, 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

Additional query words: SDES SetLockInfo violation av sql worktable

Keywords: kbbug kbfix kbqfe kbhotfixserver KB909089

-

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

© Microsoft Corporation. All rights reserved.