等待数据库引擎恢复句柄失败.检查SQL Server错误日志中是否存在潜在原因 [英] Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes

查看:687
本文介绍了等待数据库引擎恢复句柄失败.检查SQL Server错误日志中是否存在潜在原因的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用SQL Server 2012 Developer Edition.即使我尝试了2012 Express和Enterprise Edition,但都给出了相同的错误.我浏览了msdn博客以及关于stackoverflow的一些帖子. 但是没有什么可以帮助我!

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all gave same error. I browsed msdn blog as well as few post on stackoverflow. But nothing help me out from this !!!

以下是错误日志详细信息

Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2061893606
Start time:                    2013-10-21 12:58:05
End time:                      2013-10-21 13:52:30
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 DQ:              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 Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  CROY-TOSH
  Machine processor count:       4
  OS version:                    Windows 7
  OS service pack:               Service Pack 1
  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 

 Package properties:
   Description:                   Microsoft SQL Server 2012 Service Pack 1
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         C:\Users\CRoy\Downloads\SQL Server 2012 Developer  Edition (x86 and x64) - DVD (English)\x64\setup\
   Installation edition:          Developer

 Product Update Status:
  None discovered.

User Input Settings:
 ACTION:                        Install
 ADDCURRENTUSERASSQLADMIN:      false
 AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
 AGTSVCPASSWORD:                *****
 AGTSVCSTARTUPTYPE:             Manual
 ASBACKUPDIR:                   C:\Program Files\Microsoft SQL     Server\MSAS11.MSSQLSERVER\OLAP\Backup
 ASCOLLATION:                   Latin1_General_CI_AI
 ASCONFIGDIR:                   C:\Program Files\Microsoft SQL     Server\MSAS11.MSSQLSERVER\OLAP\Config
 ASDATADIR:                     C:\Program Files\Microsoft SQL  Server\MSAS11.MSSQLSERVER\OLAP\Data
 ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            CRoy-TOSH\CRoy
ASTEMPDIR:                     C:\Program Files\Microsoft SQL   Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CLTCTLRNAME:                   ROY
CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL  Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE:                Manual
CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE:               Manual
CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     CRoy-TOSH\CRoy
ENABLERANU:                    false
ENU:                           true
ERRORREPORTING:                true
FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP,  RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT,  SNAC_SDK, MDS
FILESTREAMLEVEL:               2
FILESTREAMSHARENAME:           MSSQLSERVER
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS:  false
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT Service\MsDtsServer110
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              SharePointFilesOnlyMode
RSSVCACCOUNT:                  NT Service\ReportServer
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AI
SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
 SQLSVCPASSWORD:                *****
 SQLSVCSTARTUPTYPE:             Automatic
 SQLSYSADMINACCOUNTS:           CRoy-TOSH\CRoy
 SQLTEMPDBDIR:                  <empty>
 SQLTEMPDBLOGDIR:               <empty>
 SQLUSERDBDIR:                  <empty>
 SQLUSERDBLOGDIR:               <empty>
 SQMREPORTING:                  false
 TCPENABLED:                    0
 UIMODE:                        Normal
 UpdateEnabled:                 true
 UpdateSource:                  MU
 X86:                           false

 Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini

Detailed results:
Feature:                       Management Tools - Complete
Status:                        Passed

Feature:                       Client Tools Connectivity
Status:                        Passed

 Feature:                       Client Tools SDK
 Status:                        Passed

Feature:                       Client Tools Backwards Compatibility
Status:                        Passed

Feature:                       Management Tools - Basic
Status:                        Passed

Feature:                       SQL Server Data Tools
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:          0x851A001A
 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.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

 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:          0x851A001A
 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.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

 Feature:                       Data Quality Services
 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:          0x851A001A
 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.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

 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:          0x851A001A
  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.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

 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:          0x851A001A
 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.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

 Feature:                       Master Data Services
 Status:                        Passed

 Feature:                       Distributed Replay Client
 Status:                        Passed

  Feature:                       Distributed Replay Controller
  Status:                        Passed

 Feature:                       Integration Services
 Status:                        Passed

 Feature:                       Data Quality Client
 Status:                        Passed

 Feature:                       Analysis Services
 Status:                        Passed

 Feature:                       Reporting Services - SharePoint
 Status:                        Passed

 Feature:                       Reporting Services Add-in for SharePoint Products
 Status:                        Passed

 Feature:                       SQL Browser
 Status:                        Passed

 Feature:                       Documentation Components
 Status:                        Passed

 Feature:                       SQL Writer
 Status:                        Passed

 Feature:                       SQL Client Connectivity
 Status:                        Passed

 Feature:                       SQL Client Connectivity SDK
 Status:                        Passed

 Rules with failures:

 Global rules:

 Scenario specific rules:

 Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

这里的链接很少

StackOverflow1

StackOverflow2

推荐答案

以下为我工作:

当进入服务器配置"屏幕时,将数据库引擎服务的帐户名更改为NT AUTHORITY \ NETWORK SERVICE并继续安装,它将成功安装所有组件,而不会出现任何错误. - 更多信息请访问: https://superpctricks.com/sql-install-error-数据库引擎恢复句柄失败/

When you come to Server Configuration Screen, Change the Account Name of Database Engine Service to NT AUTHORITY\NETWORK SERVICE and continue installation and it will successfully install all components without any error. - See more at: https://superpctricks.com/sql-install-error-database-engine-recovery-handle-failed/

这篇关于等待数据库引擎恢复句柄失败.检查SQL Server错误日志中是否存在潜在原因的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