Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.

Symptoms

In Windows 7, you perform one of the following operations:

  • You install Microsoft SQL Server 2008 through the graphical user interface (GUI).

  • You upgrade from SQL Server 2000 or SQL Server 2005 to SQL Server 2008 through the GUI.

  • You install a SQL Server 2008 Cluster through the GUI.

  • You upgrade from a SQL Server 2000 cluster or SQL Server 2005 cluster to a SQL Server 2008 cluster through the GUI.

After you perform one of these operations, you may receive the following error message during the Setup Support Rule step of the installation:

Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

Additionally, the following error message may be logged in one of the Setup log files of the SQL Server setup. For example, the following error message may be logged in the Detail_LandingPage.txt file:

<Date><Time> Slp: Exception type: System.InvalidOperationException<Date><Time> Slp: Message: <Date><Time> Slp: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.<Date><Time> Slp: Stack: <Date><Time> Slp: at System.Windows.Forms.Control.WaitForWaitHandle(WaitHandle waitHandle)<Date><Time> Slp: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)<Date><Time> Slp: at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)<Date><Time> Slp: at Microsoft.SqlServer.Configuration.UIExtension.WaitScreen.Close()<Date><Time> Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker)<Date><Time> Slp: at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)<Date><Time> Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)<Date><Time> Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)<Date><Time> Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)<Date><Time> Slp: Rule evaluation done : Succeeded

Resolution

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 Cumulative update package 4 for SQL Server 2008 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 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 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft 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.

The release version of SQL Server 2008

Important You must install this fix if you are running the release version of SQL Server 2008.The fix for this issue was first released in Cumulative Update 8. 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:

975976 Cumulative update package 8 for SQL Server 2008Note 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 The SQL Server 2008 builds that were released after SQL Server 2008 was released

Status

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

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor 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 packagesFor 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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.