Article ID: 972687 - Last Review: August 20, 2009 - Revision: 3.2

FIX: Error message when you restore a SQL Server 2000 database by using SQL Server 2005 Management Studio or SQL Server 2008 Management Studio: "Cannot show requested dialog. Failed to retrieve data for this request (Microsoft.SqlServer.SmoEnum)"

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
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.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario.
  • You are running one of the following versions of SQL Server Management Studio:
    • SQL Server 2005 Service Pack 2 (SP2) Management Studio, version 9.00.3325 to 9.00.3329
      Note For example, you install SQL Server 2005 SP2 Cumulative Update 13, and the version of Management Studio is 9.00.3325.
    • SQL Server 2005 Service Pack 3 (SP3) Management Studio, version 9.00.4220 to 9.00.4228
      Note For example, you install SQL Server 2005 SP3 Cumulative Update 3, and the version of Management Studio is 9.00.4220.
    • The release version of SQL Server 2008 Management Studio, version 10.00.1806 to 10.00.1813
      Note For example, you install SQL Server 2008 Cumulative Update 5, and the version of Management Studio is 10.00.1806.
    • SQL Server 2008 Service Pack 1 (SP1) Management Studio, version 10.00.2714 to 10.00.2725
      Note For example, you install SQL Server 2008 SP1 Cumulative Update 2, and the version of Management Studio is 10.00.2714.
  • You use one of these versions of SQL Server Management Studio to connect to a SQL Server 2000 instance.
  • You perform a backup operation on a database in the SQL Server 2000 instance.
  • In SQL Server Management Studio, you right-click the database to perform a restore operation in this SQL Server 2000 instance.
In this scenario, you receive the following error message:

===================================
Cannot show requested dialog.
===================================
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Program Location:

at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.GetBackupSetsFromHistory(String DatabaseName)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.comboDatabaseSource_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.InitializeProperties()
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.OnHosted()
at Microsoft.SqlServer.Management.SqlMgmt.SqlManagementUserControl.SetSite(IServiceProvider sp)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.ProcessAllViews()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Program Location:

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query)
at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(StringCollection query, Object con, StatementBuilder sb)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
at Microsoft.SqlServer.Management.Smo.RestorePlan.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
===================================
Line 235: Incorrect syntax near '('.
Line 296: Incorrect syntax near '('.
Line 362: Incorrect syntax near '('.
Line 413: Incorrect syntax near '('.
Line 474: Incorrect syntax near '('.
Line 548: Incorrect syntax near '('.
Line 610: Incorrect syntax near '('.
Line 651: Incorrect syntax near '('.
Line 690: Incorrect syntax near '('. (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2282&EvtSrc=MSSQLServer&EvtID=170&LinkId=20476
------------------------------
Server Name: <Server Name>
Error Number: 170
Severity: 15
State: 1
Line Number: 235

------------------------------

Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand)
Back to the top

RESOLUTION

To resolve this problem, use the following table to find the appropriate method for your version of SQL Server.
Collapse this tableExpand this table
SQL Server releaseCumulative update (version of SQL Server)Resolution
SQL Server 2005 SP29.00.3325 to 9.00.3329Apply SQL Server 2005 SP2 Cumulative update package 15.
SQL Server 2005 SP39.00.4220 to 9.00.4228Apply SQL Server 2005 SP3 Cumulative update package 5.
The release version of SQL Server 200810.00.1806 to 10.00.1813Apply the individual hotfix for the release version of SQL Server 2008. To obtain this hotfix, refer to the "Hotfix information" section in this article. Or, apply SQL Server 2008 Cumulative update package 7.
SQL Server 2008 SP110.00.2714 to 10.00.2725Apply the individual hotfix for the SQL Server 2008 Service Pack 1. To obtain this hotfix, refer to the "Hotfix information" section in this article. Or, Apply SQL Server 2008 Service Pack 1 Cumulative update package 4.
Back to the top

Cumulative update information

SQL Server 2005 Service Pack 2 (SP2)

Important You must install this hotfix if you are running SQL Server 2005 Service Pack 2 (SP2). The fix for this issue was first released in Cumulative Update 15 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972510   (http://support.microsoft.com/kb/972510 /LN/ ) Cumulative update package 15 for SQL Server 2005 Service Pack 2
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 2005 fix release. Microsoft recommends 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:
937137  (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3 (SP3)

Important You must install this hotfix if you are running SQL Server 2005 Service Pack 3 (SP3). The fix for this issue was also released in Cumulative Update 5 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972511   (http://support.microsoft.com/kb/972511 /LN/ ) Cumulative update package 5 for SQL Server 2005 Service Pack 3
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 2005 fix release. Microsoft recommends 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:
960598  (http://support.microsoft.com/kb/960598/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008

Important You must use this fix if you are running the release version of SQL Server 2008.

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, click the following article number to view the article in the Microsoft Knowledge Base:
973601  (http://support.microsoft.com/kb/973601/ ) Cumulative update package 7 for SQL Server 2008
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 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:
956909  (http://support.microsoft.com/kb/956909/ ) The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must use this fix if you are running SQL Server 2008 Service Pack 1.

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
973602  (http://support.microsoft.com/kb/973602/LN/ ) Cumulative update package 4 for SQL Server 2008 Service Pack 1
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 fix release. Microsoft recommends 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:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top

Hotfix information

Back to the top

Hotfix information

The release version of SQL Server 2008

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 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 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 Web site:
http://support.microsoft.com/contactus/?ws=support (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 the release version of SQL Server 2008 installed on your computer.

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

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.


SQL Server 2008 Service Pack 1

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 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 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 Web site:
http://support.microsoft.com/contactus/?ws=support (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 SQL Server 2008 Service Pack 1 installed on your computer.

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

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.


Back to the top

WORKAROUND

To work around this problem, use one of the following methods.

Method 1

Use Transact-SQL statements to restore the database. For example, you can use the following command to restore a database:
restore database Database Name from disk = 'Backup file'
Method 2

To restore the database by using SQL Server Management Studio, following these steps:
  1. Do not right-click the database. Instead, right-click the Database node, and then click Restore Database.
  2. Do not select the From database option under Source for restore. Instead, select the From device option.
  3. Follow the instructions to complete the restore operation.
Back to the top

STATUS

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

MORE INFORMATION

To know whether the version of SQL Server Management Studio that is installed on your computer is affected by this problem, check whether the version of the Microsoft.SqlServer.SqlEnum.dll file matches one of the affected versions in the "Symptoms" section. Generally, the Microsoft.SqlServer.SqlEnum.dll file is in one of the following folders, depending on whether SQL Server is installed by using Windows on Windows (WOW) mode.

SQL Server 2005

drive:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
drive:\Program Files (x86)\Microsoft SQL Server\90\SDK\Assemblies

SQL Server 2008

drive:\Program Files\Microsoft SQL Server\100\SDK\Assemblies
drive:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies
Back to the top

REFERENCES

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise 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 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Workgroup
Back to the top
Keywords: 
kbhotfixserver kbautohotfix kbsurveynew kbexpertiseadvanced kbqfe kbfix KB972687
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers