Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SQL Server reports error 17310 after you apply the fix from KB 2515286

SQL Server reports error 17310 after you apply the fix from KB 2515286

View products that this article applies to.

Symptoms

After applying the fix provided in the Knowledge Base article 2515286 on your SQL server, if you run a XQuery, you will notice the query encounters errors and the following messages are reported in the SQL Server Error log:

2011-05-30 07:31:36.60 spid76      Using 'dbghelp.dll' version '4.0.5'
2011-05-30 07:31:36.64 spid76      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0006.txt
2011-05-30 07:31:36.64 spid76      SqlDumpExceptionHandler: Process 76 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2011-05-30 07:31:36.64 spid76      * *******************************************************************************
2011-05-30 07:31:36.64 spid76      *
2011-05-30 07:31:36.64 spid76      * BEGIN STACK DUMP:
2011-05-30 07:31:36.64 spid76      *   05/30/11 07:31:36 spid 76
2011-05-30 07:31:36.64 spid76      *
2011-05-30 07:31:36.64 spid76      *
2011-05-30 07:31:36.64 spid76      *   Exception Address = 01003CA2 Module(sqlservr+00003CA2)
2011-05-30 07:31:36.64 spid76      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2011-05-30 07:31:36.64 spid76      *   Access Violation occurred writing address 010201A0

2011-05-30 07:31:39.10 Server      Error: 17310, Severity: 20, State: 1.
2011-05-30 07:31:39.10 Server      A user request from the session with SPID 76 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.


↑ Back to the top

Cause

This is due to a bug in the XQuery initialization fix released in article 2515286

↑ Back to the top

Resolution

 
Consult the following table to determine if you have a build that is affected by this problem and if a fix is available.


When the fix is released for SQL Server 2008 Service Pack 3, this KB article will be updated with that information.

For more information refer to the following links:

  • 2494113 MS11-049: Description of the security update for SQL Server 2005 Service Pack 3 GDR: June 14, 2011
  • 2494120 MS11-049: Description of the security update for SQL Server 2005 Service Pack 4 GDR: June 14, 2011
  • 2494096 MS11-049: Description of the security update for SQL Server 2008 Service Pack 1 GDR: June 14, 2011
  • 2494089 MS11-049: Description of the security update for SQL Server 2008 Service Pack 2 GDR: June 14, 2011
  • 2494088 MS11-049: Description of the security update for SQL Server 2008 R2 GDR: June 14, 2011
  • 2572407 FIX: Error 5180 when you use the ONLINE option to rebuild an index in SQL Server 2005
  • 2582282Cumulative update package 16 for SQL Server 2008 Service Pack 1
  • 2617148Cumulative update package 7 for SQL Server 2008 Service Pack 2
  • 2673383 Cumulative update package 4 for SQL Server 2008 Service Pack 3
  • 2633145Cumulative update package 11 for SQL Server 2008 R2
  • 2633146Cumulative update package 4 for SQL Server 2008 R2 Service Pack 1
  • 957826 Where to find information about the latest SQL Server builds



↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2587929
Revision : 1
Created on : 1/7/2017
Published on : 4/20/2012
Exists online : False
Views : 1015