Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 934713 - Last Review: June 26, 2007 - Revision: 1.3
FIX: Error message when you run the CHECKPOINT statement after you restore a database that has a read-only user-defined filegroup in SQL Server 2005: "The operating system returned error 5(Access is denied.) to SQL Server"
Bug #: 50001046 (SQL Hotfix)
Consider the following scenario in Microsoft SQL Server 2005:
- You restore a database.
- The database has a user-defined filegroup.
- The user-defined filegroup is marked as read-only.
In this scenario, when you run the CHECKPOINT statement against the database, you receive the following error message:
Msg 823, Level 24, State 3, Line 1
The operating system returned error 5(Access is denied.) to SQL Server during a write at offset 0x0000000000e000 in file 'FilePath\FileName'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
If you then restart the SQL Server service, the database does not recover. Additionally, the database enters the suspect state. When you examine the SQL Server 2005 Errorlog file, you find error messages that resemble the following:
Date Time SPID 0 transactions rolled back in database 't' (7). This is an informational message only. No user action is required.
Date Time SPID Recovery is writing a checkpoint in database 't' (7). This is an informational message only. No user action is required.
Date Time SPID Error: 823, Severity: 24, State: 3.
Date Time SPID The operating system returned error 5(Access is denied.) to SQL Server during a write at offset 0x0000000000e000 in file 'c:\t.ro.1.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Date Time SPID Error: 3414, Severity: 21, State: 2.
Date Time SPID An error occurred during recovery, preventing the database 't' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Date Time SPID Recovery is complete. This is an informational message only. No user action is required.
Cumulative update information
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305Â
(http://kbalertz.com/Feedback.aspx?kbNumber=936305/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137Â
(http://kbalertz.com/Feedback.aspx?kbNumber=937137/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problem
- Create a database that has a user-defined filegroup.
- Set the database to use the bulk-logged recovery model.
- Perform bulk operations against objects in the user-defined filegroup.
- Mark the user-defined filegroup as read-only.
- Perform a backup for the database.
- Restore the database to overwrite the original database.
- Run the CHECKPOINT statement against the database.
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Workgroup Edition
| kbsql2005as kbexpertiseadvanced kbfix kbpubtypekc kbqfe KB934713 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please