"RESTORE DATABASE is terminating abnormally" error message when you perform a full backup of a database in SQL Server 2008 R2

Article translations Article translations
Article ID: 2487231 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You create a database in Microsoft SQL Server 2008 R2.
  • You update the logical name of the database by using the ALTER DATABASE statement.
  • You perform a full backup of the database.

    Note A full database backup file is generated after the backup is performed.
  • You try to restore the database from the database backup file.
In this scenario, you receive the following error message:
Msg 3234, Level 16, State 2, Line 1
Logical file '<logical file name>' is not part of database '<database name>'. Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
If you use the RESTORE FILELISTONLY statement to check the backup file, you find that the logical file name that you updated is corrupted. The last character of the logical file name is truncated. For example, you try to update the logical name for a database to DB_modified. However, it is incorrectly changed to DB_modifie in the backup file.

Note This issue does not occur if you restart the SQL Server service after the logical file name is updated.

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2489376 Cumulative Update package 6 for SQL Server 2008 R2
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 2008 R2 fix release. We recommend 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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

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 the problem described in this article. 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 website:
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

To apply this hotfix, you must have Microsoft SQL Server 2008 R2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

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.
32-bit SQL Server 2008 R2 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
atxcore.dll2009.100.1755.02646424-Dec-100:33x86
datacollectorcontroller.dll2009.100.1755.013552024-Dec-100:33x86
etwcls.mofNot applicable 111632823-Dec-103:54Not applicable
instmsdb.sqlNot applicable 224126022-Dec-1020:49Not applicable
mssqlsystemresource.ldfNot applicable 52428822-Dec-1022:52Not applicable
mssqlsystemresource.mdfNot applicable 6356992022-Dec-1022:52Not applicable
sql_engine_core_inst_keyfile.dll2009.100.1755.01366424-Dec-100:31x86
sqlaccess.dll2009.100.1755.041558424-Dec-100:29x86
sqlagent.exe2009.100.1755.036796824-Dec-100:34x86
sqlagent100_msdb_upgrade.sqlNot applicable 237124523-Dec-103:53Not applicable
sqlos.dll2009.100.1755.01468824-Dec-100:22x86
sqlscriptdowngrade.dll2009.100.1755.01468824-Dec-100:21x86
sqlscriptupgrade.dll2009.100.1755.0461142424-Dec-100:21x86
sqlservr.exe2009.100.1755.04290492824-Dec-100:34x86
sqsrvres.dll2009.100.1755.08995224-Dec-100:21x86
64-bit SQL Server 2008 R2 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
atxcore.dll2009.100.1755.03158423-Dec-1023:40x64
datacollectorcontroller.dll2009.100.1755.026249623-Dec-1023:40x64
etwcls.mofNot applicable111632823-Dec-103:54Not applicable
instmsdb.sqlNot applicable224126022-Dec-1020:49Not applicable
mssqlsystemresource.ldfNot applicable52428822-Dec-1022:52Not applicable
mssqlsystemresource.mdfNot applicable6356992022-Dec-1022:52Not applicable
sql_engine_core_inst_keyfile.dll2009.100.1755.01417623-Dec-1023:40x64
sqlaccess.dll2009.100.1755.040329623-Dec-1023:38x86
sqlagent.exe2009.100.1755.042838423-Dec-1023:40x64
sqlagent100_msdb_upgrade.sqlNot applicable237124523-Dec-103:53Not applicable
sqlos.dll2009.100.1755.01571223-Dec-1023:37x64
sqlscriptdowngrade.dll2009.100.1755.01571223-Dec-1023:37x64
sqlscriptupgrade.dll2009.100.1755.0461091223-Dec-1023:37x64
sqlservr.exe2009.100.1755.06195798423-Dec-1023:40x64
sqsrvres.dll2009.100.1755.010582423-Dec-1023:37x64
Itanium-architecture SQL Server 2008 R2 Database Services Core Instance
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
atxcore.dll2009.100.1755.06332823-Dec-1023:05ia64
datacollectorcontroller.dll2009.100.1755.047702423-Dec-1023:05ia64
etwcls.mofNot applicable111632823-Dec-103:54Not applicable
instmsdb.sqlNot applicable224126022-Dec-1020:49Not applicable
mssqlsystemresource.ldfNot applicable52428822-Dec-1022:52Not applicable
mssqlsystemresource.mdfNot applicable6356992022-Dec-1022:52Not applicable
sql_engine_core_inst_keyfile.dll2009.100.1755.01929623-Dec-1023:05ia64
sqlaccess.dll2009.100.1755.039203223-Dec-1023:01x86
sqlagent.exe2009.100.1755.0120560023-Dec-1023:09ia64
sqlagent100_msdb_upgrade.sqlNot applicable237124523-Dec-103:53Not applicable
sqlos.dll2009.100.1755.02236823-Dec-1022:56ia64
sqlscriptdowngrade.dll2009.100.1755.02083223-Dec-1022:56ia64
sqlscriptupgrade.dll2009.100.1755.0461705623-Dec-1022:56ia64
sqlservr.exe2009.100.1755.012176265623-Dec-1023:09ia64
sqsrvres.dll2009.100.1755.018876823-Dec-1022:56ia64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

WORKAROUND

To work around this issue, use one of the following two methods:
  • After the logical file name is modified, run the following statements to restart the database:
    ALTER DATABASE <database name> SET OFFLINE
    ALTER DATABASE <database name> SET ONLINE
  • When you modify the logical file name, append a dummy space character in the new logical name. For example, if you want to change the logical name to DB_modified, use the following statement to modify the logical file name:
    ALTER DATABASE <database name> MODIFY FILE (NAME=N'<database name>', NEWNAME='DB_modified ') -- Append ' ' to NEWNAME

REFERENCES

For more information about the ALTER DATABASE Transact-SQL statement, visit the following Microsoft Developer Network (MSDN) website:
General information about the ALTER DATABASE Transact-SQL statement
For more information about the RESTORE FILELISTONLY Transact-SQL statement, visit the following Microsoft Developer Network (MSDN) website:
General information about the RESTORE FILELISTONLY Transact-SQL statement

Properties

Article ID: 2487231 - Last Review: February 21, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Standard Edition for Small Business
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2487231

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