Microsoft KB Archive/937683

= Error message when you try to restore a database by using SQL Server Management Studio in SQL Server 2005 after you use the Backup tool: &quot;Restore failed for Server '' (Microsoft.SqlServer.Smo)&quot; =

Article ID: 937683

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

-



SYMPTOMS
Consider the following scenario. The SQL Writer service is running on a computer that has Microsoft SQL Server 2005 installed. You use SQL Server Management Studio to back up a database. Additionally, you use the Backup tool (NTBackup.exe) to back up the database files. Then, you try to restore the database from the backup set by using SQL Server Management Studio. In this scenario, you receive an error message that resembles the following:

Restore failed for Server ' '. (Microsoft.SqlServer.Smo)

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: Cannot open backup device ' '. Operating system error 2(The system cannot find the file specified.). (Microsoft.SqlServer.Smo)

If you examine the start date and the finish date of the backup set, you find that the dates are updated to the date that you used the Backup tool.



CAUSE
This problem occurs because the Backup tool uses the SQL Writer service to back up SQL Server 2005 databases. The Backup tool triggers the SQL Writer service to create a snapshot. After the SQL Writer service creates the snapshot, the Backup tool determines whether the database files are on the exclude list. The database files include .ldf files and .mdf files. If the database files are on the exclude list, the Backup tool deletes the database files from the snapshot. However, the Backup tool adds entries in the backupset table in the msdb database.



RESOLUTION
To resolve this problem, stop the SQL Writer service when you use the Backup tool if you use both the Backup tool and the SQL Server 2005 backup functionality on the computer. Do not use the Backup tool to back up the database files. Instead, use the built-in functionality in SQL Server 2005 to back up the database.



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
If you examine the SQL Server error log file, you find messages that resemble the following message for the user databases and for the system databases:

I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

I/O was resumed on database model. No user action is required.

Backup Database backed up. Database: master, creation date(time):, pages dumped: 1, first LSN: 300:248:52, last LSN: 301:120:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {' '}). This is an informational message only. No user action is required.

Keywords: kbtshoot kbprb kbexpertiseadvanced kbsql2005engine KB937683

-

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

© Microsoft Corporation. All rights reserved.