SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘Microsoft’

The installation fails when you try to install a new instance of SQL Server 2008 on an x64-based computer

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.

The Full-Text Search component is not completely rolled back to the Service Pack 1 version after you uninstall Cumulative Update 3 for SQL Server 2008 Service Pack 1 that is applied by using a sl …

Symptoms
Consider the following scenario:On a Microsoft Windows-based computer, you apply Cumulative Update 3 for SQL Server 2008 Service Pack 1 by using a slipstream installation.For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491?(http://support.microsoft.com/kb/971491/) Cumulative update package 3 for SQL Server 2008 Service Pack 1You tryto uninstall this cumulative update after the slipstream installation.In this scenario, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
To confirm whether you are encountering this issue, you can check the SQL Server Full-Text Key file (Sql_fulltext_keyfile.dll) in theSQL Server 2008 Installation folder. Typically, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10.<Instance Name>\MSSQLIf this file has a file version that is greater than 10.00.2531.00, the Full-Text Search component is not completely rolled back to the SQL Server 2008 Service Pack 1 version.
Resolution
To work around this problem, follow these steps: In Control Panel, open Add or Remove Programs.
Note For Windows Vista or for Windows Server 2008, open Programs and Features.In the Currently installed programs list, click Microsoft SQL Server 2008, and then click Change/Remove.
Note For Windows Vista or Windows Server 2008, right-click Microsoft SQL Server 2008, and then click Change.In the SQL Server 2008 dialog box, click Remove.Select the appropriate instance or instances, and then click Next.In the Select Features window, select Full-Text Search from the Features list.Complete the Remove SQL Server 2008 wizard, as appropriate for your configuration.Click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Installation Center.Click Installation, and then click New SQL Server stand-alone installation or add features to an existing installation.In the Browse For Folder dialog box, locate the SQL Server 2008 installationfolder that you want, and then click OK.In the SQL Server 2008 Setup window,click Next to move to the Installation Type phase.Click Add Features to an existing instance of SQL Server 2008, select the appropriate instance in the drop-down list, and then click Next to move to the Feature Selection phase.Select Full-Text Search from the Features list.Follow the steps in the Full-Text Search installation wizard.Note There is no workaround for cluster scenarios. To roll back the cumulative update, you must reinstall the clustered instance of SQL Server.

The DBCC CHECKDB statement does not raise exceptions in SQL Server when the DBCC CHECKDB statement detect a consistency error in the database

Symptoms
In Microsoft SQL Server, you use a TRY…CATCH construct to process exceptions that are raised from the DBCC CHECKDB statement. However, when the DBCC CHECKDB statement detects a consistency error in the database, the CATCH block is not triggered.
Note This behavior also occurs in SQL Server 2008.
Resolution
This behavior occurs because the DBCC CHECKDB statement does not raise an exception when the DBCC CHECKDB statement detects a consistency error inside the database.

The Databases folder may take longer than expected to open when you expand the folder in Object Explorer in SQL Server 2008 Management Studio

Symptoms
When you expand the Databases folder in Object Explorer in Microsoft SQL Server 2008 Management Studio, the Databases folder may take longer than expected to open. For example, the Databases folder may take several minutes to open.
Note This issue occurs only for instances of Microsoft SQL Server 2008 that have a large history of backups.
Resolution
This issue occurs because of a sub-optimal query that SQL Server 2008 Management Studio runs. This query is run when one of the following columns is enabled in the Object Explorer Details window for the Databases folder:Last Backup DateLast Log Backup Date

The ActiveX Script task in an Integration Services package does not run after you uninstall SQL Server 2005 from a computer that has SQL Server 2008 installed

Symptoms
After you uninstall Microsoft SQL Server 2005 from a computer that has Microsoft SQL Server 2008 installed, the Microsoft ActiveX Script task in a SQL Server Integration Services package does not run.Additionally, when you try to add an ActiveX Script Task to a new package in BIDS, the task will show a validation error pointing ScriptHost can’t be instantiated.
Resolution
This problem occurs because the Axscphst.dllfile is deleted or is unregistered after you uninstall SQL Server 2005. The Axscphst.dllfile is in the following location:
%SystemRoot0%\Program Files\Microsoft SQL Server\100\COMNote SQL Server 2005 and SQL Server 2008 use the Axscphst.dll file.

SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

Symptoms
SummaryMore informationPrerequisitesHow to identify your SQL Server service pack and version SQL Server 2000 baseline buildsHotfix update information
Resolution
This article contains a list of the Microsoft SQL Server 2000 hotfixes. You can use this list to determine which hotfixes are included in a specific hotfix build. Unless otherwise specified, all the hotfixes in prior builds will be included in later builds. The list includes all the public hotfixes that have been released since the release of Microsoft SQL Server 2000 Service Pack 3 and Microsoft SQL Server 2000 Service Pack 3a.
Here are some important notes regarding the Microsoft SQL Server 2000 hotfixes. For all the hotfixes, you must have SQL Server 2000 Service Pack 3 or SQL Server 2000 Service Pack 3a installed.For hotfixes earlier than build 8.00.0818, we recommend that you apply build 8.00.0818 instead. Build 8.00.0818 contains security fixes that are documented in Microsoft Security Bulletin MS03-031. For download locations and additional information about the security vulnerability addressed in MS03-031, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/bulletin/MS03-031.mspx(http://www.microsoft.com/technet/security/bulletin/MS03-031.mspx)Hotfixes that are not part of a security release can only be obtained by contacting Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone phone numbers and for information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. To install any hotfix later than build 8.00.0977, you must first install the 8.00.0977 “baseline” build. For more information about “baseline” builds, see the “SQL Server 2000 baseline builds” section. This list does not contain the fixes for Microsoft Data Access Components (MDAC) or forMicrosoft SQL Server 2000 Analysis Services.