Не найден дескриптор запуска ядра субд код ошибки 0x851a0019

Столкнулся с интересной ошибкой при установке MS SQL Server 2014 на новом сервере Windows Server 2012 R2. Установка SQL Server прерывается почти в самом конце с ошибкой «Не найден дескриптор запуска компонента Database Engine» (Could not find the Database Engine startup handle).

В логе установки Summary.txt при этом присутствует ошибка:

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: Could not find the Database Engine startup handle.

Данная ошибка установки MS SQL Server связана с тем, что используются стандартные настройки установки, при котором служба SQL Server запускается под непривилегированной учетной записью NT ServiceMSSQL$V2014. У данной учетной записи может быть недостаточно полномочий для запуска службы SQL Server, поэтому запустить службу невозможно, и установщик завершается с ошибкой «Could not find the Database Engine startup handle». Также эта ошибка может указывать на то, что ранее на компьютере уже пытались установить SQL Server и не очистили файлы и службы, оставшиеся от предыдущей установки.

Чтобы исправить ошибку установки SQL Server:

Корректно деинсталлируйте все программы, связанные с SQL Server через Панель управления и перезагрузите сервер (проверьте, что не осталось файлов и папок в каталоге C:Program FilesMicrosoft SQL ServerMSSQL12.xxx);
Запустите чистую установку из дистрибутива SQL Server. На вкладке «Server Configuration» убедитесь, что служба SQL Server Database Engine запускается под учетной записью NT ServiceMSSQLSERVER;
Измените эту учетную запись на NT AUTHORITYSYSTEM;
Продолжите установку SQL Server. Ошибка больше не должна появляться.

После окончания установки настоятельно рекомендуем изменить учетную запись, под которой запускается служба SQL Server Database Engine на непривилегированную учетную запись. Эта учетная запись не обязательно должна обладать правами локального администратора сервера (вполне достаточно полномочий внутри SQL Server). Можно использовать аккаунты с правами sysadmin — NT ServiceMSSQLSERVICE или NT ServiceSQLSERVERAGENT. Чтобы изменить учетную запись, под которой работает SQL Server:

Запустите SQL Server Configuration Manager и перейдите в раздел SQL Server Services;
Щелкните по SQL Server (MSSQLSERVER), нажмите кнопку Browse и в поле This account укажите учетную запись, под которой нужно запускать службу или используйте управляемую учетную запись — gMSA (Group Managed Service Accounts). Укажите пароль пользователя и сохраните изменения;
Перезапустите службы SQL Server.

Этот способ поможет вам исправить ошибку «Не найден дескриптор запуска компонента Database Engine» при установке любых версий SQL Server (2016, 2014, 2012 или 2008).

Источник

Introduction
Problem Definition
Cause
Solution
- Uninstall
- Fresh install
Looking at SQL Server Errorlog
Forum threads related to this issue
Suggested Readings
See Also

Introduction

This article is about how to proceed when you get error message ‘Could not find database engine startup handle ‘ while installing SQL Server 2008 R2/2012 or 2014.

↑ Back to top

Problem Definition

If you are an active member of
SQL Server Setup and Upgrade forum you must have noticed some users creating a thread with error messages of ‘Could not find database engine startup handle ‘
while installing SQL Server . This article tries to provide a simple solution to this problem, that many users face during installation of SQL Server 2008 R2, SQL Server 2012 and SQL Server 2014 as well.

Let’s get started. For resources on installing SQL Server 2008/R2/2012/2014; there are lot of good articles which you find in Suggested Readings section .

Its common belief that installation of SQL Server is very easy, just do *Next, Next * and installation would be complete.

It is correct, it’s simple but internally what all operations go a general user is not aware about it and when he faces issue he feels that SQL Server product is not good ( this is my forum experience where many of Original Poster (OP) get frustrated with
SQL Server installation error). It’s recommend to read below Microsoft articles before proceeding with installation of SQL Server

Hardware and Software requirement for installing SQL Server
Install SQL Server from installation wizard
How to use SQL Server in win 8 and Windows Server environment

Problem is when a user tries to install SQL Server 2012 or 2014 or 2008 R2 during installation error is flashed which says

Could not find database engine startup handle and some Hex error like ‘0x851a0019’ error could also be ‘Wait on the Database Engine recovery handle failed’.

↑ Back to top

Cause

Following can be the reason behind the error message.

The account which user selected on Server Configuration page window ( during installation) is somehow not able to bring SQL Server database engine services online. Either is lacks privilege or it is corrupted. During installation of database engine services
SQL Server tries to bring online database services as a internal process but due to startup account either corrupt or not having appropriate privileges it fails to do so and ultimately installation fails.
Other reason is when installation fails first time due to some reason and user uninstall failed installation from add remove program, the un-installation leaves account in broken state so any further attempt to install flashes this error message.
The reason can be also that SQL Server installation was successful in installing SQL Server and its services but due to some other limitation in system or other system related errors SQL Server is not able to come online. The same has been discussed in
section ‘Looking at SQL Server errorlog’

↑ Back to top

Solution

A simple solution to above problem is below.

Uninstall

Uninstall SQL Server completely from add remove program. Make sure no previous failed installation fragments are present on your system. Please use this
link for uninstalling existing instance of SQL Server. If you have SQL Server 2005
use this link.

—Below Steps should ONLY be followed if removing SQL Server is giving error and if you have used all means to remove SQL Server and you have failed. If you have doubts about the approach please DONT follow it.

If you are unable to uninstall SQL Server completely because you deleted SQL Server files and un-installation is giving error please follow below method. This method is tested and suggested on

this thread and
Forum.

Below Solution (about removing reg keys) will work correctly for SQL Server having Just one instance.
If you have multiple instances and you have messed up SQL Server installation please contact Microsoft Support personal to get better guidance on removal of SQL Server. Please DONT use this method if you are new to SQL Server take help of experienced
DBA to locate proper registry keys and remove them if you are not confident at all it would be better calling Microsoft Support.

Note: Removing necessary registry entries might cause SQL Server instance to crash so backup registry before doing changes.

1. Uninstall the existing SQL Server and all the components from the add remove program.
2.
Backup the registry.
3. Delete the following keys using regedit:
- —HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
- —HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServer
4. Go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer.
7. Reboot the machine.

Fresh install

2. Start a fresh installation. Locate Setup.exe file in SQL Server installable. It would be something like below

Always Right click on Setup file and select Run As Administrator to launch the setup.

After launching the setup and providing necessary details you would reach to Server Configuration page as below. When you reach this page please select startup account for Database Engine services as NT AuthoritySYSTEM which is also called as Local System
account.

Next you need to proceed as normally you do for installation.You will see this will solve the issue.

After installation completes please change Service Account from NT AUTHORITYSYSTEM to a low privileged domain account. Please refer to below Microsoft link about how to configure various accounts for SQL Server and what minimum rights to provide

Configure Windows Service Account and Permissions

To get information about Local System account please refer to below link

Local System Account

Looking at SQL Server Errorlog

Even after following above method if you still get the error this means that problem is not with SQL Server installation something different is blocking SQL Server installation. The important point to note here with such error is you will see SQL Server
installed but the services are not online( there might be few exception). Please check SQL Server configuration manager and Services.msc to check whether SQL Server services are present or not. If they are present but in stopped state you must look at

log files present at location

Drive:Program FilesMicrosoft SQL ServerMSSQL.nMSSQLLOGERRORLOG and
ERRORLOG.n files.

Where Drive is system drive on which you installed SQL Server. It can be system drive C or any user drive (D,E,F…) . MSSQLn here means version number of SQL Server
n=10 for SQL Server 2008/2008 R2
n= 11 for SQL Server 20012
n=12 for SQL Server 2014.
One such thread with similar issue
is this , The problem was not the SQL Server, services were installed but SQL Server cannot start due to error

Cannot
use file ‘C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDB_NAMEmaster.mdf’ because it was originally formatted
with sector size 4096
and is now on a volume
with sector size

Now above error is not related to SQL Server but related to disk drive formatting on which SQL Server master data file resides. Error is beyond the scope of this article hence would not be discussed.

↑ Back to top

Forum threads related to this issue

This article is an outcome of my answer provided to below forum threads which faced issue ‘Could not find Database engine startup handle’. Please have a look

Could not find database engine startup handle Thread 1
Could Not find database engine startup handle thread 2
Database engine startup handle issue
Similar Thread

If you still cannot find solution to your problem please post your question on

SQL Server Setup and Upgrade forum for more assistance.

↑ Back to top

Ошибка установки SQL Server: Could not find the Database Engine startup handle

В логе установки Summary.txt при этом присутствует ошибка:

Feature: Database Engine Services

Чтобы исправить ошибку установки SQL Server:

Корректно деинсталлируйте все программы, связанные с SQL Server через Панель управления и перезагрузите сервер (проверьте, что не осталось файлов и папок в каталоге C:Program FilesMicrosoft SQL ServerMSSQL12.xxx);
Запустите чистую установку из дистрибутива SQL Server. На вкладке «Server Configuration» убедитесь, что служба SQL Server Database Engine запускается под учетной записью NT ServiceMSSQLSERVER;

Запустите SQL Server Configuration Manager и перейдите в раздел SQL Server Services;
Щелкните по SQL Server (MSSQLSERVER), нажмите кнопку Browse и в поле This account укажите учетную запись, под которой нужно запускать службу или используйте управляемую учетную запись — gMSA (Group Managed Service Accounts). Укажите пароль пользователя и сохраните изменения;
Перезапустите службы SQL Server.

Источник

0x851a0019 ошибка установки sql server

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

Asked by:

Question

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2017-11-02 10:33:21
End time: 2017-11-02 10:59:54
Requested action: Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for AdvancedAnalytics: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:
Machine name: RAJ-THINKPAD
Machine processor count: 4
OS version: Microsoft Windows 10 Pro (10.0.15063)
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 Configured

Package properties:
Description: Microsoft SQL Server 2016
ProductName: SQL Server 2016
Type: RTM
Version: 13
Installation location: C:SQLServer2016MediaExpressAdv_ENUx64setup
Installation edition: Express

Slipstream: True
SP Level 1

Product Update Status:
Success: KB 3182545

Product Updates Selected for Installation:
Title: Microsoft SQL Server 2016 Express Advanced SP1
Knowledge Based Article: KB 3182545
Version: 13.1.4001.0
Architecture: x64
Language: 1033

Update Source: Slipstream

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT:
ASSVCPASSWORD:
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS:
ASTELSVCACCT:
ASTELSVCPASSWORD:
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME:
CLTRESULTDIR:
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT:
CLTSVCPASSWORD:
CLTWORKINGDIR:
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT:
CTLRSVCPASSWORD:
CTLRUSERS:
ENABLERANU: true
ENU: true
EXTSVCACCOUNT: NT ServiceMSSQLLaunchpad$SQLEXPRESS
EXTSVCPASSWORD:
FEATURES: SQLENGINE, REPLICATION, ADVANCEDANALYTICS, FULLTEXT, RS, CONN, BC, SDK, BOL, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME:
FTSVCACCOUNT: NT ServiceMSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD:
HELP: false
IACCEPTROPENLICENSETERMS: true
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR:
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD:
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT:
ISTELSVCPASSWORD:
ISTELSVCSTARTUPTYPE: 0
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME:
MATRIXNAME:
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT:
PBDMSSVCPASSWORD:
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT:
PBENGSVCPASSWORD:
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE:
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT ServiceReportServer$SQLEXPRESS
RSSVCPASSWORD:
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR:
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SQLEXPRESS
SQLSVCINSTANTFILEINIT: true
SQLSVCPASSWORD:
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RAJ-THINKPADhuzefapc
SQLTELSVCACCT: NT ServiceSQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD:
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR:
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR:
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR:
SQLUSERDBLOGDIR:
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: Slipstream
USEMICROSOFTUPDATE: true
X86: false

Configuration file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20171102_103319ConfigurationFile.ini

Detailed results:
Feature: Client Tools Connectivity
Status: Passed

Feature: Client Tools SDK
Status: Passed

Feature: Client Tools Backwards Compatibility
Status: Passed

Feature: Reporting Services — Native
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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

Feature: Full-Text and Semantic Extractions for Search
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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

Feature: R Services (In-Database)
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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

Feature: SQL Browser
Status: Passed

Feature: Documentation Components
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: LocalDB
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Feature: Setup Support Files
Status: Passed

Источник

Ошибка установки SQL Server: не удалось найти дескриптор запуска ядра СУБД

В журнале установки SQL произошла следующая ошибка (файл summary.txt):

Особенность: Услуги СУБД
Статус: Ошибка: подробности см. В журналах.
Причина сбоя: во время процесса установки функции произошла ошибка.
Следующий шаг: используйте следующую информацию для устранения ошибки, удалите эту функцию, а затем снова запустите процесс установки.
Имя компонента: функции экземпляра служб СУБД SQL Server
Код ошибки компонента: 0x851A0019
Описание ошибки: не удалось найти дескриптор запуска компонента Database Engine.

Чтобы исправить ошибку установки SQL Server:

Правильно удалите все программы, связанные с SQL Server, из панели управления и перезапустите сервер (убедитесь, что в папке C: Program Files Microsoft SQL Server MSSQL12.xxx нет файлов или папок).
Запустите установку из дистрибутива SQL Server с нуля. На вкладке Конфигурация сервера убедитесь, что служба ядра СУБД SQL Server запущена с учетной записью NT Service MSSQLSERVER;
Измените эту учетную запись на NT AUTHORITY SYSTEM;
Продолжите установку SQL Server. Ошибка не должна появиться снова.

Чтобы изменить учетную запись, под которой работает SQL Server:

Запустите диспетчер конфигурации SQL Server и перейдите к службам SQL Server;
Нажмите SQL Server (MSSQLSERVER), затем нажмите кнопку «Обзор» и в поле «Эта учетная запись» укажите учетную запись, под которой должна быть запущена служба, или используйте gMSA (учетная запись группы управляемых служб). Введите пароль пользователя и сохраните изменения;
Перезапустите службы SQL Server.

Источник

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2017-11-02 10:33:21
End time: 2017-11-02 10:59:54
Requested action: Install

Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured

Slipstream: True
SP Level 1

Product Update Status:
Success: KB 3182545

Product Updates Selected for Installation:
Title: Microsoft SQL Server 2016 Express Advanced SP1
Knowledge Based Article: KB 3182545
Version: 13.1.4001.0
Architecture: x64
Language: 1033

Update Source: Slipstream

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
EXTSVCACCOUNT: NT ServiceMSSQLLaunchpad$SQLEXPRESS
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE, REPLICATION, ADVANCEDANALYTICS, FULLTEXT, RS, CONN, BC, SDK, BOL, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT ServiceMSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTROPENLICENSETERMS: true
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT ServiceReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SQLEXPRESS
SQLSVCINSTANTFILEINIT: true
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RAJ-THINKPADhuzefapc
SQLTELSVCACCT: NT ServiceSQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: Slipstream
USEMICROSOFTUPDATE: true
X86: false

Configuration file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20171102_103319ConfigurationFile.ini

Detailed results:
Feature: Client Tools Connectivity
Status: Passed

Feature: Client Tools SDK
Status: Passed

Feature: Client Tools Backwards Compatibility
Status: Passed

Feature: SQL Browser
Status: Passed

Feature: Documentation Components
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: LocalDB
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Feature: Setup Support Files
Status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20171102_103319SystemConfigurationCheck_Report.htm

Источник

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2017-11-02 10:33:21
End time: 2017-11-02 10:59:54
Requested action: Install

Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured

Slipstream: True
SP Level 1

Product Update Status:
Success: KB 3182545

Product Updates Selected for Installation:
Title: Microsoft SQL Server 2016 Express Advanced SP1
Knowledge Based Article: KB 3182545
Version: 13.1.4001.0
Architecture: x64
Language: 1033

Update Source: Slipstream

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
EXTSVCACCOUNT: NT ServiceMSSQLLaunchpad$SQLEXPRESS
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE, REPLICATION, ADVANCEDANALYTICS, FULLTEXT, RS, CONN, BC, SDK, BOL, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT ServiceMSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTROPENLICENSETERMS: true
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT ServiceReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SQLEXPRESS
SQLSVCINSTANTFILEINIT: true
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RAJ-THINKPADhuzefapc
SQLTELSVCACCT: NT ServiceSQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: Slipstream
USEMICROSOFTUPDATE: true
X86: false

Configuration file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20171102_103319ConfigurationFile.ini

Detailed results:
Feature: Client Tools Connectivity
Status: Passed

Feature: Client Tools SDK
Status: Passed

Feature: Client Tools Backwards Compatibility
Status: Passed

Feature: SQL Browser
Status: Passed

Feature: Documentation Components
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: LocalDB
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Feature: Setup Support Files
Status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:Program FilesMicrosoft SQL Server130Setup BootstrapLog20171102_103319SystemConfigurationCheck_Report.htm

Источник

Having a problem on installing ms sql server 2016 on windows 10.
I tried on possible solutions.
uninstall sql server, remove registry, fresh installation. still end up with the same error.

Here’s the errorlog:

