Microsoft KB Archive/934713

= 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: &quot;The operating system returned error 5(Access is denied.) to SQL Server&quot; =

Article ID: 934713

Article Last Modified on 6/26/2007

-

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

-



Bug #: 50001046 (SQL Hotfix)



SYMPTOMS
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 ' '. 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:

0 transactions rolled back in database 't' (7). This is an informational message only. No user action is required.

Recovery is writing a checkpoint in database 't' (7). This is an informational message only. No user action is required.

Error: 823, Severity: 24, State: 3.

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.

Error: 3414, Severity: 21, State: 2.

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.

Recovery is complete. This is an informational message only. No user action is required.



Cumulative update information
To resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). For more information about how to obtain cumulative update package 2 (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:

936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce the problem

 * 1) Create a database that has a user-defined filegroup.
 * 2) Set the database to use the bulk-logged recovery model.
 * 3) Perform bulk operations against objects in the user-defined filegroup.
 * 4) Mark the user-defined filegroup as read-only.
 * 5) Perform a backup for the database.
 * 6) Restore the database to overwrite the original database.
 * 7) Run the CHECKPOINT statement against the database.

Keywords: kbsql2005as kbexpertiseadvanced kbfix kbpubtypekc kbqfe kbhotfixserver KB934713

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.