SQL Server Q&A

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 the SQL Server errorlog 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 Update4 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 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?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes 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 2008Important 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?(http://support.microsoft.com/kb/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?(http://support.microsoft.com/kb/956909/) The SQL Server 2008 builds that were released after SQL Server 2008 was released

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you have a database that has query notification enabled. You back up the database, and then you try to restore the database from this backup. However, the restore operation may fail during the recovery phase.
This issue may also occur during the recovery phase of a regular startup of the database.

When this problem occurs, a mini-dump file is generated in the SQL Server log folder. Additionally, the following error message is logged in the SQL Servererror log file:

<Date><Time> spid61* *******************************************************************************
<Date><Time> spid61*
<Date><Time> spid61* BEGIN STACK DUMP:
<Date><Time> spid61*08/13/09 04:15:19 spid 61
<Date><Time> spid61*
<Date><Time> spid61* Server was configured to produce dump on the following event – ex_raise2: Exception raised, major=97, minor=68, state=1, severity=16
<Date><Time> spid61*2009-08-13 04:15:19.57 spid61* Input Buffer 510 bytes -
<Date><Time> spid61*<Restore database statement>
<Date><Time> spid61Error: 9768, Severity: 16, State: 1.
<Date><Time> spid61A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER while conversations are being created.
<Date><Time> spid61Failed to check for pending query notifications in database “36″ because of the following error when opening the database: ‘A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER while conversations are being created. The query notification subscriptions cleanup operation failed. See previous errors for details.’.
<Date><Time> spid61Error: 9001, Severity: 16, State: 5.
<Date><Time> spid61The log for database <Database Name> is not available. Check the event log for related error messages. Resolve any errors and restart the database.
<Date><Time> spid61Error: 3314, Severity: 21, State: 4.
<Date><Time> spid61During undoing of a logged operation in database <Database Name>, an error occurred at log record ID (1835:7401:137). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Resolution
The issue occurs because query notifications are sent to a user who has been dropped from the database before the database has been backed up. When you restore the database, SQL Server tries to redo all the query notification transactions as part of database startup. However, processing of query notifications fails because the user does not exist, and an error 9768 is raised. This error is not handled appropriately by SQL Server, and the severity of this error is increased. This causes recovery transaction to fail, and then the restore operation fails.

Symptoms
In Microsoft SQL Server 2008, an access violation occurs intermittently during message processing for service broker,and the session may be disconnected. When this problem occurs, a mini-dump file is generated in the SQL Server log folder, and the following error message is logged in the SQL Server log file:

<Date><Time> spid18s***Stack Dump being sent to <drive>:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\SQLDump0005.txt
<Date><Time> spid18sSqlDumpExceptionHandler: Process 18 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
<Date><Time> spid18s* *******************************************************************************
<Date><Time> spid18s*
<Date><Time> spid18s* BEGIN STACK DUMP:
<Date><Time> spid18s*<Date><Time> spid <spid>
<Date><Time> spid18s*
<Date><Time> spid18s*
<Date><Time> spid18s*Exception Address = 0000000002164AC2 Module(sqlservr+0000000001164AC2)
<Date><Time> spid18s*Exception Code= c0000005 EXCEPTION_ACCESS_VIOLATION
<Date><Time> spid18s*Access Violation occurred reading address 0000000000000000
<Date><Time> spid18sStack Signature for the dump is 0×00000001CCC51BCC
<Date><Time> spid18sExternal dump process return code 0×20000001.External dump process returned no errors.
<Date><Time> spid15sThe Service Broker protocol transport has stopped listening for connections.
<Date><Time> spid15sService Broker manager has shut down.
Resolution
The fix for this issue was first released in Cumulative Update5 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:
975977?(http://support.microsoft.com/kb/975977/LN/) Cumulative update package 5 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?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes 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.

Symptoms
When you install Microsoft SQL Server 2008, the following error message is logged in the setup log file:

Date Time Slp: An error occurred while processing item 10 defined on lines 73 – 79 in file C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof:
Date Time Slp: Compiler returned error 0×80004002Error Number: 0×80004002, Facility: <Null>
Date Time Slp: Description: No such interface supported
Date Time Slp:
Date Time Slp: Sco: Compile operation for mof file C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
Date Time Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
Resolution
This issue occurs because of a Windows Management Instrumentation (WMI) configuration issue on the computer where you run the SQL Server 2008 Setup program. This is an operating system issue. Therefore, you must resolve the issue before you install SQL Server 2008 on the computer.