Ms sql error 20476

Исправление: При использовании связанного сервера, созданное поставщик собственного клиента SQL в SQL Server 2008 возникает несколько проблем

Корпорация Майкрософт распространяет исправления Microsoft SQL Server 2008 как один загружаемый файл. Так как исправления являются накопительными, каждый выпуск содержит все исправления и все исправления безопасности, которые были включены в предыдущие 2008 SQL Server исправления выпуска.

Симптомы

На компьютере, на котором выполняется Microsoft SQL Server 2008 возникают одно или несколько из следующих проблем при создании связанного сервера с помощью поставщика собственного клиента SQL (Sqlncli.dll).

Примечание. Эти проблемы также возникают в Пакет обновления 3 (SP3) для Microsoft SQL Server 2005. Однако исправление, описанное в данной статье неприменимы к SQL Server 2005 с пакетом обновления 3.

Проблема 1

Рассмотрим следующий сценарий:

В среде SQL Server Management Studio откройте окно новый связанный сервер и создать связанный сервер, используя один из следующих вариантов настройки:

Поставщик собственного клиента SQL с Тип сервера SQL Server

Поставщик собственного клиента SQL (не SQL собственного клиента 10) Тип сервера , что другие источники данных

Поставщик Microsoft OLE DB для SQL Server Тип сервера , что другие источники данных

Разверните каталог Связанных серверов в среде SQL Server Management Studio для просмотра связанных серверов.

В этом случае неожиданного завершения работы службы SQL Server или мини-дамп повторно создается в папке журнала ошибок SQL Server. Такая ситуация будет повторяться до остановки службы SQL Server. Кроме того среда SQL Server Management Studio выводит следующее сообщение об ошибке:

Название: Microsoft SQL Server Management Studio
——————————
Не удается получить данные для этого запроса. (Microsoft.SqlServer.Management.Sdk.Sfc)

Для получения справки, щелкните: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
——————————
ДОПОЛНИТЕЛЬНЫЕ СВЕДЕНИЯ:
Возникло исключение во время выполнения инструкции Transact-SQL или пакета. (Microsoft.SqlServer.ConnectionInfo)
——————————

Истекло время ожидания. Время ожидания истекло до завершения операции или сервер не отвечает. (Microsoft SQL Server, ошибка: -2)

Примечание. Эта проблема не возникает при выполнении запроса к связанному серверу при использовании поставщика собственного клиента SQL в SQL Server Тип сервера .

Проблема 2

Рассмотрим следующий сценарий:

Создание связанного сервера с помощью поставщика Microsoft OLE DB для драйверов ODBC.

Источник данных ODBC создается с помощью поставщик собственного клиента SQL Server типа в другом источнике данных.

В этом случае связанный сервер не возвращает результатов.

Решение

Исправление этой уязвимости первого выпуска накопительного обновления 7 для SQL Server 2008 Пакет обновления 1. Дополнительные сведения о этот накопительный пакет обновления щелкните следующий номер статьи базы знаний Майкрософт:-

979065 Накопительный пакет обновления 7 для SQL Server 2008 Пакет обновления 1
Примечание. Поскольку построения являются накопительными, каждый новый выпуск исправление содержит все исправления и все исправления, входившие в состав предыдущих SQL Server 2008 выпуска исправлений. Мы рекомендуем рассмотреть применение последнего выпуска исправления, содержащего это исправление. Для получения дополнительных сведений щелкните следующий номер статьи базы знаний Майкрософт:-

970365 SQL Server 2008 выполняет построение, выпущенных после выпуска SQL Server 2008 Пакет обновления 1
Исправления Microsoft SQL Server 2008 создаются для определенных пакетов обновления SQL Server. Необходимо установить исправление SQL Server 2008 Пакет обновления 1 для установки SQL Server 2008 Пакет обновления 1. По умолчанию какие-либо исправления, включенный в пакет обновления SQL Server включено в следующий пакет обновления SQL Server.

Дополнительные сведения

Можно подтвердить версии файлов Sqlncli.dll и Sqlservr.exe, выполняется следующий запрос:

Если Пакет обновления 1 (SP1) для SQL Server 2008 или более поздней версии Microsoft SQL Server 2008, запрос будет возвращать следующей информацией:

Файл Sqlncli.dll будет иметь свою версию позже, чем 9.0:3207.0.

Файл Sqlservr.exe будет иметь свою версию позже или равно 10.0:2531.0, но ранее чем 10.0:2766.0.

При использовании Microsoft SQL Server 2008 RTM-версии или более поздней версии SQL Server 2008 RTM, запрос будет возвращать следующей информацией:

Файл Sqlncli.dll будет иметь свою версию более поздней, чем версия 9.0:3207.0.

Файл Sqlservr.exe будет иметь свою версию позже или равно 10.0:1600.0, но ранее чем 10.0:1835.0.

Временное решение

Чтобы обойти эти проблемы, выполните следующие действия.

1. Удалите связанный сервер при сбое.

2. Создание нового связанного сервера с помощью поставщика 10.0 собственного клиента SQL Server (SQLNCLI10). Чтобы сделать.
а. Щелкните правой кнопкой мыши Связанные серверы и выберите Связанный сервер.
б. выберите другой источник данных и выберите 10.0 собственного клиента SQL Server для поставщика.

Создайте раздел реестра с именем «SQLNCLI» по следующему адресу:

Создайте запись реестра типа REG_DWORD, с именем «SQLOSPartitioning» в него.

Значение этой записи значение 0x0.

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Дополнительные сведения

Версии продуктов, для которых вычисляется правило

Советник по System Center

Чтобы предотвратить повреждение памяти собственный клиент SQL SQL Server отсутствует обновление KB979779

На этом сервере присутствует поставщик собственного клиента SQL, который соответствует SQL Server 2005. Эта старая версия SQLNCLI.dll может быть потенциально загружен в SQL Server 2008 и SQL Server 2008 R2, при перечислении поставщиков и создания связанных серверов. Определенные сборки SQL Server 2008 и SQL Server 2008 R2 могут возникнуть проблемы и зависает при создании или использовании связанному серверу, созданному с помощью уязвимых SQLNCLI.dll. Обновление соответствующих экземпляров SQL Server 2008 и SQL Server 2008 R2 с необходимые исправления или избегать использования этой SQLNCLI.dll при создании связанных серверов.

SQL Server 2008

SQL Server 2008 R2

Ссылки

Дополнительные сведения о добавочных модель обслуживания для SQL Server щелкните следующий номер статьи базы знаний Майкрософт:

935897 добавочных модель обслуживания доступна из группы SQL Server для предоставления исправления для проблем, о которых сообщалось в

Дополнительные сведения о схеме именования для обновления SQL Server щелкните следующий номер статьи базы знаний Майкрософт:

822499 Новая схема присвоения имен пакетам обновлений программного обеспечения Microsoft SQL Server

Для получения дополнительных сведений о терминологии обновлений программного обеспечения щелкните следующий номер статьи базы знаний Майкрософт:

Описание 824684 Стандартные термины, используемые при описании обновлений программных продуктов Майкрософт

Источник

Error 20476 sql server 2008

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I am trying to install Service Pack 1 to a SQL Server 2008 R2 but the installation fails with following error message:

SQL Server Setup has encountered the following error:

A failure was detected for a previous installation, patch, or repair for instance ‘MSSQLSERVER’ during configuration for features [SQL_Replication_Core_Inst,SQL_Engine_Core_Inst,MPT_AGENT_CORE_CNI,SQL_FullText_Adv,]. In order to apply this patch package (KB2528583), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.

Error code 0x84B20001.

I found following discussion: http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/95e92910-156e-4da9-91f7-5a5e1512050d and tried run ‘Repair’ from SQL Server Installation Center -> Maintenance. However the repair completed with an error message: «Login failed for user ‘DOMAINuser’.» The user account I am using when trying to run this, is as a member of Domain Admins group and of course in local Administrators of this particular server.

Any ideas how to solve the issue with the ‘Repair’ and how to get SP1 installed on the SQL Server 2008 R2?

Источник

Error 20476 sql server 2008

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

upgrading from 2008 r2 eval to 2008 r2 enterprise.

Use the maintenance option from setup. Get pretty far along in the process. But then the following error. ( an additional note. setup warns that I am running sql server on a domain controller server. )

The link the error message points to has nothing to say. Why would my sql server upgrade fail? If I have to reinstall, will I lose my database data?

TITLE: Microsoft SQL Server 2008 R2 Setup
——————————

The following error has occurred:

Access to the path ‘C:Program FilesMicrosoft SQL Server100License TermsSQLServer2008R2_License_ENT_1033.rtf’ is denied.

Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.

Answers

Please give full control access on the “C:program filesMicrosoft SQL” folder and subfolders to the Windows Account you are using to run SQL Server setup. Verify that even if you are logged in as an Administrator.

Hope this helps.

Please verify the Windows account you are using to run SQL Server setup has full control access to “c:program filesMicrosoft SQL Server” directory, even when that Windows account is an administrator.

Use the Run as Administrator option to run SQL Server setup also.

more info on this. Do the edition upgrade process with a sql server 2008 R2 standard edition version. The upgrade completes. Get a message «your sql edition upgrade is complete. But, attempting to use MS sql server mgmt studio, get the same «eval period has expired» error.

Here are the steps from the install:
— maintenance, edition upgrade
— setup support rules — passed
— warning: computer domain is controller
— product key — burned in
— license terms
— specify instance : MSSQLSERVER
— edition upgrade rule. passed 5.
— click upgrade button
— your sql edition upgrade is complete
— close

Happy you upgraded your SQL instance.

The issue with SQL Server Management Studio is a known issue. Please see the following article by Jonathan Kehayias:

Hope this helps.

ran as administrator ( the title of the window says: «Administrator: Command prompt» ). same error:

D:>d:Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=MSSQLSERVER /IACCEPTSQL
SERVERLICENSETERMS
Microsoft (R) SQL Server 2008 R2 Setup 10.50.1600.01
Copyright (c) Microsoft Corporation. All rights reserved.

The following error occurred:
Access to the path ‘C:Program FilesMicrosoft SQL Server100License TermsSQLSc:
erver2008R2_License_STD_1033.rtf’ is denied.

Error result: -2068119551
Result facility code: 1211
Result error code: 1

Please review the summary.txt log for further details

here is the summary.txt log file:

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: Access to the path ‘C:Program FilesMicrosoft SQL Server100License TermsSQLServer2008R2_License_STD_1033.rtf’ is denied.
Start time: 2010-06-23 12:40:10
End time: 2010-06-23 12:41:28
Requested action: EditionUpgrade
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20100623_123902Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x60797DC7%400xBB814387

Machine Properties:
Machine name: ANTEC
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Management Tools — Basic 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Management Tools — Complete 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools Connectivity 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools Backwards Compatibility 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools SDK 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Integration Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No

Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: d:x64setup
Installation edition: STANDARD

User Input Settings:
ACTION: EditionUpgrade
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20100623_123902ConfigurationFile.ini
ENU: True
FARMACCOUNT:
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: OCS,CE_RUNTIME
HELP: False
IACCEPTSQLSERVERLICENSETERMS: True
INDICATEPROGRESS: False
INSTANCENAME: MSSQLSERVER
PASSPHRASE: *****
PID: *****
QUIET: True
QUIETSIMPLE: False
UIMODE: Normal
X86: False

Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20100623_123902ConfigurationFile.ini

Detailed results:
Feature: SQL Compact Edition Runtime
Status: Skipped
MSI status: Passed
Configuration status: Passed

Feature: Microsoft Sync Framework
Status: Skipped
MSI status: Passed
Configuration status: Passed

Rules with failures:

There are no scenario-specific rules.

Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20100623_123902SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Источник

I could not find answer to the problem I am facing.

Here is the snapshot of the issue

2011-05-13 15:16:44 SQLEngine: —SqlEngineDBStartConfig: ConfigRC : SqlEngineDBStartConfig Configuration
2011-05-13 15:16:44 Slp: Sco: Attempting to set directory full path
2011-05-13 15:16:44 Slp: Sco: Attempting to normalize directory path C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLDATA
2011-05-13 15:16:44 Slp: Sco: Attempting to set directory full path
2011-05-13 15:16:44 Slp: Sco: Attempting to normalize directory path C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLDATA
2011-05-13 15:16:44 Slp: Sco: Attempting to set directory full path
2011-05-13 15:16:44 Slp: Sco: Attempting to normalize directory path C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLDATA
2011-05-13 15:16:44 SQLEngine: : Appending Service Account NT AUTHORITYSYSTEM to list of sysadmins.
2011-05-13 15:16:44 Slp: Sco: Attempting to get local system account name
2011-05-13 15:16:44 Slp: Sco: Attempting to get NT account from sid S-1-5-18
2011-05-13 15:16:44 Slp: Sco: Attempting to get account from sid S-1-5-18
2011-05-13 15:16:44 Slp: Sco: Attempting to get account sid for user account NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: Attempting to get sid for user account NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITYSYSTEM parameter to NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: Attempting to get local system account name
2011-05-13 15:16:44 Slp: Sco: Attempting to get NT account from sid S-1-5-18
2011-05-13 15:16:44 Slp: Sco: Attempting to get account from sid S-1-5-18
2011-05-13 15:16:44 Slp: Sco: Attempting to get account sid for user account NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: Attempting to get sid for user account NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITYSYSTEM parameter to NT AUTHORITYSYSTEM
2011-05-13 15:16:44 Slp: Sco: Attempting to get account sid for user account ITLINFOSYSPraveen_Devathi
2011-05-13 15:16:44 Slp: Sco: Attempting to get sid for user account ITLINFOSYSPraveen_Devathi
2011-05-13 15:16:44 Slp: Sco: GetSidForAccount normalized accountName ITLINFOSYSPraveen_Devathi parameter to ITLINFOSYSPraveen_Devathi
2011-05-13 15:16:44 SQLEngine: : Checking Engine checkpoint ‘StartEngineService’
2011-05-13 15:16:44 SQLEngine: —SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -f -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -dC:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLTemplate Datamaster.mdf -lC:Program
FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLTemplate Datamastlog.ldf)…

2011-05-13 15:16:44 Slp: Sco: Attempting to start service MSSQL$SQLEXPRESS
2011-05-13 15:16:44 Slp: Sco: Attempting to open SC Manager
2011-05-13 15:16:44 Slp: Sco: Attempting to open service handle for service MSSQL$SQLEXPRESS
2011-05-13 15:16:46 Slp: Sco: Service MSSQL$SQLEXPRESS started
2011-05-13 15:16:46 Slp: Sco: Attempting to close service handle for service MSSQL$SQLEXPRESS
2011-05-13 15:16:46 Slp: Sco: Attempting to close SC Manager
2011-05-13 15:16:46 Slp: Sco: Attempting to get service process id for service MSSQL$SQLEXPRESS
2011-05-13 15:16:46 Slp: Sco: Attempting to open SC Manager
2011-05-13 15:16:46 Slp: Sco: Attempting to open service handle for service MSSQL$SQLEXPRESS
2011-05-13 15:16:46 Slp: Invoking QueryServiceStatusEx Win32 API
2011-05-13 15:16:46 Slp: Sco: Attempting to close service handle for service MSSQL$SQLEXPRESS
2011-05-13 15:16:46 Slp: Sco: Attempting to close SC Manager
2011-05-13 15:16:46 Slp: Sco: Returning service process id 13072
2011-05-13 15:16:46 SQLEngine: : Checking Engine checkpoint ‘GetSqlServerProcessHandle’
2011-05-13 15:16:46 SQLEngine: —SqlServerServiceSCM: Waiting for nt event ‘GlobalsqlserverRecComplete$SQLEXPRESS’ to be created
2011-05-13 15:16:46 SQLEngine: —SqlServerServiceSCM: Waiting for nt event ‘GlobalsqlserverRecComplete$SQLEXPRESS’ or sql process handle to be signaled
2011-05-13 15:16:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2011-05-13 15:16:46 Slp: Access is denied
2011-05-13 15:16:46 Slp: The configuration failure category of current exception is ConfigurationFailure
2011-05-13 15:16:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2011-05-13 15:16:46 Slp: System.ComponentModel.Win32Exception: Access is denied
2011-05-13 15:16:46 Slp:    at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
2011-05-13 15:16:46 Slp:    at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
2011-05-13 15:16:46 Slp:    at System.Diagnostics.Process.OpenProcessHandle()
2011-05-13 15:16:46 Slp:    at System.Diagnostics.Process.get_Handle()
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerStartup.StartSQLServerForInstall(String sqlCollation, String masterFullPath, Boolean isConfiguringTemplateDBs, Boolean isSlipstreamRunning)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary`2 actionData, PublicConfigurationBase
spcbCurrent)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2011-05-13 15:16:46 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2011-05-13 15:16:46 Slp: Exception: System.ComponentModel.Win32Exception.
2011-05-13 15:16:46 Slp: Source: System.
2011-05-13 15:16:46 Slp: Message: Access is denied.
2011-05-13 15:16:47 Slp: Watson Bucket 1
 Original Parameter Values

2011-05-13 15:16:47 Slp: Parameter 0 : SQL Server 2008
R2@RTM@

2011-05-13 15:16:47 Slp: Parameter 1 : System.Diagnostics.ProcessManager.OpenProcess

2011-05-13 15:16:47 Slp: Parameter 2 : System.Diagnostics.ProcessManager.OpenProcess

2011-05-13 15:16:47 Slp: Parameter 3 :
System.ComponentModel.Win32Exception@-2147467259

2011-05-13 15:16:47 Slp: Parameter 4 :
System.ComponentModel.Win32Exception@-2147467259

2011-05-13 15:16:47 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc

2011-05-13 15:16:47 Slp: Parameter 6 :
INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST

2011-05-13 15:16:47 Slp:
 Final Parameter Values

2011-05-13 15:16:47 Slp: Parameter 0 : SQL Server 2008
R2@RTM@

2011-05-13 15:16:47 Slp: Parameter 1 : 0x0CE75128

2011-05-13 15:16:47 Slp: Parameter 2 : 0x0CE75128

2011-05-13 15:16:47 Slp: Parameter 3 : 0xC24842DB

2011-05-13 15:16:47 Slp: Parameter 4 : 0xC24842DB

2011-05-13 15:16:47 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc

2011-05-13 15:16:47 Slp: Parameter 6 : 0x9396DE01

2011-05-13 15:16:47 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110513_150950Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2011-05-13 15:16:48 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftWindowsCurrentVersionUninstall to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110513_150950Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2011-05-13 15:16:48 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110513_150950Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2011-05-13 15:16:52 Slp: Access is denied
2011-05-13 15:16:53 Slp: Watson bucket for exception based failure has been created

Let me know if any further information is needed.

Regards,

Praveen

If you try doing the out of the box install for SQL Express 2014, SQL Express 2012 (or for that matter SQL Server 2012 or SQL Server 2014) and just want to set up a simple development PC then you will probably get the same error I did:

… “Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.”

(for the impatient, skip down a page or two for the fix)

SQL Express 2012, SQL Express 2012 SP1, SQL Enterprise 2012, SQL Express 2014 or SQL Enterprise 2014 will all generate this same message:

Once you click OK, installation proceeds to the end and shows (in my case) what actually did not install correctly, along with links to the error log:

the error logs aren’t a lot of help, typically you get something like this:

Configuration file:            C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20140402_153752ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

Rules with failures:

attempt at repair didn’t entirely work, though at least a few more features appeared ok afterwards, seems the features that failed weren’t really installed to begin with.

  Configuration file:            C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20140402_164618ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84B40002
  Error description:             The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84B40002
  Error description:             The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Some people suggesting changing security on %userprofile%AppDataMicrosoftRoamingMicrosoftProtect folder, but the user accounts are generated during install, so the logical thing (well it worked for me) was to simply re-use LOCAL SERVICE and NETWORK SERVICE accounts instead.

Caveat: this is a development machine, not production, I’m a developer not a DBA – this is convenient and expedient for me.

THE FIX

Short version: the fix for SQL 2012 or SQL 2014 installs is the same, just manually set the security for “SQL Server Agent” and “SQL Server Database Engine” to “NETWORK SERVICE”,
and for “SQL Server Analysis Services”, “SQL Server Reporting Services”, and if used for “SQL Server Distributed Replay Client” and “SQL Server Distributed Replay Controller” all to “LOCAL SERVICE”

Long version, below:

Here’s the complete install procedure end to end for the demo of SQL Server 2012 Enterprise, however the procedure is much the same for 2014 or SQL Express as well.

Launch the installation by running setup.exe, click on “Installation”

Once you click on Installation, click on “New SQL Server stand-alone installation or add features to an existing installation”

After the checks are completed, click OK

choose your version, click Next

Click at least “I accept the license terms” (once you do), and optionally click “Send feature usage..” then click Next

Doesn’t hurt to leave the checkbox on, allow installer to add the updates now. BTW This will vary depending on your install of SQL 2012 or 2014. Click Next.

If all is well, you should see something similar to this. If there are issues, correct them, as advised, and come back here.

(For me Firewall was not a problem as this was a standalone dev. machine and not for other’s consumption.) Click Next

Leave the choice here on “SQL Server Feature Installation” to allow you to change the settings. Click Next

Choose your options. Note that you may see different features in SQL 2012 vs SQL 2014. Click Next when your options have been selected.

not too long to wait …

After further checks, click Next

Create a unique name. If you have just one SQL instance you could call it say SQLSERVER or SQLEXPRESS. IMO good to plan ahead, as you might find it useful to install a different version of SQL server to allow you to do development of server to server / ETL queries etc. Click NEXT when completed.

another intermediate check, this time for space, just click Next.

This is where you need to change from the default user accounts (most of which do not exist yet).

Choose one of the account names, scroll down and select “<<Browse…>>”

When you click browse, the account selection window pops up, click Advanced.

Click Find Now, then choose NETWORK SERVICE (or LOCAL SERVICE) depending on the service you are configuring. Click OK

You will be returned to the original popup, check the account selected, then click OK

Repeat until you change these accounts to either NETWORK SERVICE or LOCAL SERVICE, as shown, then click Next.

I usually select Mixed Mode, as it (a) gives me a back door in case something goes wrong, and (b) to be able to develop apps using name/password as opposed to using window authentication.

If using Mixed Mode, enter a password (twice)

Either way, make sure you click “Add Current User”, and you will find your local user account is added as a SQL Server Administrator.

If you want to experiment with Filestream development, make sure you select the “FILESTREAM” tab, and select these options.

Make sure while there you add a sharename, as shown. This can be set to correspond with your SQL instance name.

Once completed, click Next

Click “Add Current User”, then click Next

Click Next

Click “Add Current User”, then click Next

Add your local machine name, then click Next.

Optional checkbox, click Next

Another pre-install check, wait a bit, click Next

A summary of what will be installed, click Next

Time for coffee .. waiting ..

The end of install, almost .. if you are lucky you might need to reboot (don’t worry though, the reboot is not forced).

Click OK

there’s a brief message, just wait.

Finally you can click Close.

You are not forced to reboot, but now is the time (if you were prompted that you needed to), to reboot.

#four, #one, #three, #two