FIX: Error message when you run queries on a database that has the SNAPSHOT isolation level enabled in SQL Server 2005: "Unable to deallocate a kept page"

Article translations Article translations
Article ID: 949199 - View products that this article applies to.
Bug #: 50002473 (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.
Expand all | Collapse all

On This Page

SUMMARY

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

SYMPTOMS

In Microsoft SQL Server 2005, you enable the SNAPSHOT isolation level for a database. When you run queries on the database, you may receive the following error message:
Error 831, Severity 20, State 1 - "Unable to deallocate a kept page"

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:
http://support.microsoft.com/contactus/?ws=support
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

You must have SQL Server 2005 Service Pack 2 installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 2, 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 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, 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3230.068,63221-Feb-200822:37x86
Chsbrkr.dll12.0.7822.01,684,84022-Jun-200709:22x86
Chtbrkr.dll12.0.7822.06,112,61622-Jun-200709:22x86
Databasemailprotocols.dll9.0.3230.046,10421-Feb-200822:37x86
Distrib.exe2005.90.3230.070,68021-Feb-200822:37x86
Dts.dll2005.90.3230.01,102,36021-Feb-200822:37x86
Dtsconn.dll2005.90.3230.0250,39221-Feb-200822:37x86
Dtspipeline.dll2005.90.3230.0605,20821-Feb-200822:37x86
Fteref.dll12.0.7822.0446,46422-Jun-200709:22x86
Infosoft.dll12.0.7822.0468,32822-Jun-200709:22x86
Korwbrkr.dll12.0.7822.071,01622-Jun-200709:22x86
Langwrbk.dll12.0.7822.0136,55222-Jun-200709:22x86
Mergetxt.dll2005.90.3230.032,28021-Feb-200822:37x86
Microsoft.analysisservices.dll9.0.3230.01,217,56021-Feb-200822:37x86
Microsoft.sqlserver.connectioninfo.dll9.0.3230.0156,69621-Feb-200822:37x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3230.0115,73621-Feb-200822:37x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3230.0295,96021-Feb-200822:37x86
Microsoft.sqlserver.replication.dll2005.90.3230.01,628,18421-Feb-200822:37x86
Microsoft.sqlserver.servicebrokerenum.dll9.0.3230.042,00821-Feb-200822:37x86
Microsoft.sqlserver.smo.dll9.0.3230.01,606,68021-Feb-200822:37x86
Microsoft.sqlserver.smoenum.dll9.0.3230.0222,23221-Feb-200822:37x86
Microsoft.sqlserver.sqlenum.dll9.0.3230.0898,07221-Feb-200822:37x86
Msfte.dll12.0.7822.02,430,31222-Jun-200709:22x86
Msftefd.exe12.0.7822.066,92022-Jun-200709:22x86
Msftepxy.dll12.0.7822.095,59222-Jun-200709:22x86
Msftesql.exe12.0.7822.095,59222-Jun-200709:22x86
Msgprox.dll2005.90.3230.0200,21621-Feb-200822:42x86
Msir5jp.dll5.0.2130.03,159,91222-Jun-200709:22x86
Nlhtml.dll12.0.7822.0124,26422-Jun-200709:22x86
Nls400.dll5.0.4217.012,240,74422-Jun-200709:22x86
Odsole70.dll2005.90.3230.058,90421-Feb-200822:42x86
Osql.exe2005.90.3230.053,27221-Feb-200822:42x86
Query9x.dll12.0.7822.048,48822-Jun-200709:22x86
Rdistcom.dll2005.90.3230.0644,63221-Feb-200822:42x86
Replerrx.dll2005.90.3230.0114,71221-Feb-200822:42x86
Replisapi.dll2005.90.3230.0272,92021-Feb-200822:42x86
Replmerg.exe2005.90.3230.0320,53621-Feb-200822:42x86
Replprov.dll2005.90.3230.0552,98421-Feb-200822:42x86
Replrec.dll2005.90.3230.0785,43221-Feb-200822:42x86
Replsub.dll2005.90.3230.0408,08821-Feb-200822:42x86
Replsync.dll2005.90.3230.0101,40021-Feb-200822:42x86
Sac.exe9.0.3230.082,96821-Feb-200822:42x86
Sbmsmdlocal.dll9.0.3230.015,969,30421-Feb-200822:42x86
Sbmsmdredir.dll9.0.3230.04,022,80821-Feb-200822:42x86
Sqlaccess.dll2005.90.3230.0350,23221-Feb-200822:42x86
Sqladhlp.exe2005.90.3230.047,12821-Feb-200822:42x86
Sqlagent90.exe2005.90.3230.0349,72021-Feb-200822:42x86
Sqlbrowser.exe2005.90.3230.0242,71221-Feb-200822:42x86
Sqlcmd.exe2005.90.3230.0143,38421-Feb-200822:42x86
Sqlctr90.dll2005.90.3230.067,60821-Feb-200822:42x86
Sqldiag.exe2005.90.3230.01,074,20021-Feb-200822:42x86
Sqldumper.exe2005.90.3230.068,63221-Feb-200822:42x86
Sqlmaint.exe2005.90.3230.077,84821-Feb-200822:42x86
Sqlmergx.dll2005.90.3230.0194,07221-Feb-200822:42x86
Sqlmgmprovider.dll2005.90.3230.0236,56821-Feb-200822:42x86
Sqlsac.exe2005.90.3230.01,246,23221-Feb-200822:42x86
Sqlservr.exe2005.90.3230.029,215,76821-Feb-200822:42x86
Sqlsqm.exe9.0.3230.0128,02421-Feb-200822:42x86
Sqlwep.dll2005.90.3230.090,64821-Feb-200822:42x86
Sqlwtsn.exe9.0.3230.099,35221-Feb-200822:42x86
Sqsrvres.dll2005.90.3230.070,16821-Feb-200822:42x86
Ssradd.dll2005.90.3230.042,52021-Feb-200822:42x86
Ssravg.dll2005.90.3230.043,03221-Feb-200822:42x86
Ssrmax.dll2005.90.3230.040,98421-Feb-200822:42x86
Ssrmin.dll2005.90.3230.040,98421-Feb-200822:42x86
Ssrpub.dll2005.90.3230.030,23221-Feb-200822:42x86
Svrenumapi.dll2005.90.3230.0615,44821-Feb-200822:42x86
Sablediff.exe9.0.3230.087,06421-Feb-200822:42x86
Thawbrkr.dll12.0.7822.0206,18422-Jun-200709:22x86
Xmlfilt.dll12.0.7822.0197,99222-Jun-200709:22x86
Xmlsub.dll2005.90.3230.0194,58421-Feb-200822:42x86
Xpadsi90.exe2005.90.3230.050,71221-Feb-200822:42x86
Xpqueue.dll2005.90.3230.056,85621-Feb-200822:42x86
Xprepl.dll2005.90.3230.073,24021-Feb-200822:42x86
Xpstar90.dll2005.90.3230.0298,52021-Feb-200822:42x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" 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

Important information for SQL Server 2005 Analysis Services

A known issue exists in Cumulative Update 7 for SQL Server 2005 Analysis Services. Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 SP2. In SQL Server Profiler, you start a trace or stop a trace. Then, you run a query. The execution time of the query exceeds the value of the ForceCommitTimeout server setting. In this scenario, all the queries that are running on the server are canceled. To work around this issue, do not run MDX queries before you start a trace or stop a trace.

Properties

Article ID: 949199 - Last Review: May 6, 2008 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
Keywords: 
kbautohotfix kbpubtypekc kbhotfixserver kbexpertiseadvanced kbqfe kberrmsg kbfix KB949199

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com