FIX: Error message after you roll back transactions on a table in SQL Server 2005: "Error: 3315, Severity: 21, State: 1" (917886)
The information in this article applies to:
- Microsoft SQL Server 2005 Service Pack 1
Bug #: 745 (SQL Hotfix)
NoticeMicrosoft 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.This article describes the following about this hotfix release: - The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Information about whether you must restart the computer after you install the hotfix package
- Information about whether the hotfix package is replaced by any other hotfix package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMSIn SQL Server 2005, an error message that resembles the following is logged in the SQL Server error log after you roll back transactions on a table: Error: 3315, Severity: 21, State: 1 During rollback, the following process did not hold an expected lock: process 51 with mode 8 at level 2 for row Rid pageid is (1:73) and row num is 0x0 in database 'DatabaseName' under transaction (0:546). Restore a backup of the database, or repair the database. This problem occurs when page locks are disabled on the table before the transactions are rolled back. Notes- In the error message, DatabaseName represents the database that contains the table.
- You may have run the sp_indexoption stored procedure to disable the page locks on the table.
For more information about how to view the SQL Server error log, visit the following Microsoft Developer Network (MSDN) Web site: RESOLUTIONA 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 Microsoft SQL Server 2005 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: 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. PrerequisitesYou must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.
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 informationYou do not have to restart the computer after you apply this hotfix. Registry informationYou do not have to change the registry. Hotfix file informationThis 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 32-bit version |
Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 908,064 | 23-May-2006 | 10:04 | x86 | Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 75,552 | 23-May-2006 | 10:04 | x86 | Msmdlocal.dll | 9.0.2156.0 | 15,661,344 | 23-May-2006 | 10:05 | x86 | Sqlaccess.dll | 2005.90.2156.0 | 347,936 | 23-May-2006 | 10:04 | x86 | Sqlservr.exe | 2005.90.2156.0 | 28,937,560 | 23-May-2006 | 10:05 | x86 |
SQL Server 2005 x64-based version |
Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 875,296 | 24-May-2006 | 11:08 | x86 | Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 91,424 | 23-May-2006 | 10:04 | x64 | Msmdlocal.dll | 9.0.2156.0 | 15,661,344 | 23-May-2006 | 10:05 | x86 | Sqlaccess.dll | 2005.90.2156.0 | 355,104 | 24-May-2006 | 11:09 | x86 | Sqlservr.exe | 2005.90.2156.0 | 39,345,952 | 24-May-2006 | 11:08 | x64 |
SQL Server 2005 Itanium architecture version |
Microsoft.sqlserver.sqlenum.dll | 9.0.2156.0 | 875,296 | 24-May-2006 | 02:50 | x86 | Ms.ss.mgdsqldumper.dll | 2005.90.2156.0 | 75,552 | 23-May-2006 | 10:04 | x86 | Msmdlocal.dll | 9.0.2156.0 | 48,731,936 | 24-May-2006 | 02:49 | IA-64 | Sqlaccess.dll | 2005.90.2156.0 | 349,472 | 24-May-2006 | 02:50 | x86 | Sqlservr.exe | 2005.90.2156.0 | 72,186,144 | 24-May-2006 | 02:50 | IA-64 |
WORKAROUNDAlthough you receive this error message in the SQL Server error log, you can safely ignore this error message. The rollback operation should have completed successfully without causing any problems. If you do not want to receive this error message, you can enable page locks on the table. To enable page locks on the table, run the following statement: exec sp_indexoption '<TableName>', 'DisAllowPageLocks','FALSE' Note <TableName> represents the table on which you want to enable page locks. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbsql2005engine kbHotfixServer kbfix kbExpertiseAdvanced kbQFE kbpubtypekc KB917886 kbAudITPRO kbAudDeveloper |
---|
|