FIX: An EXCEPTION_STACK_OVERFLOW exception may occur when you try to run a Transact-SQL query in SQL Server 2005

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 1023 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
SUMMARY
This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package
SYMPTOMS
When you try to run a Transact-SQL query in Microsoft SQL Server 2005, an EXCEPTION_STACK_OVERFLOW exception may occur. When this problem occurs, the SQL Server service may stop unexpectedly.

Note This problem may only occur in SQL Server 2005 x64 editions.
RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed on the computer.For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

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 of 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.SQL Server 2005, 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2181.0522,52815-Aug-200608:20x64
Microsoft.analysisservices.adomdclient.dll9.0.2181.0543,52015-Aug-200608:20x86
Microsoft.analysisservices.adomdclient.dll9.0.2181.0543,52015-Aug-200608:28x86
Microsoft.analysisservices.deploymentengine.dll9.0.2181.0138,01615-Aug-200608:26x86
Microsoft.analysisservices.dll9.0.2181.01,215,26415-Aug-200608:26x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2181.091,42415-Aug-200608:19x64
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2181.075,55215-Aug-200608:25x86
Microsoft.sqlserver.sqlenum.dll9.0.2181.0875,29615-Aug-200608:21x86
Msgprox.dll2005.90.2181.0259,36015-Aug-200608:20x64
Msmdlocal.dll9.0.2181.015,703,84015-Aug-200608:27x86
Msmdredir.dll9.0.2181.03,968,80015-Aug-200608:27x86
Replprov.dll2005.90.2181.0745,24815-Aug-200608:21x64
Replrec.dll2005.90.2181.01,008,41615-Aug-200608:19x64
Sqlaccess.dll2005.90.2181.0355,10415-Aug-200608:20x86
Sqlagent90.exe2005.90.2181.0390,94415-Aug-200608:20x64
Sqlservr.exe2005.90.2181.039,327,52015-Aug-200608:20x64
Xpstar90.dll2005.90.2181.0540,44815-Aug-200608:20x64
Xpstar90.rll2005.90.2181.0153,37615-Aug-200608:19x64
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
When the problem occurs, information that resembles the following is logged in the SQL Server error log file:

2006-06-09 22:08:22.23 spid55      06/09/06 22:08:22 Stack Overflow Dump not possible - Exception c00000fd EXCEPTION_STACK_OVERFLOW at 0x00000000018C4E672006-06-09 22:08:22.23 spid55      SqlDumpExceptionHandler: Address=0x00000000018C4E67 Exception Code = c00000fd2006-06-09 22:08:22.23 spid55      Rax=00000000000040a0 Rbx=000000008f356d10 Rcx=000000008f356e40 Rdx=000000008f6ce0502006-06-09 22:08:22.23 spid55      Rsi=0000000001613270 Rdi=000000008f356d10 Rip=00000000018c4e67 Rsp=000000000da75ba82006-06-09 22:08:22.23 spid55      Rbp=000000000da75c10 EFlags=00000000000102872006-06-09 22:08:22.23 spid55      cs=0000000000000033 ss=000000000000002b ds=000000000000002b es=000000000000002b fs=0000000000000053 gs=000000000000002b2006-06-09 22:08:22.23 spid55      <query here>2006-06-09 22:08:22.23 spid55      TotalPhysicalMemory = 4288049152, AvailablePhysicalMemory = 18738012162006-06-09 22:08:22.23 spid55      AvailableVirtualMemory = 8791461752832, AvailablePagingFile = 55428751362006-06-09 22:08:22.23 spid55      Stack Signature for the dump is 0x00000000000000002006-06-09 22:08:22.26 spid55      External dump process not executed. 2006-06-09 22:08:22.28 spid55      DoMiniDump () encountered error (0xC00000FD)2006-06-09 22:08:22.28 spid55      Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)2006-06-09 22:08:22.28 spid55      Stack Signature for the dump is 0x00000000000000002006-06-09 22:08:30.29 spid55      External dump process return code 0x20000001. External dump process returned no errors.
For more information, 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
Properties

Article ID: 922638 - Last Review: 12/09/2015 06:25:50 - Revision: 2.0

Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Standard X64 Edition

  • kbnosurvey kbarchive kbautohotfix kbexpertiseadvanced kbsql2005tsql kbHotfixServer kbqfe KB922638
Feedback