2018-06-27 19:57:58.24 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/name ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2018-06-27 19:57:59.75 spid5s External dump process return code 0x20000001. 
2018-06-27 19:58:01.11 spid6s      Error: 5243, Severity: 22, State: 8.
2018-06-27 19:58:01.11 spid6s      An inconsistency was detected during an internal operation. Please contact technical support.
2018-06-27 19:58:01.11 spid6s      Error: 5105, Severity: 16, State: 1.
2018-06-27 19:58:01.11 spid6s      A file activation error occurred. The physical file name 'C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLDATAmodellog.ldf' may be incorrect. Diagnose and correct additional errors, and retry the operation.
2018-06-27 19:58:01.11 spid6s      File activation failure. The physical file name "C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLDATAmodellog.ldf" may be incorrect.
2018-06-27 19:58:01.11 spid6s      Error: 945, Severity: 14, State: 2.
2018-06-27 19:58:01.11 spid6s      Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2018-06-27 19:58:01.11 spid6s      SQL Server shutdown has been initiated
2018-06-27 19:58:01.11 spid6s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

THANKS!

asked Jun 28, 2018 at 4:02

edoms06edoms06

872 silver badges11 bronze badges

C:UsersAdministrator>net start mssql$msdb1 /T3608
The SQL Server (MSDB1) service is starting.
The SQL Server (MSDB1) service was started successfully.


C:UsersAdministrator>sqlcmd -e
1> restore database model
2> go
restore database model

RESTORE DATABASE successfully processed 0 pages in 0.101 seconds (0.000 MB/sec).

now the database should start

answered Jun 28, 2018 at 4:12

SudheejSudheej

1,8136 gold badges28 silver badges55 bronze badges

Источник

Windows OS Hub / SQL Server / SQL Server Install Error: Could Not Find the Database Engine Startup handle

I came across an interesting error when installing MS SQL Server 2014 on a new VM running Windows Server 2012 R2. SQL Server setup was interrupted almost at the end with the error “Could not find the Database Engine startup handle”.

There was the following error in the SQL installation log (summary.txt file):

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: Could not find the Database Engine startup handle.

This MS SQL Server installation error is related to standard installation settings when SQL Server is run under an unprivileged account NT ServiceMSSQL$V2014. This account may not have the privilege to run SQL Server service, so the service cannot be run and the installer returns the “Could not find the Database Engine startup handle” error. Also, this error may indicate that somebody has already tried to install SQL Server on this computer and files or services left after the installation have not been removed.

To fix the SQL Server install error:

Correctly uninstall all programs related to SQL Server from the Control Panel and restart your server (make sure there are no files or folders in the folder C:Program FilesMicrosoft SQL ServerMSSQL12.xxx).;
Run the installation from the SQL Server distribution from scratch. On the Server Configuration tab, make sure that the SQL Server Database Engine service is run under NT ServiceMSSQLSERVER account;
Change this account to NT AUTHORITYSYSTEM;
Continue the SQL Server installation. The error shouldn’t appear again.

After the installation is complete, we strongly recommend to change the account, under which SQL Server Database Engine is run, to an unprivileged account. You don’t need to grant this account local administrator permissions ( it’s enough to provide necessary privileges inside SQL Server security settings). You can use accounts with sysadmin privileges: NT ServiceMSSQLSERVICE or NT ServiceSQLSERVERAGENT. To change the account, under which SQL Server runs:

Run the SQL Server Configuration Manager and go to SQL Server Services;
Click SQL Server (MSSQLSERVER), then click Browse and in the “This account” field specify the account, under which the service must be run, or use a gMSA (Group Managed Service Account). Enter the user password and save the changes;
Restart SQL Server services.

This method will help you to fix the “Could not find the Database Engine startup handle” error during the installation of any SQL Server versions (2016, 2014, 2012 or 2008 r2).

Источник

Table of Contents

Introduction

Problem Definition

Cause

Solution

Uninstall

Fresh install

Looking at SQL Server Errorlog

Forum threads related to this issue

Suggested Readings

See Also

Ошибка установки SQL Server: Could not find the Database Engine startup handle

0x851a0019 ошибка установки sql server

Asked by:

Question

Ошибка установки SQL Server: не удалось найти дескриптор запуска ядра СУБД

Читайте также:

Table of Contents

Introduction

Problem Definition

Cause

Solution

Uninstall

Fresh install

Looking at SQL Server Errorlog

Forum threads related to this issue

Suggested Readings

See Also

Ошибка установки SQL Server: Could not find the Database Engine startup handle

0x851a0019 ошибка установки sql server

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Asked by:

Question

Ошибка установки SQL Server: не удалось найти дескриптор запуска ядра СУБД

Читайте также: