Symptoms
Assume that you have installed one of the following updates on a computer that has Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 installed:
-
Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1 (SP1) or later versions
-
Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2 (SP2) or later versions
In this situation, you run a RESTORE FILELISTONLY statement to restore a database in SQL Server 2008 R2. However, the restore operation fails. Additionally, you receive the following error message:
Message 3241, Level 16, State 1, Line 1
The media family on device '<BackupFilePath>' is incorrectly formed. SQL Server cannot process this media family.
Message 3013, Level 16, State 1, Line 1
RESTORE FILELIST is terminating abnormally.
Note If you run the DBCC CHECKDB statement in earlier builds of SQL Server 2008 R2, you experience no consistency error that indicates problems in the backup media. Therefore, the backup can be restored in these earlier versions.
Cause
The issue occurs because Cumulative Update 5 for SQL Server 2008 R2 SP1 and Cumulative Update 1 for SQL 2008 R2 SP2 perform a database completeness validation when the database is restored. However, this validation is not necessary for the RESTORE FILELISTONLY statement.
This validation was included in the hotfixes that are described in KB 2685132. For more information about the database completeness validation, click the following article number 2685132 to view the article 2685132 in the Microsoft Knowledge Base:
2685132 FIX: The log shipping restore job restores a corrupted transaction log backup to a secondary database when you run a log shipping backup job on an instance of SQL Server 2008 R2 or an instance of SQL Server 2012
Resolution
Cumulative update information
Cumulative Update 9 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2867319 Cumulative update package 9 for SQL Server 2012Note 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 2012 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Cumulative Update 5 for SQL Server 2012 Service Pack 1
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2861107 Cumulative update package 5 for SQL Server 2012 Service Pack 1Note 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 2012 Service Pack 1 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative Update 13 for SQL Server 2008 R2 SP1
The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2855792 Cumulative update package 13 for SQL Server 2008 R2 SP1Note 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 SP1 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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Cumulative Update 7 for SQL Server 2008 R2 SP2
The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
2844090 Cumulative update package 7 for SQL Server 2008 R2 SP2Note 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 SP2 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
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, run the RESTORE FILELISTONLY statement together with the CONTINUE_AFTER_ERROR option.
