SQL Server Q&A

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

Symptoms
When an instance of the x86-based version of Microsoft SQL Server 2008 and an instance of the x64-based version of SQL Server 2008 are installed on an x64-based computer, and you try to install a new instance of one version after you uninstall the instance of the other version, the installation fails. For example, the installation fails if you try to install a new instance of the x64-based version after you uninstall the x86-based version.
When this problem occurs, the following errors appear in the SQL Server 2008 log:

Date Time Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.
Date Time Slp: System.ArgumentException: Cannot find service {0}.
Date Time Slp: Nazwa parametru: MSSQLServerADHelper100
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.ChangeServiceSecurity(EffectiveProperties properties)
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install_ConfigNonRC_Prepare(EffectiveProperties properties)
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
Date Time Slp:w Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
Date Time Slp: Exception: System.ArgumentException.
Date Time Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
Date Time Slp: Message: Cannot find service {0}.
Date Time Slp: Nazwa parametru: MSSQLServerADHelper100.Date
Resolution
This problem occurs because the SQL Server Active Directory Helper Service is removed when you uninstall any instance of SQL Server 2008. On an x64-based computer, both 32-bit instances and 64-bit instances share the SQL Server Active Directory Helper service. However, a separate reference count of the service is maintained for each platform. Therefore, when you uninstall the last instance of either platform, the SQL Server Active Directory Helper service is deleted.
If multiple instances of a single platform are installed, this problem does not occur.

Symptoms
When you run an application that uses Microsoft SQL Server 2005 service broker or Microsoft SQL Server 2008 service broker, an access violation occurs intermittently. Then, error messages that resemble the following arelogged in the SQL Server error log file:

<Date Time>,spid76,Unknown,Service Broker needs to access the master key in the database ‘<Database Name>’. Error code:25. The master key has to exist and the service master key encryption is required.
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,* Access Violation occurred reading address 0000000000000000
<Date Time>,spid22s,Unknown,* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
<Date Time>,spid22s,Unknown,* Exception Address = 0000000002B8FA73 Module(sqlservr+0000000001B8FA73)
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,*
<Date Time> spid 22
<Date Time>,spid22s,Unknown,* BEGIN STACK DUMP:
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,* *******************************************************************************
<Date Time>,spid22s,Unknown,SqlDumpExceptionHandler: Process 22 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION.
SQL Server is terminating this process.
<Date Time>,spid22s,Unknown,***Stack Dump being sent to C:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
<Date Time>,spid22s,Unknown,An error occurred in the Service Broker internal activator while trying to scan the user queue ‘<User Queue>’ for its status. Error: 2905<c/> State: 2.These error messages describe the following sequence of events. An error occurs when SQL Server 2005 or SQL Server 2008 accesses the master key. This error causes the access violation. Additionally, other errors occur when SQL Server 2005 or SQL Server 2008 tries to scan the user queue.
Note A mini-dump file is generated in the SQL Server logfolder.
Resolution
This problem occurs because of a race condition between the alter operation for a queue whose status is “on” and the drop operation for the same queue. If the drop operation succeeds, the access violation occurs. Additionally, the queue cannot be scanned successfully aspart of the alter operation.

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

Symptoms
This article describes the following about this hotfix release: The issues that are fixed by this hotfix package.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.The files that are contained in the hotfix package.
Resolution
When you open a database in Microsoft SQL Server 2000, you notice that a user database is marked as suspect. Also, an error message that is similar to the following is logged in the SQL Server 2000 error log:

<Date> <Time> spid9 Recovery of database ‘UserDatabaseName’ (5) is 2% complete (approximately 185 more seconds) (Phase 3 of 3).
<Date> <Time> spid9 Using ‘dbghelp.dll’ version ‘4.0.5′ *Dump thread – spid = 9, PSS = 0×80178098, EC = 0×801783c0
<Date> <Time> spid9 The exception information has been submitted to Watson error reporting.
<Date> <Time> spid9 Stack Signature for the dump is 0×986D5509
<Date> <Time> spid9 SQL Server Assertion: File: <page.cpp>, line=3430 Failed Assertion = ‘m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed’.
<Date> <Time> spid9 Location: page.cpp:3430 Expression: m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed

Symptoms
You put the Microsoft SQL Server 2008 setup binary files in a folder whose path is in the 8.3 compatible format. When you start the Setup program, an exception may occur and the Setup program fails during the LoadExtensions action. Additionally, thefollowing error message is logged in the Detail_GlobalRules.txt file in the setup log folder:

<Date><Time> Slp:Message:
<Date><Time> Slp:Object of type ‘Microsoft.SQL.Chainer.Package.PropertiesTypeProperty’ cannot be converted to type ‘Microsoft.SQL.Chainer.Package.PropertiesTypeProperty’.
<Date><Time> Slp:Stack:
<Date><Time> Slp:at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr)
<Date><Time> Slp:at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
<Date><Time> Slp:at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
<Date><Time> Slp:at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
<Date><Time> Slp:at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionDatastoreIntegration.SetPropertiesOnRunningAction(ActionKey key, TextWriter loggingStream)
<Date><Time> Slp:at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
<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)
Note The 8.3 compatible format refers to the 8 characters that are used for the file name, and the 3 characters that are used for the file name extension. This format is used for MS-DOS. For example, the file name “ABCDEFGHIJK” in the 8.3 compatible format is “ABCDEF~1.”
Resolution
When SQL Server 2008 uses the Assembly.LoadFrom() function to load file name extensions, the 8.3 compatible path cannot match the real path, and this causes the exception that is described in the “Symptoms” section.