Microsoft KB Archive/937544

= FIX: You may receive error 3456 when you try to restore a transaction log for a SQL Server 2005 database =

Article ID: 937544

Article Last Modified on 11/20/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 #: 50001267 (SQL Hotfix)



Notice
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 the hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you try to restore a transaction log for a Microsoft SQL Server 2005 database, you may receive error 3456. When this error occurs, you cannot continue restoring the transaction log.

Additionally, when you examine the SQL Server Errorlog file, it resembles the following:

2007-03-29 16:00:35.43 spid59 Error: 17053, Severity: 16, State: 1.

2007-03-29 16:00:35.43 spid59 G:\MSSQL\DATA\attach_space_079.ndf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-03-29 16:00:35.45 spid59 Error: 5149, Severity: 16, State: 1.

2007-03-29 16:00:35.45 spid59 MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file.

...

2007-04-14 13:11:58.82 spid56 Error: 3456, Severity: 16, State: 1.

2007-04-14 13:11:58.82 spid56 Could not redo log record (509687:1091266:3), for transaction ID (0:84708793), on page (67:57769216), database 'custdata' (database ID 7). Page: LSN = (508062:635535:172), type = 8. Log: OpCode = 7, context 8, PrevPageLSN: (509687:1090182:20). Restore from a backup of the database, or repair the database.



CAUSE
This problem occurs when you receive errors 17053 and 5149 before you try to restore the transaction log. Errors 17053 and 5149 occur when error 112 occurs. Error 112 occurs because there is not enough space on the disk.



RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
 SQL Server 2005 Service Pack 1

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 have to restart the computer only if all SQL Server components are not shut down before you install this hotfix. The hotfix installer will inform you of any running SQL Server components that must be shut down so that you can shut down them to avoid a system restart.

Hotfix replacement information
This hotfix is not replaced by any other hotfixes.

Registry information
You do not have to change the registry.

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, Itanium architecture version


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

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005engine KB937544

-

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

© Microsoft Corporation. All rights reserved.